I found out by myself that changing the ip adress after the installation is a lot of trouble. do you have the possibility to setup a new server with the correct ip adress? this is way easier.
otherwise it would be helpful if you would tell us wich steps you were following.
greetings
@mlimburn have you read this thread? maybe it is helpful.
https://forums.fogproject.org/topic/6378/changing-ip-address-post-fog-install-is-problematic/27
there is provided a script that does a lot of ip changing, maybe using this script will get everything right and fix maybe forgotten entrys.
I’m using mostly ubuntu and all my images are set to “single disk, resizable” .
the order you should go in short:
on the desktop pc:
setup the desktop you want to clone
enable pxe boot in the bios of your desktop pc
on the fog server (gui):
create new image (single disk, resizable) (image management)
register host pc with the server(there are multiple ways to to that, check the wiki 
)
assign your created image with the entry of the desktop pc (select host image in host management)
click on capture image at the entry of your desktop pc
if you don’t run the fog client on the desktop pc, you should reboot your pc so it does the magic
deploy a image:
is mostly the same as above: create new host, assign image, click on deploy.
you should also look for the “fog client” - running it on the desktop pc is very usefull!
I hope I did not forget anything. 
@george1421 I don’t have any windows computers in my network. but i can ping (normal ping, not icmp) the ubuntu clients over the terminal of the fog host by the short name “pool-05” or by the IP, both successfull.
if I ping a pool pc from the server using “nc -zvv <ip_addr> 445” I also get connection refused.
root@fog:/home/admin# nc -zvv IP 445
pool-14.domain [IP] 445 (microsoft-ds) : Connection refused
sent 0, rcvd 0
Does your testing mean, that, if I install samba at my hosts, the ping would work?
I testet it installing samba and libnss-winbind and configured the file /etc/nsswitch.conf
from
hosts: files mdns4_minimal [NOTFOUND=return] dns
to
hosts: files wins mdns4_minimal [NOTFOUND=return] dns
now the output looks like this:
root@fog:/home/admin# nc -zvv IP 445
pool-14.domain [IP] 445 (microsoft-ds) open
sent 0, rcvd 0
but the hosts list still returns an error “connection timed out”
Maybe, in a new version of fog, maybe the process of pinging using icmp can be changed to a normal ping to be more variable for linux hosts? that would be great.
I will also try the steps postet by @Tom-Elliott and write back if anything changes.
@Tom-Elliott yes, I can confirm this - I don’t have to enable the ports, but I want to. I like this feature very much and it would be sad If I won’t be able to use it. 
The problem with my setup is that it says “connection refused” although I enabled the port 445 both on the server and the host via ufw firewall.
Server OS is the latest debian 8 and Client OS is the latest Ubuntu 16.04 Maybe anyone has some ideas. Thanks in advance. :))
@Tom-Elliott do you have any idea what I can try to fix this except opening the port on the host?
@Tom-Elliott Is this the same port for linux, like ubuntu 16.04 or debian 8? I also have the connection time out issue in the host menue.
If i enable the ufw firewall on ubutu and allow the port 445, the status changes from “connection timeout” to “connection refused”
I allowed these ports. (22 for ssh, 445 for the fog ping)
To Action From
-- ------ ----
22 ALLOW IN Anywhere
445 ALLOW IN Anywhere
22 (v6) ALLOW IN Anywhere (v6)
445 (v6) ALLOW IN Anywhere (v6) ```@Joe-Schmitt thank you I finally found a little mistake that crashed everything, so now it runs perfectly. this can be marked as solved. thanks again for all your help!
is it also possible to change the links on the web ui, so the links, e.g.
/fog/management/index.php?node=host
can be changed to
/fog/management/index.php?node=host&sub=list
so it immediately shows all hosts if i click on the hosts button?
well, I have to ask another question - My Snapin does not work correctly. If I start it manually on the host pc, everything works fine. but If i run it with the fog client, it does not work. the snapin history of the client says:
joindomain 2017-03-15 10:22:44 Complete 30 seconds 0
so no error code. that’s fine I guess. I read in your wiki, that the script is run by the user root or SYSTEM and that there may be some issues with the security, but I really can’t find out where or what the issues could be.
here are my snapin settings:
Name joindomain
Type Snapin Pack
Pack Template - please select an option -
Pack File /bin/bash
Pack Arguments “[FOG_SNAPIN_PATH]/joindomain.sh”
Reboot after install checked
Snapin enabled checked
Replicate? checked
Timeout after 600 seconds
Snapin Command /bin/bash “[FOG_SNAPIN_PATH]/joindomain.sh”
the fog client log says the following -
so also everything seems to be fine. what else can I consider?
------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
3/15/2017 11:22 AM Client-Info Client Version: 0.11.9
3/15/2017 11:22 AM Client-Info Client OS: Linux
3/15/2017 11:22 AM Client-Info Server Version: 1.3.4
3/15/2017 11:22 AM Middleware::Response Success
3/15/2017 11:22 AM SnapinClient Snapin Found:
3/15/2017 11:22 AM SnapinClient ID: 25
3/15/2017 11:22 AM SnapinClient Name: joindomain
3/15/2017 11:22 AM SnapinClient Created: 2017-03-15 10:22:42
3/15/2017 11:22 AM SnapinClient Action: reboot
3/15/2017 11:22 AM SnapinClient Pack: True
3/15/2017 11:22 AM SnapinClient Hide: False
3/15/2017 11:22 AM SnapinClient Server:
3/15/2017 11:22 AM SnapinClient TimeOut: 600
3/15/2017 11:22 AM SnapinClient SnapinPack File: /bin/bash
3/15/2017 11:22 AM SnapinClient SnapinPack Args: "[FOG_SNAPIN_PATH]/joindomain.sh"
3/15/2017 11:22 AM SnapinClient File: joindomain.zip
3/15/2017 11:22 AM Middleware::Communication Download: http://10.83.167.14/fog/service/snapins.file.php?mac=44:37:E6:56:46:19&taskid=25
3/15/2017 11:22 AM SnapinClient /opt/fog-service/tmp/joindomain.zip
3/15/2017 11:22 AM SnapinClient Processing SnapinPack joindomain.zip
3/15/2017 11:22 AM SnapinClient Extracting SnapinPack
3/15/2017 11:22 AM SnapinClient Processing SnapinPack settings
3/15/2017 11:22 AM SnapinClient New SnapinPack File: /bin/bash
3/15/2017 11:22 AM SnapinClient New SnapinPack Args: "/opt/fog-service/tmp/joindomain/joindomain.sh"
3/15/2017 11:22 AM Bus {
"self": true,
"channel": "Notification",
"data": "{\n \"title\": \"Installing joindomain\",\n \"message\": \"Please do not shutdown until this is completed\"\n}"
}
3/15/2017 11:22 AM Bus Emmiting message on channel: Notification
3/15/2017 11:22 AM SnapinClient Starting snapin...
3/15/2017 11:23 AM SnapinClient Snapin finished
3/15/2017 11:23 AM SnapinClient Return Code: 0
3/15/2017 11:23 AM Bus {
"self": true,
"channel": "Notification",
"data": "{\n \"title\": \"joindomain installed\",\n \"message\": \"Installation has finished and is now ready for use\"\n}"
}
3/15/2017 11:23 AM Bus Emmiting message on channel: Notification
3/15/2017 11:23 AM Middleware::Communication URL: http://10.83.167.14/fog/service/snapins.checkin.php?taskid=25&exitcode=0&mac=44:37:E6:56:46:19&newService&json
3/15/2017 11:23 AM Power Creating shutdown command in 60 seconds
3/15/2017 11:23 AM Bus {
"self": true,
"channel": "Power",
"data": "{\n \"action\": \"request\",\n \"period\": 60,\n \"options\": 2,\n \"command\": \"-r +0 \\\"Snapin requested restart\\\"\",\n \"aggregatedDelayTime\": 0,\n \"message\": \"This computer needs to reboot to apply new software.\"\n}"
}
3/15/2017 11:23 AM Bus Emmiting message on channel: Power
------------------------------------------------------------------------------
@Joe-Schmitt snapins now work perfectly! thanks a lot!
Now i just have to do some settings on my custom snapin - but I will do this tomorrow, its already late here in germany. Thanks again for your help, I really appreciate it!