SoonerLater
Explorer
- Joined
- Mar 7, 2013
- Messages
- 80
When I open File Explorer on a Windows 10 pc to \\Jessie\Scansnap, I receive an error:
However, if I point File Explorer at \\192.168.86.43\Scansnap I can see the files:
How/why can this happen? Shouldn't it either work both ways or not work both ways? What allows it to work with \\ipaddress, but not \\servername?
And just to be clear, the other shares on this server (\\Jessie\Video, \\Jessie\Audiobooks, etc.) all work using the servername. It's only with the SMB Share "Scansnap" that it only works using \\ipaddress\sharename.
Server name: Jessie (running FreeNAS 11.2-U8)
Server IP address: 192.168.86.43
Pool Name: Jessie
Dataset: Scans (mnt/Jessie/Scans)
SMB Share: Scans (points to mnt/Jessie/Scans; guest access allowed; not browseable to network clients)
SMB Share: Scansnap (points to mnt/Jessie/Scans; no guest access allowed; is browseable to network clients)
However, if I point File Explorer at \\192.168.86.43\Scansnap I can see the files:
How/why can this happen? Shouldn't it either work both ways or not work both ways? What allows it to work with \\ipaddress, but not \\servername?
And just to be clear, the other shares on this server (\\Jessie\Video, \\Jessie\Audiobooks, etc.) all work using the servername. It's only with the SMB Share "Scansnap" that it only works using \\ipaddress\sharename.
Server name: Jessie (running FreeNAS 11.2-U8)
Server IP address: 192.168.86.43
Pool Name: Jessie
Dataset: Scans (mnt/Jessie/Scans)
SMB Share: Scans (points to mnt/Jessie/Scans; guest access allowed; not browseable to network clients)
SMB Share: Scansnap (points to mnt/Jessie/Scans; no guest access allowed; is browseable to network clients)