Question Locked

System error 67 has occurred connecting to NAS

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

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. 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)
|
v
D-link Router (192.168.0.1)
^
|
NAS (192.168.0.126)

Subnet mask for all is 255.255.255.0

Any help would be appreciated!

Thanks,

Scott

11 replies

by bart777

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.126\
If not then try to go 1 level deeper.
\\192.168.0.126\sharename

If 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

by scott.917

Yes, I am able to ping the device. I've tried using \\192.168.0.126 and \\192.168.0.126\share, but I get a different error that says the network cannot be found.

On Win2K server, I'm not sure what settings I can check to see whether something is blocking that IP from getting mapped.

Thanks,

Scott

by usit

that 0.126 is not in the dhcp pool, do a ping with the -a switch, you could be pinging a different machine.

Next step would be permissions, I have a terastation pro and had similar issues.

by scott.917

I tried the ping command, no luck.

Which permissions do I need to check?

by scott.917

I did the "ping -a " and it came back fine.

I'm curious as to which permissions I need to check.

Just as another test, I shared a folder out from the Win2K machine, and tried to map it on the XP laptop. I got a message stating the network could not be found.

Scott

by usit

on the shares on the buffulo. I would think that if you can't even get to a share on the server then you have a firewall or network issue. Is it only with this one laptop? Have you tried a a different pc?

by chilidog67

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 guest

Which would fail as expected, then I typed:

net use : \\\ /user:

And I was attached successfully.

by scott.917

Thank you for that information! I will try that tonight!

Scott

by scott.917

Tried that, and still no luck.

Thanks for the suggestion, though.

Scott

This discussion is closed to new replies.