Guest Jim at SDSU Posted July 30, 2007 Posted July 30, 2007 Help!! I have a new Domain with 2 2003R2 servers and 3 XP Workstations and 1 Vista workstations installed as a test. The install is still "vanilla" meaning I haven't set any custom GPO's etc yet. In the "AD Users and Computers" MMC, if I right click on one of the workstations and select "Manage", after about 40 seconds of Hourglass, I get the error message "Computer\\computer.mydomain.edu cannot be managed. The network path was not found." For troubleshooting purposes, the firewalls are all turned off. I can ping the workstations by name and the ping shows the correct IP's. If I try to connect using "Net use x: \\computer.mydomain.edu\C$", I get the "network path not found, however if I do the same from another workstation in the Domain the connection works perfectly. The two servers however can manage each other. Anyone have any suggestions as to what I should be looking at? Domain Admins group is a member of Local Admins group on each workstation.
Guest Danny Sanders Posted July 30, 2007 Posted July 30, 2007 Re: Can't remotely manage workstations > In the "AD Users and Computers" MMC, if I right click on one of the > workstations and select "Manage", after about 40 seconds of Hourglass, I > get > the error message "Computer\\computer.mydomain.edu cannot be managed. The > network path was not found." > Usually path not found error in AD mean DNS are not setup correctly. AD MUST have a DNS server setup to host the DNS zone for the AD domain. NOT your ISP's DNS. In the properties of TCP/IP on the computer having the problems, what server does it point to for DNS? hth DDS "Jim at SDSU" <JimatSDSU@discussions.microsoft.com> wrote in message news:DBAD1F86-F090-4C89-B651-37CAB7E652B5@microsoft.com... > Help!! > > > > I have a new Domain with 2 2003R2 servers and 3 XP Workstations and 1 > Vista > workstations installed as a test. The install is still "vanilla" meaning I > haven't set any custom GPO's etc yet. > > > > In the "AD Users and Computers" MMC, if I right click on one of the > workstations and select "Manage", after about 40 seconds of Hourglass, I > get > the error message "Computer\\computer.mydomain.edu cannot be managed. The > network path was not found." > > > > For troubleshooting purposes, the firewalls are all turned off. > > > > I can ping the workstations by name and the ping shows the correct IP's. > If > I try to connect using "Net use x: \\computer.mydomain.edu\C$", I get the > "network path not found, however if I do the same from another workstation > in > the Domain the connection works perfectly. > > > > The two servers however can manage each other. > > > > Anyone have any suggestions as to what I should be looking at? > > > > Domain Admins group is a member of Local Admins group on each workstation. >
Guest Jim at SDSU Posted July 31, 2007 Posted July 31, 2007 Re: Can't remotely manage workstations "Danny Sanders" wrote: > > In the "AD Users and Computers" MMC, if I right click on one of the > > workstations and select "Manage", after about 40 seconds of Hourglass, I > > get > > the error message "Computer\\computer.mydomain.edu cannot be managed. The > > network path was not found." > > > > > Usually path not found error in AD mean DNS are not setup correctly. > > AD MUST have a DNS server setup to host the DNS zone for the AD domain. NOT > your ISP's DNS. > In the properties of TCP/IP on the computer having the problems, what server > does it point to for DNS? > The DNS is on the servers that can't manage the workstations and appears to be working properly. I can ping the workstations by name and it resolves properly, either from the server or another workstation. That is one of the things that makes this soooo frustrating. Everything "appears" to be working, and if there is a setting that isn't "vanilla", I don't know what it is. I haven't set up any Group Policies yet, or done any "tuning" yet, I'm just setting the Domain up and haven't gotten to that part yet.
Guest Danny Sanders Posted July 31, 2007 Posted July 31, 2007 Re: Can't remotely manage workstations > In the "AD Users and Computers" MMC, if I right click on one of the > workstations and select "Manage", after about 40 seconds of Hourglass, I > get > the error message "Computer\\computer.mydomain.edu cannot be managed. The > network path was not found." Does this happen from both servers to the same workstation(s)? Both servers to different workstations? or is it just happening with one server? hth DDS "Jim at SDSU" <JimatSDSU@discussions.microsoft.com> wrote in message news:DBAD1F86-F090-4C89-B651-37CAB7E652B5@microsoft.com... > Help!! > > > > I have a new Domain with 2 2003R2 servers and 3 XP Workstations and 1 > Vista > workstations installed as a test. The install is still "vanilla" meaning I > haven't set any custom GPO's etc yet. > > > > In the "AD Users and Computers" MMC, if I right click on one of the > workstations and select "Manage", after about 40 seconds of Hourglass, I > get > the error message "Computer\\computer.mydomain.edu cannot be managed. The > network path was not found." > > > > For troubleshooting purposes, the firewalls are all turned off. > > > > I can ping the workstations by name and the ping shows the correct IP's. > If > I try to connect using "Net use x: \\computer.mydomain.edu\C$", I get the > "network path not found, however if I do the same from another workstation > in > the Domain the connection works perfectly. > > > > The two servers however can manage each other. > > > > Anyone have any suggestions as to what I should be looking at? > > > > Domain Admins group is a member of Local Admins group on each workstation. >
Guest Jim at SDSU Posted July 31, 2007 Posted July 31, 2007 Re: Can't remotely manage workstations Both servers to the same workstations. Someone has suggested an invalid AD Registry entry, but neither she nor I am sure what valid AD Registry values would be. This is acting like DNS isn't working, but it is. "Danny Sanders" wrote: > Does this happen from both servers to the same workstation(s)? Both servers > to different workstations? or is it just happening with one server? > > "Jim at SDSU" <JimatSDSU@discussions.microsoft.com> wrote in message > > The two servers however can manage each other.
Guest Jim at SDSU Posted August 1, 2007 Posted August 1, 2007 Re: Can't remotely manage workstations OK, I got KB314980 and went into the registry and set logging to"4" "verbose" for a number if items like "Name Resolytion", "LDAP Interface Events" etc (From the Kb, they were items 2,7,8,11,13,16,22,23) and cleared the "Directory Service" log (after checking it). Then I tried to "Manage" one of the workstations I can't connect to. I got a number of "normal" entries like "LDAP search completed in 0ms" and reguests for replication. The only "Error" mesage I got was: "8/1/2007,2:34:28 PM,NTDS LDAP,Information,LDAP Interface ,1139,NT AUTHORITY\ANONYMOUS LOGON,MY_SERVER,Internal event: Function ldap_search completed with an elapsed time of 0 ms. 8/1/2007,2:34:23 PM,NTDS LDAP,Warning,LDAP Interface ,1216,N/A,MY_SERVER,"Internal event: An LDAP client connection was closed because of an error. Client ID: 3680 Additional Data Error value: 995 The I/O operation has been aborted because of either a thread exit or an application request. Internal ID: c0602ef" 8/1/2007,2:34:23 PM,NTDS LDAP,Information,LDAP Interface ,1317,N/A,MY_SERVER,"Internal event: The local domain controller has disconnected the LDAP connection from the following network address due to a time-out. " I've searched the Knowledge Base for the event ID, but can't find anything. Anyone have any idea what this means?
Recommended Posts