General discussion


W2K3 server - pingable but not accessible

By LANAdmin ·
I have about 110 Windows 2003 Domain Controllers. On average, about once every 3 days, a server at random will enter into a state where it is still pingable but the admin shares are not accessible, you can't run Computer Management and connect to the server. You can't Remote Desktop to the Server. You can't VNC the server. When you try to connect to c$ the following error message is displayed - "An extended error has occurred." or "System error 64 has occurred. The specified network name is no longer available."

The domain is a Windows 2003 Active Directory domain. I have also verified that all servers have the correct time and are getting their time server from the Domain Hierarchy.

Has anyone seen this behavior? Any feedback would be much appreciated.

Mike McCormick

This conversation is currently closed to new comments.

11 total posts (Page 2 of 2)   Prev   01 | 02
Thread display: Collapse - | Expand +

All Comments

Collapse -

Server Time Setting Issue

by jjondle In reply to RE: W2K3 server - pingabl ...

I just had the same error when trying to connect to one of my new servers. When connecting to an admin share it would say that "An extended error orccurred" and when I tried to connect to a regular share it told me that "This server's clock is not syncchronized with the primary domain controller's clock".

When I checked, the time was set correctly, but I failed to get the Time Zone changed from Easter to Central, so that was the issue for me.

Probably not the answer to this particular thread, but if anyone comes along this may help them out also.

Back to Networks Forum
11 total posts (Page 2 of 2)   Prev   01 | 02

Related Discussions

Related Forums