On Sun, 2017-04-02 at 15:11 -0700, Gordon Messmer wrote: > On 04/02/2017 09:01 AM, Patrick O'Callaghan wrote: > > I want to use N as a backup server for W, however W cannot see shares > > on N. It complains about permissions. > > > It seems to me that from both a performance and reliability perspective, > this is the problem you should solve. Specifically what information are > you given by W when you try to connect to N? You said that N runs > Debian, so I presume you can connect to it via SSH. What information is > logged on N when the client attempts a connection? What version of > Samba is running on N? You're right of course, this is what I should do, but the server doesn't appear to log anything when accessing from Windows, whereas it does when accessing from Linux. In more detail: Using Dolphin (on D) to browse Samba shares I see both the local Samba server on D and the NAS CIFS service on N. Further clicking gets me into the latter with no trouble. The log on N shows this happening. Using the Windows file manager on W to open the Network tab, I see several entries, including the Samba service on D and the NAS (called STORAGE). Opening the D entry shows me the shares from D. Trying to open the STORAGE tab gets an error: "Windows cannot access \\STORAGE. Check the spelling of the name. Otherwise there might be a problem with your network, ...". The log file on N shows no activity. Note that N is configured as a Workgroup server. I'm not using Active Directory, though the NAS does support this as an option. Also, W has something called Homegroup, apparently Microsoft's attempt to make this stuff easier by adding yet another layer of terminology. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
