General discussion

Locked

Remote Admin for W2K server

By jim ·
I've got the snapin for the active directory for users and computers and the other admin tools installed on a windows 2000 pro workstation. The problem is I'm unable to use them from my workstation. I receive the following error: "Naming information cannot be located because: The server is not operational. Contact your system adminstrator to verify that you domain is properly configured and is currently online. When I click OK it brings up the AD for users & computers tool with a red X whereyou would normally expand the folder.
When I right click on the item and try to attach to a domain I can browse to the domain and select it but when the tool attempts to connect I get the following error: "Windows cannot connect to the new domainbecause the server is not operational"
So maybe the operations master is non-functional. How do I get that portion started?

The domain controller is a PDC I upgraded from NT4.0sp5 and it has been running fine. I have no problem configuring thedomain on the server but this remote admin has been problematic. The PDC is running in non-native mode as I need to maintain backwards compatibility with W98 & NT4 workstations for the time being.

This conversation is currently closed to new comments.

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

All Comments

Collapse -

Remote Admin for W2K server

by simonchan In reply to Remote Admin for W2K serv ...

Microsoft has confirmed that it is a bug that prevents Active Directory Administration tools from accessing multi-homed Windows 2000 Domain Controllers with more than 51 IP addresses.

Please go tot the following web page for details, http://support.microsoft.com/support/kb/articles/Q258/8/11.ASP

Collapse -

Remote Admin for W2K server

by jim In reply to Remote Admin for W2K serv ...

Poster rated this answer

Collapse -

Remote Admin for W2K server

by tony.colgrove In reply to Remote Admin for W2K serv ...

Just a note. You only need mixed mode to maintain compatability with NT4 BDC's. If all you domain controllers are Win2K, then you can move to native mode. Client PC are unaffected. There is also a ADClient for Win9x (on the WIn2k server CD) and one for NT4 (search MS's site) that allow these client to browse the directory service and change passwords on any DC.

Collapse -

Remote Admin for W2K server

by jim In reply to Remote Admin for W2K serv ...

Poster rated this answer

Collapse -

Remote Admin for W2K server

by larromac In reply to Remote Admin for W2K serv ...

You will need to add the workstation account you intend to use for remote admin to the local admninstrators grup of the server before you are allowed to connect remotely to the server.

Collapse -

Remote Admin for W2K server

by jim In reply to Remote Admin for W2K serv ...

Poster rated this answer

Collapse -

Remote Admin for W2K server

by Corky132 In reply to Remote Admin for W2K serv ...

that sounds like a dns error?? can you ping that server?? use the FQN.. myserver.domain.com...

Collapse -

Remote Admin for W2K server

by jim In reply to Remote Admin for W2K serv ...

I think you nailed it. I'm not sure how to fix it but it seems to be a likely candidate.

Collapse -

Remote Admin for W2K server

by jim In reply to Remote Admin for W2K serv ...

This question was closed by the author

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

Related Discussions

Related Forums