General discussion

Locked

unable to ping even ip add of PC from DC

By nirmalkishore ·
Hello
Earlier this afternoon, I came across a very strange behaviour on a Windows Server 2003.

I renamed a few PCs(all Win XP) and tried to browse for the PCs on the Domain controller. The new names do appear on DNS, DHCP and in the Network Neighborhood(Entire Network). However, I cannot ping the PCs from the server by name or even by ip address. At the moment, the only thing that seems to be possible is ping between the 2 domain controllers.

On the other hand, the XP pcs can ping the 2 servers(DCs) but not anything else.
DNS is set to allow Dynamic updates(secure only)
When I did an nslookup(both on server and PC) the DNS server was being identified, but the PC name was not getting resolved. So I did an ipconfig /registerdns from the client PC and then retried nslookup. This time however, the pc name got resolved. But ping was not still possible.

The PCs can logon normally and I could not find any other visible problems

One other component in the network is an ISA server 2004. This is too long and unsure shot but I am going to try and stop ISA tomorrow and see if that makes any difference.

What still amazes me is the inability to ping ip address.

Has anyone here experienced this issue. Please throw some light.

Thanks
Nirmal

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by Blackcurrant In reply to unable to ping even ip ad ...

Hi

You say you renamed your PC's. Do the new names appear in the list of computers in the Active Directory? Sounds like you may need to:

1. Remove the old PC's from Active Directory Users and Computers
2. Rejoin the newly named PC's to the domain.

Hope this helps

Collapse -

by nirmalkishore In reply to unable to ping even ip ad ...

Hi
Thanks for the reply.
I have tried removing the PC and adding it back to the domain. That does not seem to work.

Actually, I just came across exactly the same issue with another Windows server 2003 setup in combination with a Windows XP client

Any ideas??

Thanks
Nirmal

Collapse -

by caestelle In reply to unable to ping even ip ad ...

Sounds like the hostname and IP are cached within WINS/DNS/DCHP. I would remove the trouble PCs from the domain. Go into WINS, DNS, and DHCP and delete all references to both the hostname and ip addresses of the computers and then readd them to the domain.

I have had this issue before and the above is what fixed it for me. I hope this helps!!!

Collapse -

by haileyan In reply to unable to ping even ip ad ...

I had something similar happen. I had to delete the entry for the PC in DNS. Then I went to the machine and did a IPCONFIG /REGISTERDNS. Viola! Everything was happy.

For some reason after the name change the PC was getting a new IP address from DHCP but for somereason was not updating DNS with the new IP.

Collapse -

by ralderman In reply to unable to ping even ip ad ...

It sounds like the client firewalls on the XP machines are blocking pings.

Rick

Collapse -

by nirmalkishore In reply to

Poster rated this answer.
Hey Ralderman.. That's it man.. I disable XP firewall and that did the trick..
Thanks
Nirmal

Collapse -

by nirmalkishore In reply to unable to ping even ip ad ...

This question was closed by the author

Back to Windows Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums