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-29T21:24:57+00:00

    ..and one firmware update (of my Speedtouch 780WL router) later everything works just fine! I can now access all my shares and all my files.

    /Gust+

    Was this answer helpful?

    0 comments
  2. Anonymous
    2010-01-30T23:43:01+00:00

    EDIT: The first part of this is WRONG! Please see my edit at the end. I've just fixed this on my laptop having had exactly these problems on Win7 home premium on my Dell Studio SXPS16. The XP partition on the laptop, and other machines, had no problems accessing my NAS devices, but the Dell supplied Win7 Home Premium, while it could see them, couldn't drill down without losing the connections. Tried ALL the previous suggestions on this and other threads, mapping the drive in a DOS box, addressing it via its IP address etc etc.

    I checked the Intel site, and found theres an 'update' there for the 5100 wireless card series dated 7th Jan 2010. The current driver supplied by Dell/Microsoft for the 5100 adaptor is dated Sep 2009.  I deinstalled the adaptor in device manager (which I found necessary to do to allow the Intel software to actually do the installation. ) When the installer had run (it wanted a reboot), the driver was one dated MARCH 2009, version 12 rather than 13! And now the shares all work and I can map drives from Win 7 and work with the data on the NASs.

    Prior to this I'd done several virgin Win 7 installations on this machine to see if I could see if there was anything odd about my installation.

    Clearly Intel messed up the version  of the driver  that's on the MS win 7 disk and Dells current download site, and from comments here, there may be other wireless  network adaptors with the same issues

    Here's the link on the Intel site to the driver set that worked for me, but do deinstall the adaptor in device manager , before you do the installation since otherwise it doesn't seem to actually run  and the driver is not downgraded:

    http://downloadcenter.intel.com/Detail\_Desc.aspx?agr=Y&ProdId=3062&DwnldID=18240&lang=eng.

    EDIT: I wrote this after a long night attempting to get this going again. But it's a load of nonsense I'm afraid. It's NOT the laptop card driver, but it IS as was suggested by Gustplus above,  the router that the system normally connects to. I have 2 wireless repeaters in my house, and accidentally  forcing a connection to the other one, a Buffalo Airstation, is what makes the SMB work from Win7. The Speedtouch 585 I use for wireless and my ADSL connection is the culprit when running WIn7's SMB over wireless from the laptop. Trouble is , I don't want to update the firmware since I'm running the last versionof the 585 f/w that was hackable to allow forcing the SNR for optimum ADSL speed. So I shall just have to ensure that the Win 7 laptop only connects to  the Airstation. Very wierd, and even wierder when the Speedtouch has no problem connecting the same laptop to the NASs when I am running XP on it...

    Incidentally, this issue only affects SMB. There is no problem with anything else running tcpip from the Win7 laptop into the Speedtouch.

    Was this answer helpful?

    0 comments