ERROR_BAD_NET_NAME

Posts: 3 · jakeo25 27 Oct 2020, 21:47

Hello all,

I am using a FFS batch file to run a Windows 10 scheduled backup to a file server located at a fixed IP address, but consistently errors out. I can manually initiate the same batch file inside FFS with no problems

The error dialog is
"Cannot read file attributes of "\\192.168.200.80\home".
ERROR_BAD_NET_NAME: The network name cannot be found. [GetFileAttributes]

Any ideas of how to fix this?

Posts: 3 · jakeo25 27 Oct 2020, 22:10

Just a quick note: I found a pair of orphaned sync.ffs_lock files in the local and server directories in question. Would this masquerade as a "bad net name"?

Posts: 4867 · xCSxXenon 29 Oct 2020, 19:15

No, that is what prevents a second sync from occurring at the same time, but FFS is crashing somewhere and not deleting the lock file when done. Does it have a host name you can use instead? Or what happens if it is mapped to a drive letter and that letter is used?

Posts: 3 · jakeo25 30 Oct 2020, 02:34

The Hostname stopped working after a recent replacement of the DS218+.

My first step to fix this was to replace all batch files with the full "\\<IP addr>\ShareName" instead of the \\HostName, following a Support Ticket response from Synology:

Windows has changed the mechanism to discover devices on the network since Windows Vista. Windows no longer sends out broadcasts to ask for NetBIOS names from other devices, so the NAS may not appear on the network.

Currently, there is no workaround from the NAS side (at least for DSM 6.1 and earlier) since the change is introduced by Windows.

Our current solution is to access the NAS via IP address. Please open Windows Explorer and, in the address bar, type in the following: "\\X.X.X.X", where X.X.X.X is actual internal IP address of the NAS.

If you have been able to find the diskstation before, it's because the Local Master Browser on your network had cached the location of the NAS. This was likely a PC you had accessed the NAS from and it remembered this network location.

I created a drive letter in Windows to \\ServerName\ShareName, and will try this for a few days' worth of backups.

Thanks for the suggestions.

Jake

Posts: 4867 · xCSxXenon 30 Oct 2020, 18:25

Hostname definitely still works, you just need to know it. Windows network is a little hot-or-miss, but still works sometimes. The NAS management will tell you the hostname