Clients not showing active on server
-
@Atton Can you ping a windows computer from your fog server using its short name?
If so then it should be setup correctly if you have port 445 enabled on the target computer’s firewall. FOG doesn’t use the simple ping check to confirm the computers online, it uses a connect to port 445 which is a bit more reliable to show the system is actually up than a ping.
There is a FOG service that runs at some interval to refresh the up/down status. That may have not run yet, if you just fixed the name resolver. Rebooting your FOG server should kick everything off again.
-
@george1421 I can ping the IP addresses but not the host names.
-
@Atton Well we’ll need the names resolution working. So can you ping the hosts using their FQDN?
-
@george1421 I cannot
-
@Atton Ok then something isn’t right.
Do you have an AD domain?
Is the resolv.conf pointing towards your DNS server for AD? -
@george1421 We have 3 windows active directory servers. I pointed the resolv.conf file to two of them and didn’t get anything. Resolv.conf has since overwritten itself to say 127.0.1.1.
-
@Atton So just to confirm that your fog server’s IP address is hard coded and not set by dhcp?
If its not set by dhcp, I might assume you have a ubuntu or debian based FOG server? If that is the case you will need to go into the network manager application and define the name servers and search domain in that app because each time you reboot the fog server the network manager rewrites that resolve.conf file.
-
@george1421 My ipaddress is set to static in the network manager. I am using Ubuntu and the AD servers are all in the network manager along with the domain.
-
@Atton I think I got it. I had two of our Active Directory servers in the network manager but not the third one that handles our DHCP service.
-
@Atton So now you can ping the workstation by their short windows names?
