Have you run DCDIAG and NETDIAG with no problems?
Cheers. From: Erik Goldoff [mailto:[email protected]] Sent: Friday, March 20, 2009 12:31 PM To: NT System Admin Issues Subject: RE: Network path not found, error 53 no one ??? bueller .... bueller .... bueller ... Erik Goldoff IT Consultant Systems, Networks, & Security ________________________________ From: Erik Goldoff [mailto:[email protected]] Sent: Friday, March 20, 2009 10:42 AM To: NT System Admin Issues Subject: Network path not found, error 53 Got a weird one ... very small business, one domain controller, W2K3r2, SP2 ... had a power outage a few weeks ago where even UPS ran out so hard power down ... existing machines on the domain continue to login and access previously mapped shares, but unable to add a new XP box to the domain ... When trying to add the new box to the domain, error 53, network path not found is the primary message. No relevant errors in the event log on the server either. I brought in a spare box, with W2K3r2 installed with the intention of promoting it to a domain controller, but also couldn't join it to the domain ... same error. Also, from the new boxen, doing NET VIEW /Domain:domainname yields same type of error When I promote the spare server to a DC in a new domain, new XP box joins that just fine ... On the original DC, I see no DNS errors, ping resolves server name just fine and resolves netbios name to fqdn ... Any ideas on what may have FUBAR'd here ? ( and no, they didn't have a backup ! ) Erik Goldoff IT Consultant Systems, Networks, & Security ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
