"System error 67 has occurred." thrown on 2003 server
Hello all. About to jump out a window here. I'm working on a server - which has been working fine for quite some time - and I suddenly can't get the drives to map to our file server. This is 2003 server that is the domain controller. If I try to map the drive using the little window's wizard I get a "The drive could not be mapped because no network was found." error. If I go to the command line and try "net use x: \\fileserver\shared" I get the "System error 67 has occurred." error. Now, if I try "net view \\fileserver" it shows me all the shared drives! I can also ping the server both by name and ip address. All client computers and another server can all access the file server without issue. Any thoughts? TIA.
September 12th, 2012 10:00am

read this: http://support.microsoft.com/kb/875441/en-us http://support.microsoft.com/kb/843156/en-usMarco Adamo
Free Windows Admin Tool Kit Click here and download it now
September 12th, 2012 10:10am

I've already tried these and they didn't help. I upped my LmhostsTimeout to 20 seconds (although the error is thrown instantly) and disabled the IP NAT. Restarted several times since then. Can anything be assumed since I'm able to net view and ping the file server fine but cannot otherwise "see" it from the DNS server?
September 12th, 2012 10:43am

Hi, I would like to know do you have Symantec Endpoint Protection 11.0 installed recently, I would like suggest you refer to the below link: http://www.symantec.com/business/support/index?page=content&id=TECH102742&locale=en_US As we can see, the mapped drive worked fine before, so it seems like that you have done something with you server recently, I would like suggest you remove those apps you installed recently and check the result. Regards, Yan LiYan Li TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
September 17th, 2012 3:55am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics