Timeline for answer to Windows-10 network no longer shows Linux machines by harrymc
Current License: CC BY-SA 4.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 9, 2018 at 6:30 | comment | added | harrymc | These are two different things. SMBv1 could run over NetBIOS, but SMBv2 only runs over TCP. But nothing prevents them both. You could also Enable SMBv1. This isn't extremely dangerous, since for the vulnerability to be exploited one of the computers on the network must already be infected. | |
| Nov 9, 2018 at 2:04 | comment | added | aqk | ADDENDUM#2 - It seems that WSD support in Samba is still a work in progress. From what I can see, it's preferable at present to continue using the old and obsolescent NetBios for discovering Linux machines on a Windows network. But- is NetBios compatible with SMB2 and up? | |
| Nov 9, 2018 at 0:55 | comment | added | aqk | ADDENDUM- The Network Discovery Method on the Windows machines is "WSD", not Netbios. Is there possibly some parameter in the Samba smb.conf that should reflect this? | |
| Nov 9, 2018 at 0:06 | comment | added | aqk | Tried the above switching Samba to SMB2, and still the Rasbian machine is not visible. Yet I can run the Apache webserver index.php from a windows machine, and I can ping the Rasp machine. But if type \\RASP3B into a Windows webbrowser, it says "Windows can not access - The device or resource (RASP3B) is not set up to accept connections on port "The File and printer sharing (SMB)". | |
| Nov 8, 2018 at 21:20 | history | answered | harrymc | CC BY-SA 4.0 |