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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2010-01-24T16:27:28+00:00

    Hi, John,

    cannot get the software to recognize the mapped drive when trying to access the folder in scheduled mode.

    You mean, when running as a scheduled task ?

    This is a classical issue due to the fact that scheduled tasks don't run with the same "user" as when you are connected. So shares (drive letters) are not "connected" then, and any access to drive letters will fail. To fix that, you have to access shares via UNC (\server_name\share_name\folder) instead of mapped drives (letter:\folder), and for that connection to succeed, the username/password pair under which the task runs has to match the same pair defined and allowed on the server. You'll find similar issue and explanations on the net, e.g. http://www.eggheadcafe.com/software/aspnet/32130764/scheduled-task-can-not-ac.aspx

    If my understanding of your problem is correct, it is not the issue this thread is about nor linked to win7 or wireless. It's just so by design for security reasons.

    Best regards,

    Vicne

    Was this answer helpful?

    0 comments
  2. Anonymous
    2010-01-24T16:35:21+00:00

    I can’t get the laptop to ‘see’ the NAS Drive properly, ie I can’t access the drive’s admin software using either the WD discovery software provided or the IP address of the Drive. The WD software tells me that the drive isn’t there or is not connected properly and internet explorer fails to contact the device’s web page via the IP address. However, I can see the ‘MYBOOKWORLD’ icon in the displayed network connections on the laptop and I can map network drives under windows explorer and I can, apparently, copy files to and certainly see any files that are in folders on the NAS drive. The issue is I can’t access any of the files on the drive from the laptop. As soon as I try to open a file, even one I copied to the drive using the laptop, Windows explorer freezes up.

     

    I have tried many things – switched off all anti-virus software and firewalls etc, tweaked a registry key to reduce security levels (as suggested by many posts on various forums), connected the laptop with cable to the router and even spoken to WD support (who were not particularly helpful – just said if it’s working on the one machine it can’t be a problem with the drive!), all to no avail.

    Hi, Chris,

    Just to make sure we speak about the same problem :

    • what is the exact error message Windows Explorer gives after freezing (if any)
    • can you confirm you have no problem browsing folders ?
    • once connected via cable, does the problem still occur ?

    If so, I would be tempted to think it is more a question of rights on the NAS that allows listing dirs but not opening files...

    Best regards,

    Vicne

    Was this answer helpful?

    0 comments