Discussion Locked

Manage other workstations on W2k Network

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have started a new W2k Server domain on a new server and am moving users from our old NT4.0 domain to the new one. I have only one server in the new domain and have AD running in native mode. After adding new users and computers to the network, all is well and the users have all resources required, but when I try to manage the computer (using ADUC, right click MANAGE)the operation fails with the message "Computer \\pcxx.domain.org cannot be managed. The network path was not found". I cannot find a reason for the computer being available in the AD but have this error. Any ideas?

5 replies

by jack republic

check your dns settings !!!
you shouled run dcdiag and netdiag from win2k support tool and look for fatal errors

by doug.webb

This pointed me down the right path. I actually had several issues. The DHCP server had not been authorized, and DNS and DHCP needed to be set up for dynamic updates. The clients then had to be pointed to the right DNS server (mine as opposed to my ISP's), the IP addresses released then re-registered to my new DNS RR via new addresses issued from the now authorized DHCP server. Once this added records to the DNS zone the server had to use the local DNS server as the primary instead of my ISP to resolve the FQDN required by AD to find and manage the clients. Without this I could ping the client, but not with the FQDN, only the client name.

by mcclenbw

If he's not correct, make sure the workstations have file and print sharing for MS networks installed. That solved the same problem for me this morning.

This discussion is closed to new replies.