Has a Windows 10 Update broken my shares? Test OK, backup fails.

[MadEngineer]

My backups are performed by the ReadyNAS device accessing remote shares on my desktop using the "remote: Windows/Nas (Timestamp)" option.  On my desktop I have a back up user created for this task and shares created for the folders to be backed up.

The error I'm getting is that the source cannot be mounted on the system.

This has been working perfectly up until maybe a week ago.  The test function for each back up job works.

I can only guess that a Windows Update has changed something?

When I perform a test, I can see a multple entries logged under Event Viewer for the backup user accessing the desktop however when running a backup there is no such entry.

System is running firmware 6.9.4 Hotfix 1

[StephenB]

Do you have another PC you can use to test access of the desktop network shares?

[doseas]

A recent Windows Update has disabled SMBv1 on systems that had it enabled.  You can either re-enable it (a security risk, but necessary if your network has older devices incapable of using SMBv2 or SMBv3), or switch all devices to a newer version of SMB.

See this article for more info:  https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows

[Sandshark]

But he shows a ReadyNAS 100 series, so SMB1 should not be the problem.  Many of us started having problems accessing the NAS via name after one of the updates.  So, if you are using the NAS name, try using the IP address instead.  There is no true solution I know of, though adding the NAS name to the Windows hosts file is a work-around if using the IP address does not suit your need.  Google is your friend for editing hosts.

[MadEngineer]

Thanks for the replies.  Without any change I've logged back in to the ReadyNAS today and found that the backups have since run with no problem.  Nothing has changed overnight