Network Discovery Won't Stay Turned On

cloud_dog

Hi

I have had a search of the forum and Google but am still struggling with my NAS.

The problem is that the connections to my mapped drives on the NAS appears to be intermittent. I'm sure it has got worse more recently. Sometimes in the main Windows Explorer window the mapped drives have a big red X on them. If I double click I will get a error (unable to connect, although the error can vary). Sometimes even with the red X, if I expand the networked folders in the left hand panel I can navigate the folders / files ok.

Anyway, long/short.... 'Network Discovery' is turned off.

I have Googled the problem and mostly I get the information to ensure the below services are running:

DNS Client
Function Discovery Resource Publication
SSDP Discovery
UPnP Device Host

....and they are all running.

I've also come across information relating to checking/changing the firewall option of 'Allow an app or feature through Windows Firewall' but have been unable to identify what to do/add. Feel that if I resolve the Network Discovery to be on then the problem should go away.

I'm not sure what else to try to do. Any help, anyone?

AndyPix

This has been a "feature" of windows for a while now ..


It seems that windows checks for drive connectivity BEFORE network is established.
These two operations seem to be the wrong way round in order of presedence ..


You can try mapping using IP address rather than share name, and if it really bugs you then you can enable the GPO , "Always wait for the network at computer startup and logon" via
Computer Configuration/ Administrative Templates/ System/ Logon


That way, the computer should establish network connection first, but your logon time will suffer

Even with the big red x on them though, your mapped drives should still work

cloud_dog

AndyPix wrote: »

This has been a "feature" of windows for a while now ..


It seems that windows checks for drive connectivity BEFORE network is established.
These two operations seem to be the wrong way round in order of presedence ..


You can try mapping using IP address rather than share name, and if it really bugs you then you can enable the GPO , "Always wait for the network at computer startup and logon" via
Computer Configuration/ Administrative Templates/ System/ Logon


That way, the computer should establish network connection first, but your logon time will suffer

Even with the big red x on them though, your mapped drives should still work

Thanks for the prompt response.

As mentioned the whole thing is a bit 'hit n miss'. I have re-booted and now I cannot access the shares in any way / shape or action, even after waiting and disconnecting the share/re-connecting.

I'll try what you suggest but I think I had tried this without success. I'll confirm.

AndyPix

Ok, well can you ping the share by ip address ?


A workaround that i have used in the past is create a batch file to delete and re-establish the share.
Set this to autorun with delayed start and that should fix your issues,
Or have it sit on the desktop and call it "Fix shares" ..


Let me know if you need a hand writing such a batch file


Andy


Edit : Might be worth clearing the ARP cache aswell incase it has got its knickers in a twist
Open an elevated command prompt and type


arp -d *


and press enter


then, check the list is clear (apart from local host) by typing arp -a and pressing enter

cloud_dog

AndyPix wrote: »

You can try mapping using IP address rather than share name, ....

This doesn't work, although going down this route gives me a simple user credential error, i.e. it (NAS??) doesn't recognise my user name / password. Have tried any / all combinations of that but no joy.

cloud_dog

AndyPix wrote: »

Ok, well can you ping the share by ip address ?


A workaround that i have used in the past is create a batch file to delete and re-establish the share.
Set this to autorun with delayed start and that should fix your issues,
Or have it sit on the desktop and call it "Fix shares" ..


Let me know if you need a hand writing such a batch file


Andy


Edit : Might be worth clearing the ARP cache aswell incase it has got its knickers in a twist
Open an elevated command prompt and type


arp -d *


and press enter


then, check the list is clear (apart from local host) by typing arp -a and pressing enter

Hi

I tried the arp -d * and arp -a and the list shows two entries:
192.168.0.1 - Dynamic... (router obviously)
224.0.0.22 - Static.... (haven't a clue what this is)

EDIT: For info, if I ping the 224 it times out.

AndyPix

cloud_dog wrote: »

This doesn't work, although going down this route gives me a simple user credential error, i.e. it (NAS??) doesn't recognise my user name / password. Have tried any / all combinations of that but no joy.

Hmm, i think you need to address this first.
Mapping by IP rather than share name skips the need for DNS and will likely solve your issue especially if you give your NAS a static IP address rather than DHCP.


Did you not create a username password when you set up the box ?
If not, use google to find the defaults for your unit


Let us know

cloud_dog

The share I am trying to access has read only rights for any user.

My user is set up to add/delete but I am just trying to access at the moment.

cloud_dog

I've just mapped a drive to the share on my work's laptop (I WFH) and it connected through straight away (Windows 7....ahhhh god bless W7).

EDIT: Home PC on W10 btw

EDIT EDIT: Just re-mapped on work's laptop using IP address and mapped straight away (and this is also on the works VPN), if that makes any difference).

AndyPix

cloud_dog wrote: »

224.0.0.22 - Static.... (haven't a clue what this is)
.

Dont worry about that one, that's just the IGMP ..


https://en.wikipedia.org/wiki/Internet_Group_Management_Protocol

cloud_dog

DNLA stuff (Roku, Squeezebox, TV, etc, etc) works quite happily