[SOLVED] Kubuntu machine can't see Windows PCs on network
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I actually have two W10 laptops and my old one sees the Kubuntu VM under network and one does not. With the one that does not if I manually connect to the VM it shows the share. Neither one prompts for a username or password with samba setup as posted.
Although password protection is turned off on one of the W10 laptops I still am prompted for credentials regardless of operating system. I have not found anything yet that "fixes" it. Are you sure you have a null password versus blank?
With no SMB version 1 anymore dolphin is not going to find a workgroup under shared folders (SMB).
Huh, interesting. If I delete the "workgroup" line from smb.conf, will Dolphin then stop telling me that it can't find a workgroup, and just proceed to look for individual computers? Or is there any other way to overcome this "no workgroup found" hurdle?
About passwords: how can I tell if I have a null password vs. a blank password, and which one should I aim to have? I'm not even sure what the difference is.
The two W10 laptops have different builds and not exactly configured the same. I don't know since workgroup browsing is based on SMB version 1 which has been removed.
Null means no value and blank means an empty string.
Thank you, but the distinction between a "null" password and an "empty" password is still unclear.
How would I set a "null" password, or how would I set an "empty" password?
I asked the gods of the Internet and they seem to focus on SQL, VBScript, and other similarly unfamiliar contexts whose applicability to our case is uncertain to me.
null ==> undefined (as in does not exist)
empty ==> contains nothing (does exist with no content)
Any password (or other variable) that has previously been given a value but then emptied will still be defined unless it has explicitly been 'unset' in that environment.
For example, I can define a variable XYZ as empty with ' XYZ="" '
The content of XYZ is blank or empty but XYZ exists.
If I then want XYZ to be null I would then 'unset XYZ' and it would no longer exist. (it would now be null)
Respectfully, I believe that you're over-thinking this whole situation. File sharing is not a difficult thing to set up. There are countless guides on the internet... Eg: https://www.youtube.com/watch?v=FCQjtl929Ro
Also, in the output for testparm, there seem to be some strange error messages about your smb.conf... How long is it? It doesn't need to be much more than 15 or 16 lines (including the "global" section) for a single file share.
Huh, interesting. If I delete the "workgroup" line from smb.conf, will Dolphin then stop telling me that it can't find a workgroup, and just proceed to look for individual computers? Or is there any other way to overcome this "no workgroup found" hurdle?
The workgoup concept involved the SMBv1 protocol, now deprecated. Recent KDE/Dolphin versions should find Windows hosts advertising via WS-Discovery, with the proviso that the firewall allows such broadcasts.
Also, in the output for testparm, there seem to be some strange error messages about your smb.conf... How long is it? It doesn't need to be much more than 15 or 16 lines (including the "global" section) for a single file share.
Below are the contents of smb.conf for the Kubuntu laptop. This has been a little-used system, recently upgraded from Kubuntu 18.04 LTS to 20.04 LTS (which in the case of the Kubuntu desktop, is the moment when all the problems started). I use it pretty much only to test things, like we've been doing now. The tinkering done to it lately in the hope of resolving the networking issue, has added a half-dozen lines (or less) to the file. The bulk of the file is just as it downloaded from the folks at Kubuntu.
Code:
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
map to guest = Bad User
Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
[guest]
# This share allows anonymous (guest) access
# without authentication!
path = /home/pt/public
read only = no
guest ok = yes
guest only = yes
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
log level = 1
# Cap the size of the individual log files (in KiB).
max log size = 1000
# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
logging = file
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set
#
# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 means that usershare is disabled.
# usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
browseable = yes
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
Moving the [guest] lines to the end of smb.conf unfortunately didn't seem to make an immediate difference, even after restarting smbd and nmdb.
However, by following the steps in the YouTube video that @rkelsen provided, I managed to create a new shared folder on the Kubuntu laptop that can be seen by both Windows Explorer in Windows 7 and by File Explorer in Windows 10. Oddly, on the Win10 machine, the laptop is now listed in the navigation panel under both its IPv4 address and its computer name, but in the right panel only under its computer name; while on the Win7 system the laptop's IPv4 address is listed in the navigation panel but not at all (computer address OR name) in the right panel.
But I'm not complaining: this is major progress!! While the other folders on the laptop still require an unknown username and password to access them, this new folder doesn't require these things and I can simply point and click my way to it.
Now if a way can be found to get the Kubuntu machines to browse the Windows machines just as easily. I'll look into WS-Discovery as suggested by @ferrari up above.
However, by following the steps in the YouTube video that @rkelsen provided, I managed to create a new shared folder on the Kubuntu laptop that can be seen by both Windows Explorer in Windows 7 and by File Explorer in Windows 10.
The config from that video contains the following:
Code:
[EveryOneReadWrite]
path = /Share/ReadWrite
comment = Everyone Full Access
browseable = yes
writable = yes
guest ok = yes
guest only = yes
read only = no
create mode = 0755
directory mode = 0755
force user = nobody
Your config contains:
Code:
[guest]
path = /home/pt/public
read only = no
guest ok = yes
guest only = yes
There are a few key differences!
Also, the video instructs you to change the ownership of shared directories to the user: nobody:nogroup, and then sets some loose permissions on that directory. In concert with the "force user" directive, it achieves what you want.
Also, the video instructs you to change the ownership of shared directories to the user: nobody:nogroup, and then sets some loose permissions on that directory. In concert with the "force user" directive, it achieves what you want.
You bet! Some time after that post, I made the changes described on the video and that's when the setup started working from the Windows-to-Linux side. Thank you!
Just created the suggested registry value on the Windows 10 desktop and saved it, but there's no difference as Kubuntu/Dolphin still can't navigate to that (or any other) Windows machine, I'm still getting stuck on the "Unable to find workgroup" error when clicking on "Shared Folders (SMB)"; while if I try to access it via the IPv4 address, it's still asking for a username and a password that I've never created.
I'll restart the PC to see what happens.
UPDATE: Rebooted the Windows 10 desktop after making the suggested registry change, and there's no improvement. Note: the Public folder is supposedly being shared and all the appropriate settings are correct in Advanced Sharing Settings.
Last edited by Rodrigo7; 04-20-2022 at 12:45 AM.
Reason: additional info
Just created the suggested registry value on the Windows 10 desktop and saved it, but there's no difference as Kubuntu/Dolphin still can't navigate to that (or any other) Windows machine, I'm still getting stuck on the "Unable to find workgroup" error when clicking on "Shared Folders (SMB)"; while if I try to access it via the IPv4 address, it's still asking for a username and a password that I've never created.
Do you have a firewall running on the Linux host? I would expect to see Windows hosts enumerated via Dolphin. Sometimes a refresh is required (F5 key).
Do you have a firewall running on the Linux host? I would expect to see Windows hosts enumerated via Dolphin. Sometimes a refresh is required (F5 key).[/url]
Yes, the firewall currently has 4 rules:
Code:
137,138/udp ALLOW IN Anywhere SAMBA
139,445/tcp ALLOW IN Anywhere SAMBA
137,138/udp (v6) ALLOW IN Anywhere (v6) SAMBA
139,445/tcp (v6) ALLOW IN Anywhere (v6) SAMBA
Do I need to tweak any of these or add new rule(s)?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.