System Error 67 Has Occurred
I am running Windows 2000 Server SP4 and I recently purchased a Buffalo Tech TeraStation Pro 2 NAS. I have followed the instructions in the install guide, but cannot connect to a shared drive on this device. I have been working with Buffalo's tech support and they suggested trying to connect to the NAS via another PC. I did this successfully with an XP laptop using the Buffalo NAS Navigator Utility. This same utility does not work on Windows 2K Server.
I have a service running, on windows Server 2008 R2, which requires access to a webdav mapped drive, for copying file dependencies. Everything works when I run net use from command prompt: net use. Basic Info I'm running Cryptomator on: Windows 10 Pro Anniversary, Version 1607 Build 14393.351 I'm using Cryptomator in version: 1.2.0 Description A vault that that could be mounted successfully in the past suddently stopped working. The network name cannot be found. I can ping the server we are trying to map too just fine. I can also run the mapping command using the FQDN of the server and it will map(net use x: servername.domain share.
System Error 67 Has Occurred Network Name
Buffalo says that there is an incompatibility issue with it, so they recommended using the 'net use' command to map the NAS using UNC. I've tried this and receive a 'System error 67 has occurred.' I've looked all over the place on the web for an explanation of this error, and everything seems to point to some sort of DNS or NetBIOS issue. I'm not an expert at all with Windows networking, so I am not sure how to resolve this.Here is a brief overview of how I'm connected:Win2K server (192.168.0.111) vD-link Router (192.168.0.1)^ NAS (192.168.0.126)Subnet mask for all is 255.255.255.0Any help would be appreciated!Thanks,Scott. Can you ping the device when it's on the network?
If not you need to address that in the setup of the device.If you can then can you get to the shares by usign the IP address?192.168.0.126If not then try to go 1 level deeper.192.168.0.126sharenameIf you STILL can't get to it then you will need to look at the setting of the shares and teh overall permissions of the device to make sure it's advertising the shares.The 67 error is saying that it can't find a device by that name. So it has to be naming or something blocking it.Once you get to the point where you are able to get to the device then you can add a DNS entry to your server that will point to the NAS box by name.Best of luck. I had a similar experience with my TeraStation Live. I could ping the TeraStation by it's DNS name or ip address just fine, I could login and manage the device through my web browser, etc. but any time I tried to map a drive, through the GUI or a DOS prompt, I would get the System Error 67 or System Error 5.After some plugging around with different mappings, it was acting as if I had already connected with other credentials. It seemed to be an issue with the built in Guest account on the TeraStation trying to authenticate before the account I created could.
The NAS does not have a password for the Guest account that I can find, however when I attempt a Net Use from Windows it asks for one and will fail when a blank password is provided. So I figured purposefully providing bad credentials for Guest account might work.So I did this at a DOS prompt:net use: /user:guest guestWhich would fail as expected, then I typed:net use: /user: And I was attached successfully.