DHCP gives IP, but then PC can't ping DHCP server

Question

_{Monday, June 6, 2011 8:04 PM}

Windows Server 2008 R2 with SP1. IP address statically assigned is 192.168.10.12. Roles are Active Directory Services, AD Certificates, DHCP, DNS, File Services (DFS), and Print services.

This server replaced another server last night with the same services, but IP was 192.168.10.11.

PCs are running Windows 7 x64 (with and without SP1). We have about 100 PCs. All but 4 are working with the new server just fine. These 4 will get DHCP information from the server. They'll get an IP (which gets put into the DHCP reservation list). They'll get subnet mask, gateway, and DNS server information just fine. Their dynamic network properties are populated just fine. These 4 machines can ping the email server, the vpn server, and any IP address on the network except for the Windows server (192.168.10.12). It just times out.

If I put in the same IP / network information into the PCs statically, they work just fine. Only when getting the information via DHCP do they fail.

I tried fixing them by doing

sfc /scannow

netsh winsock reset

netsh int ip reset

Even removed the NIC from device manager and had it reinstall it. I've even removed the PC from the Domain and rejoined it to reset that information. I removed all references to the PCs from the DHCP and DNS servers.

Doing all of that, 1 of the PCs now works fine. The others do not though. I've tried various sequences of the above steps. I've done reboots after each step. I've tried everything I can think of. Can anyone offer me any clues?

All replies (11)

_{Thursday, June 9, 2011 3:42 PM ✅Answered | 1 vote}

Last night, I removed the DHCP and DNS server roles from the server. Rebooted, etc etc.

Reinstalled DHCP, reconfigured etc. Manually set up the scope and reservations again (only 1 scope and 10 reservations)

Reinstalled DNS. All the zones came back. They were saved in Active Directory. Deleted them all and recreated them. Only 1 Forward and 1 Reverse. The _msdcs. zone was not recreated. After some searching, decided to just manually create it. The _msdcs subzone under the domain was present though. All things looked good.

Rebooted server, ran through a few tests, best practices, etc. Looked good.

Rebooted the machines that was giving problem and they worked fine.

It seems something had been corrupted in the DNS and DHCP migration on the server side. Wish I hadn't wiped those 2 other computers first though. Now I have to reinstall everything. (Going to reinstall rather than image cause the images are a year old and we need fresh ones anyway.)

Freaky problem, but solved. Thanks to everyone for their help!

_{Tuesday, June 7, 2011 5:21 AM | 1 vote}

Hi,

Thanks for posting here.

Can you compare the server and scope options you set on this new DHCP server with the pervious one’s first?

We’d suggest migrate the old DHCP settings to the new one with following article and this method should also apply to Windows server 2008 to 2008 migration scenario:

How to move a DHCP database from a computer that is running Windows Server 2003 to Windows Server 2008

http://support.microsoft.com/kb/962355

After that please check if this issue persist. Meanwhile, some connectivity troubleshooting methods could also be found form the article below, please also verify the local ARP cache :

How to troubleshoot TCP/IP connectivity with Windows XP

http://support.microsoft.com/kb/314067

Thanks.

Tiger Li

TechNet Subscriber Support in forum

If you have any feedback on our support, please contact [email protected]

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

_{Tuesday, June 7, 2011 5:53 AM}

The old DHCP server is decommissioned and not online. I'm sure the currently active scope is fine. I have about 90 computers using it and they function fine. It's just these 4 that aren't working. I'm guessing it's something corrupted in the OS. Here's what the DHCP server does hand out:

IP address (let's say 192.168.10.101 for example)

subnet: 255.255.255.0

gateway: 192.168.10.1

DNS: 192.168.10.12 (which houses the DHCP, Active Directory, and file shares as well)

These 4 machines get those settings. And they can ping everything on the network fine except for 192.168.10.12. They boot and get DHCP configuration information from .12 server. The server even updates DHCP and DNS records to reflect them getting IP addresses. However these 4 machines cannot contact .12 server in any way once this happens.

If I change the 4 machines TCP/IPv4 properties from using DHCP to static information (exactly as the above), then they function fine. The only thing changed is from DHCP to static configuration. All IP information stays the same. DHCP = no contacting .12. Static = working. And about 90 other machines work fine with DHCP.

I'm pretty sure it's something cached that's causing the problem, but I can't figure out what exactly.

I'll read the links you posted in about 9 hours when I go into work. I'll post back what I discover.

_{Tuesday, June 7, 2011 6:36 PM}

When you run an ipconfig /all, does it show the old DC or the new DC as a DNS address? Check the registry in HKLM\System\Services\TCPIP\Parameters\Interfaces for any settings that seem amiss while the machine is set to DHCP.

Is there a local firewall running (Windows or third party such as Symantec, McAfee, AVG, Avast, etc)?

Ace

Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

This posting is provided AS-IS with no warranties or guarantees and confers no rights.

_{Tuesday, June 7, 2011 7:03 PM}

The DHCP and the static information is the same. IPConfig /all reveals DHCP points to the .12 server as it should. The registry settings reflect this and I see nothing out of the ordinary.

DHCP

C:\>ipconfig /all

Windows IP Configuration

  Host Name . . . . . . . . . . . . : MISPC-01
  Primary Dns Suffix . . . . . . . : lwia41.lan
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : lwia41.lan

Ethernet adapter Local Area Connection:

  Connection-specific DNS Suffix . : lwia41.lan
  Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connec
tion
  Physical Address. . . . . . . . . : 00-24-E8-1A-07-E4
  DHCP Enabled. . . . . . . . . . . : Yes
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::a076:95cb:d19:fd53%15(Preferred)
  IPv4 Address. . . . . . . . . . . : 192.168.10.121(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Lease Obtained. . . . . . . . . . : Tuesday, June 07, 2011 1:56:19 PM
  Lease Expires . . . . . . . . . . : Wednesday, June 15, 2011 1:56:19 PM
  Default Gateway . . . . . . . . . : 192.168.10.1
  DHCP Server . . . . . . . . . . . : 192.168.10.12
  DHCPv6 IAID . . . . . . . . . . . : 251667688
  DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-29-BB-02-00-24-E8-1A-44-72

  DNS Servers . . . . . . . . . . . : 192.168.10.12
  NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.lwia41.lan:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix . : lwia41.lan
  Description . . . . . . . . . . . : Microsoft ISATAP Adapter
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix . :
  Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

Static

C:\>ipconfig /all

Windows IP Configuration

  Host Name . . . . . . . . . . . . : MISPC-01
  Primary Dns Suffix . . . . . . . : lwia41.lan
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No
  DNS Suffix Search List. . . . . . : lwia41.lan

Ethernet adapter Local Area Connection:

  Connection-specific DNS Suffix . :
  Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connec
tion
  Physical Address. . . . . . . . . : 00-24-E8-1A-07-E4
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  Link-local IPv6 Address . . . . . : fe80::a076:95cb:d19:fd53%15(Preferred)
  IPv4 Address. . . . . . . . . . . : 192.168.10.50(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 192.168.10.1
  DHCPv6 IAID . . . . . . . . . . . : 251667688
  DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-29-BB-02-00-24-E8-1A-44-72

  DNS Servers . . . . . . . . . . . : 192.168.10.12
  NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{6BE3745A-9251-4BCB-869E-7FF1F635700D}:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix . :
  Description . . . . . . . . . . . : Microsoft ISATAP Adapter
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix . :
  Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

_{Tuesday, June 7, 2011 7:22 PM}

Try resetting the TCPIP stack with

netsh int ip reset c:\resetlog.txt

More info:

How to reset the TCP/IP stack:
http://support.microsoft.com/kb/299357

Ace

This posting is provided AS-IS with no warranties or guarantees and confers no rights.

_{Wednesday, June 8, 2011 4:07 PM}

Okay. I just reinstalled Windows on one of the PCs. Destroyed all partitions, and reinstalled Win7 x64 Ultimate. The problem persists. So the problem has to be server side, right?

_{Thursday, June 9, 2011 12:42 PM | 1 vote}

So let's take a deeper look at the server. What's installed on it? Is there an AV/Security app that is perhaps set to "protect network traffic?"

Is there a local firewall running (Windows or third party such as Symantec, McAfee, AVG, Avast, etc)?

This posting is provided AS-IS with no warranties or guarantees and confers no rights.

_{Friday, June 10, 2011 3:05 AM}

Good to hear you found a resolution. Interesting a corruption such as this would have caused it.

As for the _msdcs zone, if you manually recreated it, make sure you have a delegation created under the lwia41.lan zone for "_msdcs" to insure it's properly working. You can then run an ipconfig /registerdns, then restart the Netlogon service and the SRV records will get recreated under the _msdcs zone.

Ace

This posting is provided AS-IS with no warranties or guarantees and confers no rights.

_{Friday, June 10, 2011 10:59 AM}

Hello ,

1) When DHCP is giving out the IP - are clients getting proper IP address ?

2) If yes then try to do a NSLOOKUP for the 192.168.10.12 - see whats the name it resolves to?

3)we can check if there are any security rules for ICMP.

4)We can try stopping BFE service for couple of minutes and check if the ping works?

Thanks
Rajesh

_{Wednesday, June 1, 2016 6:13 AM}

Hello~ :)

In my case

I guess this issue is "Port-Security of Switch".

You need to resolve it with Switch configuration(Disable to port-security or Clear to Mac address).

Thank you

Last updated on 2011-06-06

Share via

DHCP gives IP, but then PC can't ping DHCP server

Question

All replies (11)

Additional resources