When I need to install something on the server, I switch cables physically. There are no firewalls on the Windows rigs, they are airgapped workstations with no internet, the local net is a Red Zone development thing. I can't be the first person since Windwas released that has tried to connect it to a Samba share on a generic Linux installation? So I am not sure whether I have configured Samba wrong or if the Win10 is at fault. I can't make heads or tails of /var/log/samba/smbd.log though - it is drenched in babble that I do not understand, but nothing as simple as say "got request from 10.0.0.11, denied it" or some such. The Win10 rig is assigned the proper IP (based on MAC), I can ping the server, and as far as my layman eyes can sleuth from the /var/log/samba/nmbd.log (log level=10) the Win10 rig is connected. The Win7 rig sees the Win10 rig and its Public folder, the Win10 rig can't see the Win7 rig. I can't see the server in the Network Neighborhood (or whatever it is named these days), I can't reach the server by putting \\10.0.0.1\share in an explorer address field. Almost all those cases are about NAS though, with a good fraction of Raspberry Pi's. Google is rife with people who complain about the same things as me, with scores of answers that profess to fix the problem. I also learned that Win10 should have some Lanman policy changed to allow unsafe logons, that I can re-enable SMB1 in Win10, various "Get-WindowsOptionalFeature" operations in PowerShell can enable/disable SMB123, et cetera. Many hours later I learned that SMB1 is removed from Windows 10, and that I should make sure that /etc/samba/smb.cfg allows SMB2-3. I put up a small Ubuntu 20.04 backup server and shared a folder on it. Not sure if this is the right forum since it is either a Linux problem or a Windows problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |