NAS access issues -- please help :)

[rage_311]

Hey everyone...

I am having a strange issue that I've been scratching my head about for a few days. I have a D-Link DNS-323 NAS on my network. I have two computers, an xbox, and ps3 that can all access it perfectly. I have ONE computer that suddenly cannot. I can't think of anything I've changed, it just stopped being able to access it about a week ago.

Symptoms:
Even though I can access the "root" of the network share (\\D-linknas\) and see all the items in there (ie shared printer, bittorrent folder which is built in to the unit, shared folder, drive root folder, etc.), I can't get into the shared folder or the "drive root" folder (\\D-linknas\Volume_1\). The shared folder is shared to EVERYONE (SMB) with no credentials required while the Volume_1 requires credentials. I CAN get into the bittorrent folder, the shared printer, and the web interface folder that contains the webpage. I can't access the web interface (using any browser) and can't login to the ftp server either. I can get to other computers' shared files just fine and I can access the web just fine. Again, all these issues are on one computer only...

I've tried uninstalling and reinstalling the client for microsoft networks client in the LAN connection properties. I don't know what else to try. Any thoughts? Need any more details? Thanks in advance!

Matt

EDIT: I forgot to add the error message when I try to access either the shared folder or the volume_1 folder (it's pretty standard though). "\\D-linknas\Shared is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The specified network name is no longer available."

 

[thiggins]

Can you access the NAS by its IP address? (\\IPaddress_of_NAS).

I assume you've run the Windows connection repair?

Try going to My Network Places and deleting all of the shares there.

 

[rage_311]

I can access it by the ip address (\\192.168.2.101) and it lists all of the shares on the device, but I can do that successfully with the name as well. Once I'm viewing the shares through that method, I get the same problem if I try to go to the "shared" folder... The window stops responding for about 2 minutes, then it pops up with the "You might not have permission to use this network resource" error.

I have tried the windows connection repair also, as well as several reboots. I've tried installing SP3, in case it was a windows bug of some sort. I've also flushed the dns (ipconfig /flushdns), refreshed netbios names (nbtstat -R and nbtstat -RR), reset the TCP/IP config (netsh int ip reset resetlog.txt)... I've even done a system restore to a point when I know it was working.

I tried your suggestion of deleting the shares in my network places. Still no luck!

Thanks for the suggestions! Any other thoughts on this?

 

[rage_311]

Ah, it seems that I have neglected one important detail that seems to be the root of the problem. This PC used to be on a wired connection to the router and the NAS was on a wired connection to that same router. Now I've moved the PC to a different room and connected it to a wireless ethernet adapter. I brought the PC back into the router's room and hooked it directly into the router again, and instantly I was able to connect to the shares again. Is it possible that something is retaining the incorrect routing information from when it was on a wired connection? I've unplugged and re-plugged the power on all devices involved... still nothing. What could be the issue??

I'm using a TrendNet TEW-633GR wireless router, by the way. It has a feature called NetBIOS announcement that's been disabled this whole time. Could that help? This is quite frustrating. Thanks for any help!

 

[rage_311]

Oh man...

Well, I solved it. It turns out the connection was having some issues because I had jumbo frames (9000 bytes) still enabled on that NIC. I put that setting back to 1500 and it's working like a charm! Just thought I'd give you all an update in case anyone else experiences this. Thanks for the help.

 

[thiggins]

Thanks for posting the fix. Glad you got it sorted.

 

[cdrsteve]

Oh man...

Well, I solved it. It turns out the connection was having some issues because I had jumbo frames (9000 bytes) still enabled on that NIC. I put that setting back to 1500 and it's working like a charm! Just thought I'd give you all an update in case anyone else experiences this. Thanks for the help.

Thanks for sharing. Great info and one to remember!

r/Steve