Windows 7: Cannot access *some* folders on a Network Drive(NAS) via wireless connection

Anonymous
2009-10-24T19:04:36+00:00

I have recently installed Windows 7 Home Premium on my 2 Desktop PCs at home. They are connected via ethernet to a router. Also connected to the router is a Network Attached Storage device (a Buffalo Linkstation Live). From these PCs I can access files and folders on the shared drive with no problems (for example, I can access the folder \MyNAS\Share\Downloads).

However, on my laptop that connects wirelessly, while I can *see* all the folders on the NAS I can only access a few. For instance, I can see "\MyNAS\Share\Test" (which is an empty folder I created) but if I try to access "\MyNAS\Share\Downloads" it waits for a bit then tells me "\MyNAS\Share\Download is not accessible. You might not have permission to use this network resource. The specified network name is no longer available." Previously the laptop was running XP and I had no problems.

There are no passwords required to access the NAS. I have tried setting the network to both "Home" and "Work". I have tried enabling and disabling HomeGroup. The laptop can access shared folders on the other PCs.

I assume this is something related to wireless security? Please help!

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2012-06-11T10:19:53+00:00

Hi Kaylamarie12,

I had exactly the same issue with windows 7 not connecting wirelessly to my NAS, however there were no issues with a wired connection.

This is the only solution that worked for me (I think it has been suggested by Piptech earlier).

First start an administrator console by entering cmd into the searchbox on the start menu and then do ctrl+shift+enter instead of just enter. In the console enter the following commands to change the MTU:

netsh interface ipv4 show interfaces

Take note of the id number of the wireless interface.

netsh interface ipv4 set subinterface id mtu=1460 store=persistent

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2010-02-25T09:42:41+00:00

This took me months to find, but the answer is:-

============

First start an administrator console by entering cmd into the searchbox on the start menu and then do ctrl+shift+enter instead of just enter. In the console enter the following commands to change the MTU:

netsh interface ipv4 show interfaces

Take note of the id number of the wireless interface.

netsh interface ipv4 set subinterface id mtu=1460 store=persistent

This worked for me. Apparently it has to do with the wireless router (mine is a Thomson 780WL) not correctly dealing with the default mtu of 1500. There is no need to change the fixed cable interface, that works without problems, it's just the wireless interface that doesn't connect without this modification. More info can be found in this thread towards the bottom  Hope this helps!

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2010-01-31T13:45:58+00:00

Before I bought Win 7 I used Win Xp and had no problem whatsoever to connect to my NAS through the Speedtouch. So, there seems to be something regarding the combination Speedtouch and Win7. But, as I stated before - a new firmware for my Speedtouch fixed it all.

Olly - are you sure you're using the latest firmware for your 716? Sometimes internet service providers keep old "custom made" firmwares just for their convenience. I've seen firmware v6.2.17.5. Is it the one you have?

Gust+

Was this answer helpful?

0 comments

79 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2009-10-28T16:05:40+00:00

    In case it's useful, the laptop (well, netbook really) is an Advent 4211c, which is the same hardware as the MSI Wind U100, and my router is a Thomson Speedtouch 716, provided by my ISP.

    Anyone have any ideas?! It's doing my head in!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2009-10-26T10:18:25+00:00

    Hi Savan. Thanks for the reply.

    Didn't work I'm afraid. My results:

    Step 1: I tried this with the "Downloads" folder. Obviously I had to do it from one of the other machines - if I right click to access Properties on the laptop then I have the same error message as above ("\MyNAS\Share\Download is not accessible. You might not have permission to use this network resource. The specified network name is no longer available.") When try to do Point 10 I get the message "Unable to set new owner on Downloads. Access is Denied." Is this because the folders are on the NAS and therefore I can't change permissions using Windows? Note: I do not have any passwords set up for any user accounts - could this be causing a problem?

    Step 2: I get the same error "\MyNAS\Share\Download is not accessible. You might not have permission to use this network resource. The specified network name is no longer available."

    Step 3: Still get the same error.

    As I said, the other 2 PCs can access all the folders fine, and EVERY computer has a clean install of Windows 7 on. The only difference is that the laptop connects wirelessly, and it is running Windows 7 32-bit, but the other computers are running 64-bit. Surely the problem must be related to one of these things? Before, when the laptop was running Windows XP 32-bit I had no problems.

    More info: I have just checked, and if I connect the laptop via a wired connection (instead of wireless) then it works perfectly.

    OK, weird: I created a test folder and put one file in it, and could access the folder fine via wireless on the laptop. I gradually increased the number of files in the folder, and at about 8/9 I receive the same error as before. Could it really be to do with the size of the folder I'm trying to access? Or perhaps related to resolving names across the wireless network?

    Was this answer helpful?

    0 comments