Clients not showing active on server

[Atton]

My clients are not showing active on the server. All other services such as domain registration and user tracker are working correctly. Interesting, when a computer is first registered it appears as active, but once it is imaged it does not.

---

----------------------------------UserTracker---------------------------------

8/15/2019 8:28 AM Client-Info Client Version: 0.11.16
8/15/2019 8:28 AM Client-Info Client OS: Windows
8/15/2019 8:28 AM Client-Info Server Version: 1.5.7
8/15/2019 8:28 AM Middleware::Response ERROR: Unable to get subsection
8/15/2019 8:28 AM Middleware::Response ERROR: Object reference not set to an instance of an object.
8/15/2019 8:28 AM Service Sleeping for 143 seconds
8/15/2019 8:30 AM Middleware::Communication URL: http://10.58.8.20/fog/management/index.php?sub=requestClientInfo&configure&newService&json
8/15/2019 8:30 AM Middleware::Response Success
8/15/2019 8:30 AM Middleware::Communication URL: http://10.58.8.20/fog/management/index.php?sub=requestClientInfo&mac=C8:1F:66:09:ED:88&newService&json
8/15/2019 8:30 AM Middleware::Authentication Waiting for authentication timeout to pass
8/15/2019 8:30 AM Middleware::Communication Download: http://10.58.8.20/fog/management/other/ssl/srvpublic.crt
8/15/2019 8:30 AM Data::RSA FOG Server CA cert found
8/15/2019 8:30 AM Middleware::Authentication Cert OK
8/15/2019 8:30 AM Middleware::Authentication ERROR: Could not get security token
8/15/2019 8:30 AM Middleware::Authentication ERROR: The data is invalid.

8/15/2019 8:30 AM Middleware::Communication POST URL: http://10.58.8.20/fog/management/index.php?sub=requestClientInfo&authorize&newService
8/15/2019 8:30 AM Middleware::Response Success
8/15/2019 8:30 AM Middleware::Authentication Authenticated
8/15/2019 8:30 AM Middleware::Communication URL: http://10.58.8.20/fog/management/index.php?sub=requestClientInfo&mac=C8:1F:66:09:ED:88&newService&json
8/15/2019 8:30 AM Middleware::Response Success
8/15/2019 8:30 AM Middleware::Communication URL: http://10.58.8.20/fog/service/getversion.php?clientver&newService&json
8/15/2019 8:30 AM Middleware::Communication URL: http://10.58.8.20/fog/service/getversion.php?newService&json

8/15/2019 8:30 AM Service Creating user agent cache
8/15/2019 8:30 AM Middleware::Response Success
8/15/2019 8:30 AM Middleware::Response Module is disabled globally on the FOG server
8/15/2019 8:30 AM Middleware::Response Module is disabled globally on the FOG server

[Sebastian Roth]

@Atton The status you see in the host list in the web UI is not connected to the fog-client software. The FOG server itself sends TCP connections on port 445 to the machines to check if those are online. If you’ve got the Windows firewall on all your clients appear as offline.

So why do you see it as online at first? It’s because we decided to mark a host as online when it just registered. But as the FOGPingHosts service is doing its job and find online hosts it will mark all the ones it doesn’t reach as offline then.

[Atton]

I turned off the windows defender firewall and restarted a computer. The error when authenticating is no longer there, but all computers are still appearing as unknown activity.

[Sebastian Roth]

@Atton The mentioned service on your FOG server does not check for online hosts instantly. Default setting is every half an hour I think. Do you still see it as offline now?

[Atton]

Yes. The antivirus has been disabled for 24 hours along with the windows defender firewall. I was reading and my resolv.conf file only has 127.0.1.1 as an entry. I don’t know if this matters but I saw people talking about it with this issue.

[george1421]

@Atton I just answered this in another thread but my searching skills are weak at the moment.

For your resolve.conf it will need to be adapted to looks similar to this.

search domain.com ad.domain.com
nameserver 192.168.1.16
nameserver 192.168.1.17

Put your most likely nameserver first in the list as well as the most likely domain first in the search list.

once resolve.conf is updated you should test to ping your hosts by their windows names (short names, not fqdn)

[Atton]

When I go to edit the resolv.conf file it says any changes I make will be over written.

[george1421]

@Atton If resolve.conf is managed by the NetworkManager (typ ubuntu or debian variant) application then you need to make those settings inside the networkmanager program. The other thing that would overwrite that file is if your fog server has its address defined by dhcp.

I would go ahead and set the file manually and see if something along the way changes it. No guts no glory, I say…

[Atton]

This post is deleted!

[Atton]

@george1421 My resolv.conf file has been updated. I changed the networkconnection and resolv.conf updated itself. It is still showing all red marks. Do I need to rerun the fog installer?

[george1421]

@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.

[Atton]

@george1421 I can ping the IP addresses but not the host names.

[george1421]

@Atton Well we’ll need the names resolution working. So can you ping the hosts using their FQDN?

[Atton]

@george1421 I cannot

[george1421]

@Atton Ok then something isn’t right.

Do you have an AD domain?
Is the resolv.conf pointing towards your DNS server for AD?

[Atton]

@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.

[george1421]

@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.

[Atton]

@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]

@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.

[george1421]

@Atton So now you can ping the workstation by their short windows names?