I have tried everything I can find on the net and at Microsoft's Knowledgebase. I have two computers at home which I use to test and learn about win2k server. I have one machine loaded with server and the other with win2k-pro. I joined the Pro machine to the domain with no problem and it shows up in the Computers folder in Active Directory Users and Computers. When I try to manage it I get a message saying: Computer \\computername.domain.com cannot be managed. Network path not found. Microsoft Knowledge base says that File and Print sharing is not enabled on remote machine and to enable it, but win2k default is enabled already, so that's not it. This problem works both ways. I can log on as admin on Pro machine and get same message. I have win2k-pro dual boot on machine with Server and can load it up and can manage either way in a ptp as admin. Possible leads, named pipes? IPC$ share? Active Dir. itself? I can run registry edit and manage remote registry. Sharing files and accessing directory no problem. Reinstalling win2k server did not solve problem. This will bug me to death until I find out why.

I have had the same problem. I saw a similar post a while back. I don't think anyone here is going to be able to answer that one. Good luck!

this is a tuff one, are both hard drives NTFS??

Yes, actually both of them are NTFS. I can share resources fine, I just can't manage the server from the domain server. Any ideas would be great. Thanks, Sean

I just figured this one out. I had been having the same problem testing out windows 2000 server. The solution is you need to have the win2k server running DNS with active directory integrated and then in the tcp/ip settings of the win2k server set the first DNS server to the ip address of the werver itself. After I did this everything started working fine. I hope this helps you out.

I have a similar situation where all the workstations were joining a new domain. We have One NT 4.0 and One 2000 Server Domain controller. The workstations from the NT 4.0 were move to the 2000 DC. I removed all the machines that were listed in the Server Manager on the NT DC thinking that would help solve the problem, but ultimately the same error pops up "Computer ... cannot be managed. The network path was not found." Is there something that needs to be refreshed on the server side?