Ok, right, I took off version 1 of SMB, not sure if that will make a difference, but I put a shortcut to get to the shared drives of the NAS on quck access, so that works.

Reflect have just made a backup of Windows and it worked fine, no problem at all this time. Allsync works fine all the time, but that uses FTP.

I have looked at all the settings of reflect and my NAs and there should not be anything there
to cause a problem.

In reply to a post by zyborg47:

I wonder if it is anything to do with hagving SMB version 1 enabled on my computer? The problem is without version one, devices on the network don't appear on windows.

SMB version 1 is very old and has a whole bunch of security issues, so MS recommend it is no longer used. The have the option to re-enable so you can still make a "drive mapping" (MS & IBM terminology) or "mount" (Novell / Unix terminology) to a machine running Windows 95/98/ME/2000 or earlier. Some NAS devices don't get firmware updates to the embedded Linux software so need SMB 1 as they pretend to be ancient Windows.

SMB 1 does not normally impact the "Network Neighbourhood" concept, but this has always been an issue when people install security software on PCs as the security software always blocks the technology.

A couple of decades ago I learnt all about Netbios-over-IP and browse masters and similar, but to be honest, if you have a handful of machines just set up shortcuts to the IP based UNC e.g. \\192.168.0.15\data

Name to IP resolution is complicated because none of us run our own DNS or WINS servers at home. Some routers let you set up names when using DHCP reservations, and then return this if the router is used for DNS, but many people override this.

Depends what you want and how much effort you want to put in.