O
Oso Alex
I just set up a LAN environment with two Windows 10 April 2018 Update machines and one Kubuntu 18.04 LTS machine.
The two Windows 10 machines see each other in 'Network', whereas the Kubuntu one is nowhere to be found.
Interestingly, if you type \\KUBUNTU-PC-NAME\ in the address bar, you can access the shared content and even drop and take files from the shared folder. So Samba has been set up correctly.
I checked the CIFS/SMB 1.0 Client support in both of the Windows machines with the "Turn Windows Features On or Off" applet, which made the Kubuntu PC appear in the 'Network' section of both machines.
Now, we all know how vulnerable Windows becomes when this feature is turned on, so my question is, how can I make this computer visible without having to type its name in the address bar?
I have already turned on the following Services and parameters:
And here's the content for the smb.conf file inside the Kubuntu machine. One of the last changes I made was adding max client protocol = smb3_11, which is the protocol used by Windows 10 (correct me if I'm wrong), so SMB 1 wouldn't be needed in those other PCs, but still this didn't make it work without turning SMB 1.0 on in Windows Features.
Continue reading...
The two Windows 10 machines see each other in 'Network', whereas the Kubuntu one is nowhere to be found.
Interestingly, if you type \\KUBUNTU-PC-NAME\ in the address bar, you can access the shared content and even drop and take files from the shared folder. So Samba has been set up correctly.
I checked the CIFS/SMB 1.0 Client support in both of the Windows machines with the "Turn Windows Features On or Off" applet, which made the Kubuntu PC appear in the 'Network' section of both machines.
Now, we all know how vulnerable Windows becomes when this feature is turned on, so my question is, how can I make this computer visible without having to type its name in the address bar?
I have already turned on the following Services and parameters:
- DNS Client
- Function Discovery Provider Host
- Function Discovery Resource Publication
- Peer Networking Grouping
- SSDP Discovery
- UPnP Device Host
- Enabled NetBIOS over TCP/IP in IPv4 Properties.
And here's the content for the smb.conf file inside the Kubuntu machine. One of the last changes I made was adding max client protocol = smb3_11, which is the protocol used by Windows 10 (correct me if I'm wrong), so SMB 1 wouldn't be needed in those other PCs, but still this didn't make it work without turning SMB 1.0 on in Windows Features.
#============================ Global definition ================================
[global]
workgroup = WORKGROUP
client max protocol = smb3_11
server string = Samba Server %v
netbios name = KUBUNTU-PC-NAME
browseable = yes
security = user
map to guest = Bad User
dns proxy = no
ntlm auth = yes
client lanman auth = no
bind interfaces only = no
wins support = yes
local master = yes
preferred master = yes
#============================ Share Definitions ==============================
[Público]
path = /home/username/Público/
writable = yes
guest ok = yes
read only = no
create mode = 0777
directory mode = 0777
force user = nobody
[global]
workgroup = WORKGROUP
client max protocol = smb3_11
server string = Samba Server %v
netbios name = KUBUNTU-PC-NAME
browseable = yes
security = user
map to guest = Bad User
dns proxy = no
ntlm auth = yes
client lanman auth = no
bind interfaces only = no
wins support = yes
local master = yes
preferred master = yes
#============================ Share Definitions ==============================
[Público]
path = /home/username/Público/
writable = yes
guest ok = yes
read only = no
create mode = 0777
directory mode = 0777
force user = nobody
Continue reading...