NAS won't connect properly when using wifi

[Salazaar]

Hope someone can give me some help/thoughts on this:

I've got a Zyxel NSA310 NAS attached by ethernet to my Virgin Superhub 3 and when my PC is connected by a powerline connection I have no problems seeing and accessing the NAS.

But I changed the powerline connection to my PC (NAS is still wired) to a wireless connection (because the powerline connection was really flaky and drops out quite a lot) and the NAS no longer appears in the windows network folder and the network drives I've set up no longer connect.

However, I can still connect to the admin page for the NAS through my browser and see the Twonky Media Server instance that's running on the NAS from Windows.

Anyone got any idea how to restore full connection to my NAS without dropping back to the powerline link?

[SUMMONER]

Have you tried temporarily turning off your computer firewall (just to see if the problem goes away)? It is most likely applying a more restrictive security policy to the wireless network than it is to your Ethernet connection.

[Salazaar]

Just tried that an apparently no joy!

[SUMMONER]

Can you see the NAS network shares by typing \\nasipaddress (eg: \\192.168.1.10) into the address bar of Windows File Explorer?

[Salazaar]

That's very interesting... Yes, I can see all the folders I'd expect to see when I go in like that!

[SUMMONER]

Can I assume that you have rebooted all 3 devices (the computer, NAS box and router?)

Try setting your wireless connection to be a "home" network, instead of public/work...

[Salazaar]

Yes to rebooting.

Windows 10 doesn't seem to have the same options as 7 but I've checked and the network is set to private rather than guest or public so I assume that's similar.

At least being able to access the shares/folders means that I can set up new network drives to point at the important files - shames it's not as easy as before though. I think others have had similar issues with Virgin Media superhubs.

[SUMMONER]

hmmm...

How about a work around?

Go to C:\Windows\System32\drivers\etc and open the file hosts in notepad

add the following entry to the bottom of the file

NASipaddress NASboxhostname (eg: 192.168.1.10 nasbox)

Notice that in Windows 10 you will likely have to give your current user permission to write to the hosts file before you can overwrite it.

[Salazaar]

That seems to have fixed it! Thanks!

[SUMMONER]

Try "pinging" the hostname (not the IP address) of the NASbox from another WiFi connected computer/device. If that does work it is likely the Windows/Internet Security software on your main PC that is causing the issue, not the VirginMedia router. Alternatively boot a Linux CD/USB stick and see if it works correctly in there.