Sounds like maybe the laptop doesn't have SMB1 client enabled perhaps?

@Jase2985 et al .... yep, thanks all, using \\192.168.x.x gives me the NAS Files on the laptop now 😁

Presumable I just now need to change the name or create a shortcut to have it showing all the time.

     >Sounds like maybe the laptop doesn't have SMB1 client enabled perhaps?<

That I had previously checked and turned on.

Wasn't this something ye olde hosts file used to sort out?

@kiwifidget ... my next step was to put the IP into the Hosts file ... may still need to to ensure NAS shows up in File Explorer by default?

To tidy this all up, I can access the NAS using laptop by entering IP address into File Explorer.

So why doesn't the NAS show up under Network when I open File Explorer at a later time?

Rickles:

 

So why doesn't the NAS show up under Network when I open File Explorer at a later time?

 

because windows

i cant see one of my windows computers that has a network share at the moment. it might show later, it might not.

just map it as a drive or create a shortcut to it on your desktop

This may sound obvious but when you have the NAS open in File Explorer have you gone through the process of mapping as a Network Drive?

@cshwone ... oh yes, tried both mapping as network drive and as adding network location .... neither works.

These were discoverable using SMB1 but as it is insecure we have been told not to use it. And therein lies our problem.

But you can map the NAS e.g. typing "\\WDMYCLOUD\Public" works here.

linw:

 

These were discoverable using SMB1 but as it is insecure we have been told not to use it. And therein lies our problem.

 

But you can map the NAS e.g. typing "\\WDMYCLOUD\Public" works here.

 

I only learned this the other day and it really surprised me, given the strength of the messaging from Microsoft to STOP USING SMB1!

To be crystal clear for anyone else who was confused like me: the thing that makes Windows/Samba shares pop up in Explorer is a feature of SMB1, an ancient protocol which is riddled with insecurities. New protocols (SMB2, SMB3 and SMB4) have replaced it but for some reason they didn't include network discovery. If SMB1 is disabled on either the server or the client, the server won't show up in Explorer and will only be accessible by typing in the \\hostname or \\IP address. This is apparently expected and intended - Microsoft thinks that this isn't a feature that anyone needs or wants anymore.

If you do want or need that feature, you need to enable SMB1 (against official Microsoft advice) at both ends. Or if the server you're trying to access is running Linux (i.e. Samba), there is a little service called WSDD that you can run that restores the network discovery feature without needing SMB1. I think some NASes actually have this built-in so might be worth checking your settings.

Bit of a fail by Microsoft in my opinion, because I'm sure that, like me, many people saw their server failing to appear in Explorer after turning off SMB1 (or rebooting after the automatic update that turned it off) and assumed that something was broken.

@allio .... brilliant, great ... thanks for that.

What I find odd though is that the desktop shows the NAS under This PC/Network, whereas the laptop doesn't.

I've checked that both have same SMB settings, etc

To piggy back on this discussion.

I recently upgraded to from Win 7 to Win 10. Win 10 will not/can not remember the NAS access password. Every time after a restart the NAS shows as connected to the network but I have to re type the password in. Yes I have ticked "Remember My Credentials". I've even gone into the Credential Manager and entered the details there.

I've tried mapping the folder I need from the NAS as network drive which I've been able to do successfully but the next time I restart there seems to be a conflict with that network drive and the network connection to the NAS.

Any ideas?

Rickles:

 

     >Sounds like maybe the laptop doesn't have SMB1 client enabled perhaps?<

 

That I had previously checked and turned on.

 

You should disable SMB1 - for security reasons.