General discussion

Locked

Can't connect to global catalog

By NateH ·
Hi all,

I have a client running Win2000 server as a domain controller. He has multiple win95 and win98 machines as well as several XP Pro.

Last week he called to complain things were running very slow and that the XP machines could not log on to the server. (The XP are the only ones set up to connect to the domain. The Win95/98 are set up in a workgroup config.)

I checked the server and found that there were multiple errors including one in particular that was disturbing:
"unable to establish connection with global catalog"

Another error in the event log:
"Windows cannot access the registry information at \\.... with (53)."

I tried to open the Active Directory Site and Services, but got an error message:
"Naming information cannot be located because specified domain does not exist or could not be contacted.."

I started poking around and finally found that the Net Logon service was halted. I started it and suddenly all seemed back to normal.

However, when I rebooted, the same situation happened again.

I did check for this error and SP4 was installed, but I cannot figure out what is the cause here.

HELP!!


Nate

This conversation is currently closed to new comments.

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

All Comments

Collapse -

by sgt_shultz In reply to Can't connect to global c ...

Microsoft Knowledge Base Article - 272686
Search Support (KB)
Windows 2000
Error Messages Occur When Active Directory Users and Computers Snap-in Is Opened
View products that this article applies to.
This article was previously published under Q272686
SYMPTOMS
On a Windows 2000-based domain controller, when you open the Active Directory Users and Computers snap-in, you may receive the following error message:

Naming information cannot be located because the specified domain either does not exist or cannot be contacted. Contact your system administrator to verify that your domain is properly configured and is currently online
When you run the Domain Controller Diagnostics tool (Dcdiag.exe) on the domain controller, you may receive the following error message:

Starting test: Services

w32time Service is stopped on server

Starting test: FsmoCheck

Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
A Good Time Server could not be located.
......................... domain.com failed test FsmoCheck
CAUSE
This issue can occur because either:

The Windows Time service has stopped.

-or-
In the Windows Time service on the domain controller, Startup Type is set to Disabled.
RESOLUTION
To resolve this issue, follow these steps:

Click Start, point to Programs, point to Administrative Tools, and then click Services.
Click Services MMC.
Start the Windows Time service.
Under Startup Type, click Automatic.
Restart the server.
The information in this article applies to:
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server

Collapse -

by NateH In reply to Can't connect to global c ...

This question was closed by the author

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

Related Discussions

Related Forums