Naming information cannot be located; Server not operational on Win2k3
- From: "Ben Scaithe" <quixotic68@xxxxxxxxxxx>
- Date: Fri, 1 Jul 2005 13:56:34 -0400
Having a problem with a Windows 2003 Server all of a sudden where everyone
loses access to the printers shared from the server. If I open Active
Directory Users and Computers at the server console, I get the following
message:
Naming information cannot be located for the following reason:
The server is not operational.
If you are trying to connect to a domain controller running Windows 2000,
verify that Windows 2000 Server Service Pack 3 or later is installed on the
domain controller, or use the Windows 2000 administration tools. For more
information about connecting to domain controllers running Windows 2000, see
Help & Support.
Rebooting the server returned things to normal, but it happened again the
very next day.
I looked in the KB and found a similar issue addressed in article 323542.
It says it applies only to Windows 2000, though, and we don't have any
TCP/IP filtering turned on at the server. Considering that I'm getting this
at the console, I don't think filtering would apply, anyway.
It first showed up right after a thunderstorm rolled through, so obviously I
suspect that's not coincidental. It's just an awful specific problem to see
for something meteorologically related.
Any thoughts?
Thanks!
- Ben
.
- Follow-Ups:
- Re: Naming information cannot be located; Server not operational on Win2k3
- From: Chriss3 [MVP]
- Re: Naming information cannot be located; Server not operational on Win2k3
- Prev by Date: Replication Problems Event ID 1311, 1865, 1566
- Next by Date: Re: Speed up Network Drive Mapping
- Previous by thread: Replication Problems Event ID 1311, 1865, 1566
- Next by thread: Re: Naming information cannot be located; Server not operational on Win2k3
- Index(es):
Relevant Pages
|
