why is Windows network system Rubbish?

Having a muck around before I go out because I had a problem with Reflect backing up to my NAs, for some reason the share path don't exist any more, and yet according to the NAS setup config , it does. Then all of a sudden it did exist, now for some strange reason it says about too many log ins.
I hate Windows network

The 'too many logins' is probably down to some latent caching or holding over existing connections on the UI on the NAS to be fair.

In reply to a post by Pheasant:

The 'too many logins' is probably down to some latent caching or holding over existing connections on the UI on the NAS to be fair.

er. How do I solve that?

Never had any problems with my NAS, but I use Robocopy in a batch file. Never fails to work. Been doing this since Windows XP, currently on Windows 11 Pro.

For full device backups, I use Veeam backup. I've never used Reflect so can't really help, sorry.

Just a hunch. Are there any options in your backup software that are possibly holding the connection / share to the NAS open after it completes its thing?

In reply to a post by zyborg47:

er. How do I solve that?

Doesn't sound like a Windows networking design issue, it sounds like an implementation issue on the NAS probably how the manufacturer has configured the Linux Samba program. Not an issue I've hit on my Synology kit.

(If you think SMB/CIFS networking is problematic, just play with NFS !).

In reply to a post by zyborg47:

In reply to a post by Pheasant:

The 'too many logins' is probably down to some latent caching or holding over existing connections on the UI on the NAS to be fair.

er. How do I solve that?

What NAS are you using?

In reply to a post by Michael_Chare:

In reply to a post by zyborg47:

In reply to a post by Pheasant:

The 'too many logins' is probably down to some latent caching or holding over existing connections on the UI on the NAS to be fair.

er. How do I solve that?

What NAS are you using?

Terramaster f4-210

In reply to a post by Pheasant:

Just a hunch. Are there any options in your backup software that are possibly holding the connection / share to the NAS open after it completes its thing?

I will have to go through the back up software bit by bit, and see. I also use allsync to sync my documents folder to the nas as well, not sure if that is causing the problem, it does a sync when files are changed, maybe I should set that to do it at a certain time or when the computer is turned on.
I wonder if I should use the I.P address of the nas instead.


I also had the error when using Windows, but that seemed to have sorted itself out now.

Strange that a friend of mine never gets these errors with the network I helped her with, She is using fibre, but I doubt that make s a difference.

In reply to a post by jchamier:

In reply to a post by zyborg47:

er. How do I solve that?

Doesn't sound like a Windows networking design issue, it sounds like an implementation issue on the NAS probably how the manufacturer has configured the Linux Samba program. Not an issue I've hit on my Synology kit.

(If you think SMB/CIFS networking is problematic, just play with NFS !).

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.

i need to watch some videos and look at some documents about networking. things have come a long way since the old coax days and BNC connectors

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.