Click here for important information about

DNS and DHCP Not working

Microsoft Windows 2003 server - 5 users
August 2, 2010 at 11:19:10
Specs: Windows Vista (clients)

This morning I came into work and the users complained that they could not access the internet or the shared folders on the server. I checked their IPs and it was clear they were no longer getting IP addresses from the server. Everyone had 169 addresses. We are using windows server 2003 and the clients are windows vista business. The server is the DHHCP, DNS,and DC.

Here is what I did so far to troubleshoot problem:

1. Reboot the server - upon startup the server says that a driver or service may not have stared correctly. The event viewer doesnt say much. In device manager there are no shown problems. In services DHCP says "not connected" and DNS says nothing next to it. Also rebooted all the switches

2. I tried manually assigning IP addresses to the clients. This worked for connecting to the internet only when I used googles DNS of as then secondary dns server. However, the clients were still unable to access internet network shares on the server, even by IP address.

3. The server can ping all clients, but the clients cannot ping the server

4. The server is able to access the internet no problem

It seems as if DNS and DHCP are screwin up on the server.

Thanks a lot for the help

See More: DNS and DHCP Not working

August 2, 2010 at 12:03:08
Did you review the server event viewer logs? They would provide clues to the problem source.

Report •

August 2, 2010 at 12:15:55
Have you tried removing the roles (DNS & DHCP) and re-adding them?

Report •

August 2, 2010 at 12:16:34
2 errors...service control manager & ipnathlp are the sources.

i can get the exact error messages in about an hour

Report •

Related Solutions

August 2, 2010 at 12:19:32
this is further problematic because i am not at the site currently so one of my collegues is telling me over the phone what is happening as he clicks around

we will re-add the roles as soon as I can get in touch with him. as i am not there and have no access to windows server here (tried installing a VM but im on a home machinepremium...grrr), we can see the current settings through manage your server and copy them correct?

Report •

August 2, 2010 at 12:30:47
as for removing and adding DNS, what are the best practices?

I'm seeing some errors people experience doing this through google such as

Report •

August 2, 2010 at 12:45:06
Start with the DHCP. You can remove that role without any issues. Then flush the DNS and the workstations.

How many PC we talking about?

Report •

August 2, 2010 at 12:59:13
Not clear what the amount of pcs has to do with addressing the issue.

Given the severity of the issue the point isn't to put in a quick fix. Restore to a time it worked from back up would that.

The question is what is broken and why.

Given the hints of the server can't be pinged indicates either a corrupt nic or tcp/ip stack or it could be as simple as a misconfiguration of the firewall software.

I would also ask the collegue what recent changes were made like new software or updates to software.

This being said I would suggest caution before you gut and rebuild the server.

Report •

August 2, 2010 at 13:35:56
I was just asking about the number of PC's to gauge size of this network. Not really anything important, just my burning curiosity.

Report •

August 2, 2010 at 15:07:48
still whats strange is how the clients cant ping server but server can ping out. this is probably the root cause of the rest of the problems no?

fyi there are about 15 clients on the network

Report •

August 2, 2010 at 15:08:56
also unfortunately i dont think we have a good backup. we were putting a backup solution in place and were only doing incremental backups on a single hard drive while waiting for a second hard drive to be purchased. the last backup failed on sat

Report •

August 2, 2010 at 15:32:41
This would also indicate the server was not properly protected from the internet.

Appears to me this was the end result of a long line of unaddressed failures. I have seen these results many times before.

How far back do the red warning go in event viewer logs?

Do you have any tested-as-good backups? It maybe better to just rebuild the server, install the apps and restore what data you have.

Your server should be behind a firewall router appliance. All patches kept up-to-date and it should have AV and Antimalware software installed and running. It should have mirrored drives minimum and backups should be full and tested by doing restores to a spare drive.

Report •

August 3, 2010 at 01:42:41

Hi Majtech
When you work and users complained that they could not access internet, the problem should be related to your IP address. You should change your IP address To work on internet..

Report •

August 3, 2010 at 12:30:35
problem is solved for now...not sure what the solution was. when i get back to the office in a few weeks i will post back with what they did to fix it

thanks for the help everyone

Report •

Ask Question