I have recently installed a Linux Samba file server on my home network. All is well with it. The issue I'm having is my one Win 10 machine is seeing itself, the other Win 10 machine, the router and the Linux. This machine (the other Win 10) only sees itself and the other Win 10 machine. All "obvious" settings seem to be correct.
Any ideas?
Thx so much in advance.
I discovered that SMB file sharing was off in windows features yet that has not resolved the issue. To my surprise, no change.
I've discovered the issue, not the resolve though. It's not that the one Win 10 machine is unable to view the Samba file server, it's that the two Win 10 machines can't at the same time. It's one or the other. Both Win 10 machines share the same MS account. Same account email and account name. The two have different computer names but the same user. Could this be the issue and if so, what can I do as both Win machines need to remain on the same MS account.
How about, create a new user on the server, and then map a drive to the server using different credentials? My first thought...
Good idea! I'll try that tomorrow. I just refuse to accept having to change to local logins, seems like a easy copout of an answer that I've heard elswhere. I can't believe that the thousands of multiple windows device users, that are synced via the same MS account, can't be connected to a file server, Linux or not Linux.
Haven't been able to gain a solution so it's on the back burner for a while. Thanks
Check versions of the SMB protocol. I have an issue with a multi function dell copier scanner and the issue is it uses a later version of the smb protocol and the windows 7 workstations I want it to connect to can't. This could be an issue...at least it is something to check.
Quote