Comments on: WinXP Pro PC cannot ping Win2003 DC after Windows Firewall configuration. http://itknowledgeexchange.techtarget.com/itanswers/winxp-pro-pc-cannot-ping-win2003-dc-after-windows-firewall-configuration/ Mon, 09 Nov 2009 09:53:21 +0000 http://wordpress.org/?v=2.6.2 By: Labnuke99 http://itknowledgeexchange.techtarget.com/itanswers/winxp-pro-pc-cannot-ping-win2003-dc-after-windows-firewall-configuration/#comment-57947 Labnuke99 Thu, 20 Nov 2008 19:26:16 +0000 #comment-57947 Lots of problems can be solved at the physical or logical layers like this. Thanks for the update! Lots of problems can be solved at the physical or logical layers like this. Thanks for the update!

]]> By: Technochic http://itknowledgeexchange.techtarget.com/itanswers/winxp-pro-pc-cannot-ping-win2003-dc-after-windows-firewall-configuration/#comment-57938 Technochic Thu, 20 Nov 2008 16:13:16 +0000 #comment-57938 Great to know, thanks for posting your discovery! Great to know, thanks for posting your discovery!

]]> By: Erin0201 http://itknowledgeexchange.techtarget.com/itanswers/winxp-pro-pc-cannot-ping-win2003-dc-after-windows-firewall-configuration/#comment-57904 Erin0201 Wed, 19 Nov 2008 20:26:09 +0000 #comment-57904 Alright, well the problem lies with our faulty switch. We have been having connection problems with this dell switch for awhile now. I will post back if anything changes, but currently all seems well since I've switched the connections over to the hub rather than the switch. Thanks everyone :) Erin Alright, well the problem lies with our faulty switch. We have been having connection problems with this dell switch for awhile now. I will post back if anything changes, but currently all seems well since I’ve switched the connections over to the hub rather than the switch.

Thanks everyone :)
Erin

]]> By: Erin0201 http://itknowledgeexchange.techtarget.com/itanswers/winxp-pro-pc-cannot-ping-win2003-dc-after-windows-firewall-configuration/#comment-57896 Erin0201 Wed, 19 Nov 2008 18:07:41 +0000 #comment-57896 The only difference in the settings is on my pc it states our .com address instead of the .local address for the DNS suffix search list. But the .local address is listed on the test pcs and on the DC. And of course DHCP is not enabled on the DC vs. all 3 workstations. No, the workstations DNS settings are not only for the internal DC for our domain. They are for the DC and the backup DC at our corporate. They have both ip addresses listed as the DNS servers with the primary WINS server being our backup DC at corporate. For pinging 4.2.2.2 and yahoo.com my desk pc received a timeout from both. The two test pcs received ping request timeout for the 4.2.2.2 and could not find host yahoo.com. Please check the name and try again for the yahoo.com The event logs show errors such as: No Domain Controller is available for domain X due to the following: There are currently no logon servers avaialbe to service the logon request. Make sure that the computer is connected to the network and try again. If the problem persist, please contact your domain administrator. -- The time provider NtpClient is configured to acquire time from one or more time sources, however, none of the sources are currently accessible. No attempt to contact a source will be made for 959 minutes. NtpClient has no source of accurate time. (I have already checked to make sure that the test pcs are on the same time as the primary DC) -- The kerberos subsytem encountered a PAC verification failure. This indicates that the PAC from the client X in realm x.LOCAL had a PAC which failed to verify or was modified. Contact your system admin. -- (This is a new one today that I've noticed, but that doesn't mean it wasn't there yesterday. The event viewer is flooded with the antivirus trying to get updates) The system failed to register host (A) resource records (RRs) for network adapter with settings: -( All of the settings are correct including the DNS server list and primary domain suffix x.Local.) Sent update to server: <?> The reason the system could nto register these RRs was because either (a) the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not accept dynamic updates. -- Let me know if you need anything else. I am definitely at a loss here. Everything "appears" to be right which is what I can't quite figure out and these are the only 2 pcs that are experiencing this in an environment with over 80 pcs. And it only happened after configuring windows firewall which was supposed to "open" ports not deny all communication. ;) Thanks so much for your help! Erin The only difference in the settings is on my pc it states our .com address instead of the .local address for the DNS suffix search list. But the .local address is listed on the test pcs and on the DC.
And of course DHCP is not enabled on the DC vs. all 3 workstations.

No, the workstations DNS settings are not only for the internal DC for our domain. They are for the DC and the backup DC at our corporate. They have both ip addresses listed as the DNS servers with the primary WINS server being our backup DC at corporate.

For pinging 4.2.2.2 and <a href="http://yahoo.com" title="http://yahoo. " target="_blank">yahoo.com</a> my desk pc received a timeout from both. The two test pcs received ping request timeout for the 4.2.2.2 and could not find host <a href="http://yahoo.com" title="http://yahoo. " target="_blank">yahoo.com</a>. Please check the name and try again for the <a href="http://yahoo.com" title="http://yahoo. " target="_blank">yahoo.com</a>

The event logs show errors such as:
No Domain Controller is available for domain X due to the following:
There are currently no logon servers avaialbe to service the logon request.
Make sure that the computer is connected to the network and try again. If the problem persist, please contact your domain administrator.
–
The time provider NtpClient is configured to acquire time from one or more time sources, however, none of the sources are currently accessible. No attempt to contact a source will be made for 959 minutes. NtpClient has no source of accurate time. (I have already checked to make sure that the test pcs are on the same time as the primary DC)
–
The kerberos subsytem encountered a PAC verification failure. This indicates that the PAC from the client X in realm x.LOCAL had a PAC which failed to verify or was modified. Contact your system admin.
–
(This is a new one today that I’ve noticed, but that doesn’t mean it wasn’t there yesterday. The event viewer is flooded with the antivirus trying to get updates)
The system failed to register host (A) resource records (RRs) for network adapter with settings: -( All of the settings are correct including the DNS server list and primary domain suffix x.Local.)
Sent update to server: <?>
The reason the system could nto register these RRs was because either (a) the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not accept dynamic updates.
–

Let me know if you need anything else. I am definitely at a loss here. Everything “appears” to be right which is what I can’t quite figure out and these are the only 2 pcs that are experiencing this in an environment with over 80 pcs. And it only happened after configuring windows firewall which was supposed to “open” ports not deny all communication. ;)

Thanks so much for your help!
Erin

]]>