I am having as similiar problem.  I am using Windows backup pro for windows 7 and cannot get the software to recognize the mapped drive when trying to access the folder in scheduled mode.  I can run the program manually but it cannot see the drive otherwise.  I have tried changing security of the network drive but I am not allowed.  I have tried the registry fix take control of but I still cannot get a security access to any folder on the NAS which by the way is a LG N4B1 with Blu-Ray drive.  I can read and write to the network manually but I really need to have scheduled access.

I had an initial problem with Windows Media Center but was able to solve it with a script program.

I hope someone can identify on how to fix this security access issue.

John C

To all:

There's some basic things we have yet to go over:

• Are you running an antivirus/software firewall? If so, have you tried disabling it or uninstalling it?
• Have you tried booting into Safe Mode to see if the issue still occurs there? (See the following link for instructions: http://windows.microsoft.com/en-US/windows7/Start-your-computer-in-safe-mode )
• If the issue doesn't occur in safe mode, try a clean boot (Follow the Vista instructions located here: http://support.microsoft.com/kb/331796 )

Hello, Cody, and thanks for taking care of this problem,

As for your questions :

a) I'm running AVG free. Tried disabling it, to no avail.

b) I tried safe mode (with networking enabled of course), but the issue is still there.

I guess (c) is useless as issue still occurs in safe mode

Since my last post, the Atheros Wifi driver has been updated (windows update) but nothing changed.

Just to re-focus the thread, the symptom we got is not at the connection level (shares are found and do connect OK), but at the time of accessing the share's file listing in Explorer, *if it is not empty* : Windows waits for a long time (more than 2 minutes) then displays a message box saying "<share_path> is not accessible. You might not have permission to use this network resource. The specified network name is no longer available."

I performed more tests, and I'll try to summarize them hereunder.

First, here's the hardware I used for testing :

Netbook (Sony Vaio W with Atheros AR9285 wireless chipset), Win7 Starter

Laptop, Win 7 RC

Desktop, Win XP SP2 (wired), with a few shared folders

NAS synology DS109

Fonera+ Wi-Fi router

Netgear 8-port Gigabit Switch

What does not work :

Netbook > Fonera+ > Netgear > NAS > samba share with many files

Netbook > Fonera+ > Netgear > NAS > http access (new test)

What does work :

Desktop > Netgear > NAS > share

Laptop > Fonera+ > Netgear > NAS > share

Netbook > Netgear > NAS > share

Netbook > Fonera+ > Netgear > Desktop > share (new test)

Netbook > Fonera+ > Netgear > NAS > ping (new test)

Netbook > Fonera+ > Netgear > NAS > ssh **for a limited time** (new test)

So the case is clearly due to a combination many factors, but what is new is that samba doesn't seem to be the culprit. Shares are just the first connection to the NAS I tested, but the IP stack at a lower level seems to be affected.

So, to summarize with the different protocols :

Ping (very small packet) works

Samba with empty share (small quantity of info) works

Samba with many files (a few KB) does not work

HTTP (a few KB of HTML) does not work

SSH works until about 2KB of text has been received, then it hangs.

In the current state, I'd be tempted to think that under certain conditions, the fix mentioned by Bart Bowman (or another change between Win7 RC and release) has caused a regression that makes accessing a resource on a linux PC hang after a few KB have been exchanged over wi-fi.

Does it make sense ?

Vicne