Quest ESSO Security Service will not start on client machine
Quest ESSO Security Services was not started on the QESSO server. So existing machines were working fine because they were running in cached mode and only new machines could not communicate.
Resart the Quest ESSO Security Services on the QESSO server
Reboot the QESSO Server
Usually the service not starting on the client is due to the machine not be able to communicate to the domain controllers. Check that the domain controllers are accessible from the machines and that the Quest ESSO Security Services is running.
If it is still happening after rebooting the QESSO server, please enable debug. Click here for the instructions for enabling debug SOL46435