Link to home
Start Free TrialLog in
Avatar of Larry Rungren
Larry RungrenFlag for United States of America

asked on

DHCP stopped working

I have a small LAN with about 50 PC's, and today when people logged out and then logged back on they can't connect to the DHCP server.  I have checked the AD server that serves DHCP and the server is up and running,  If I run ipconfig and release/renew the renew fails stating it can't connect to dhcp server.  I have restarted The DHCP Client and Server in the AD server with no luck.

Why would the DHCP Server become invisible ?  These systems have been running for between 2 and 5 years??

They are seeing the Domain Controller on the same server??? and execute logon.bat files???
Avatar of dtrance

Are you out of addresses?  Check your pool and reservations.  What does the event viewer say?
Avatar of Ernie Beek
Did you check the logs on the server to see if anything is going wrong there?
faulty nic on dhcp server.
Avatar of Larry Rungren


The error that I am getting in event viewer is from Userenv  ID 1030
"windows cannot query for thew list of Group Policy objects.
Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
maybe someone plugged in a router or wifi ap that has a dhcp server.ç this will cause ms dhcp server service to stop.
No one has plugged anything into the network with DHCP service, I can rdp to the server and run other applications on the server so I don't think it is the nic card.  Besides AD and DNS run from that server
Have you recently updated your antivirus? What antivirus program are you running?
I'm running Symantec, but this has been the same version for over 3 years
I'm assuming you're running Endpoint Protection.
I would check the Symantec Network Access Control service state. If it is stopped then start it and test DHCP. If DHCP still doesn't work when the service is started then uninstall Symantec and test.

If DHCP works then you can reinstall Symantec. It should still work.
I am still running Symantec 10.1.5
OK, I don't remember the service name in SAV 10.1 so look through them and make sure the appropriate services are running. Advice for uninstalling and testing still stands. Give that a shot and let us know what you find.

BTW - why not install the latest version? you're entitled to it if you have a current subscription.
I have found that replication is not running.  There was one source that said if replication not running then the error or one very similar will occur.

There s an issue with one of the servers and the latest version.
I don't see how this is related to DHCP. Is the DHCP server service running?
Is ther some diagnostic that I can run and send to you to help, my understanding and description is apparently not helping.
OK. Have you checked the Symantec services like I suggested? Have you uninstalled Symantec like I suggested?

I am speaking from experience of troubleshooting DHCP issue.
Which part of symantec do you think I need to remove.  I am afraid that if I restart the server then no one will be able to log on.  as it is now anyone who was logged on yesterday early AM and has not logged out can still use the system.  Anyone who has logged out cannot log back in and their system is assigned the dummy ip 169.254.x.x when dhcp tries to run
You should remove the Symantec Antivirus portion and leave the management. This will require a reboot as you mentioned.

Now, the issues that your workstations are facing are because they rebooted and are not getting a DHCP address and therefore cannot contact anything on the network. Soon, once the workstations DHCP leases have expired, all workstations will not be able to connect. Rebooting the server will not cause the workstations to loose their DHCP addresses but time will. We need to move on getting this resolved ASAP.

Avatar of Larry Rungren
Larry Rungren
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
As none of the suggestions were used and a simple restart of Cisco switches cleared up the problem this is the answer I accept