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 ...
Search found 3 matches
- 30 Oct 2020, 02:34
- Forum: Help
- Topic: ERROR_BAD_NET_NAME
- Replies: 4
- Views: 1058
- 27 Oct 2020, 22:10
- Forum: Help
- Topic: ERROR_BAD_NET_NAME
- Replies: 4
- Views: 1058
Re: ERROR_BAD_NET_NAME
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"?
- 27 Oct 2020, 21:47
- Forum: Help
- Topic: ERROR_BAD_NET_NAME
- Replies: 4
- Views: 1058
ERROR_BAD_NET_NAME
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 ...
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 ...