Buffalo Forums

Our company is using a NAS hs-dh500gl.
however, we are facing a problem that we can't access it from our Domain controller servers (they are using windows 2003 enterprise sp2 R2)
But it works well with the client computers.
From the servers, i still can ping with the ip and hostname as well as access it from the web settings but i can't access the shared folders. it always shows an error: ""the specified network name is no longer available"
Anyone has experience for this and help me to fix it?
Thanks for reading
i look forward to receiving the help soon

Windows servers generally have much more stringent Security Policies. More recent NAS devices acting as an iSCSI target are usually a lot less difficult to connect to with a server to than a standard SMB connection is.

Perusing google comes up with several things that might cause SMB connections -from- a 2003 server to fail, but I don't want to recommend registry hacks on your server :D

That said This Link (http://blogs.microsoft.co.il/blogs/dand/archive/2009/08/21/connecting-to-smb-share-on-a-windows-server-2003-based-computer-may-not-work-with-cname-alias-quot-access-denied-quot-or-quot-no-network-provider-accepted-the-given-network-path-quot.aspx) is on a Microsoft blog and while I do not suggest you do this thing, it might be an interesting read.

Thanks for your advice.
But nobody here was facing this issue before??
i suppose this issue should be popular in the enterprise environment as today???

Quote from: Eastmarch on July 26, 2013, 09:17:57 AM
Windows servers generally have much more stringent Security Policies. More recent NAS devices acting as an iSCSI target are usually a lot less difficult to connect to with a server to than a standard SMB connection is.

Perusing google comes up with several things that might cause SMB connections -from- a 2003 server to fail, but I don't want to recommend registry hacks on your server :D

That said This Link (http://blogs.microsoft.co.il/blogs/dand/archive/2009/08/21/connecting-to-smb-share-on-a-windows-server-2003-based-computer-may-not-work-with-cname-alias-quot-access-denied-quot-or-quot-no-network-provider-accepted-the-given-network-path-quot.aspx) is on a Microsoft blog and while I do not suggest you do this thing, it might be an interesting read.

i tried to do it too but it doesn't work. :(

Nobody else can help me this???

Spent a few minutes looking at google, and connecting to SMB shares from win2k3 server is not uncommon, I did see a few cases where the network connection did not have 'client for microsoft networks' bound to the NIC. Also saw some references to Antivirus software causing an issue, and also saw the Group policy setting

Network security: LAN Manager authentication level: Send LM & NTLM responses

as being necessary. This is all from a quick search. The NAS isn't the cause of the error, it clearly is serving files, it's this computer acting as a client that seems to be the issue.