Link to home
Start Free TrialLog in
Avatar of JLazore
JLazore

asked on

Windows 2000 server can't ping domain controller until after clearing arp cache

I have a windows 2000 member server on an active directory 2008 r2 domain.  Up until recently the server functioned fine.  Now users cannot connect to the oracle database that resides on this machine.  I notice that I cannot ping the one or both of the domain controllers.  When I do a "arp -d *" it clears the arp cache and I can ping for a while.  It will eventually stop working.  I can ping other servers on the same switch (all servers are on the same switch) and I can always ping our asa firewall and internet address without clearing the cache.  It does seem like sometimes different servers will not be able to ping when the domain controller ping is not working.  Very sporadic there.  I also notice my xp pc's that connect to this server exhibit very similar behavior with the pings and also have trouble logging into the domain.  Clearing the arp cache does fix the issue on the pc's as well.  All my windows 7 pc's can work in the domain without issues but they cannot connect to this 2000 server or another 2003 server which also has the same problems.  If I pull the two trouble servers off the network the windows 7 pc's work flawlessly.
Avatar of FOX
FOX
Flag of United States of America image

On the 2000 box, in the nic properties, for your DNS entries make sure you have the ips of the domain controllers listed in there.  Then try to ping the domain controllers by ip first then by hostname to see if you get replies.
Avatar of JLazore
JLazore

ASKER

Yes my domain controllers are 192.168.1.7 and 192.168.1.12 and both are listed as DNS servers.  I noticed that this is happening on the windows 2000 server and the xp pc's that connect to the database on this server.  Clearing the arp cache works for both.  I just logged into an xp workstation and was able to ping my file and print server and I could see all the folders residing on that server.  So my active directory is functioning yet I cannot ping that 2000 until I clear the arp cache.
On the 2000 server open a command prompt and do an ipconfig/flushdns.    If you are onsite with the 2000 box, with an elevated command prompt, run a   netsh winsock reset as well , then reboot.
Next time you have the problem display the arp cache, then clear it, ping the host you are having problems reaching, then display the arp cache again.

Is the MAC address for the IP address you are trying the ping the same?

I would also suggest you install Wireshark on the server and one of the desktops that is having the problem and run a packet capture on both while the problem exists.
ASKER CERTIFIED SOLUTION
Avatar of JLazore
JLazore

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of JLazore

ASKER

Found a solution on my own.