Page 1 of 1

MSHOME predominant over the true workgroup name

PostPosted: Jan 14th, '20, 22:31
by JJF
The actual workgroup name assigned in smb.conf is different from what I see when I open > files>Network>Windows Network , as shown in the 2 attached captured screens. It should have been FROMMERS.
I assume that this is the reason why I am unable to setup cups printer hooked to windows 10 usb on the same LAN, which I could access before this clean install of Mageia 7.
With Dolphin, I can access files on that Winndows 10 connected on the same LAN as shown in the 3rd captured screen. (both efrat on jf-ssd and jacob on jf-ssd)

Below is the related section of smb.conf


load printers = yes
cups options = raw
netbios name = SSDPC
hosts allow = 10.0.0.
[printers]
path = /var/spool/samba
comment = All Printers
browseable = yes
printable = yes
guest ok = no
writable = no
create mode = 0700
write list = root @adm @wheel jacob

[ML1640]
comment = Samsung ML-1640 Laser Printer
printer = ml1640
path = /var/spool/samba
printing = cups
printable = yes
user client driver = yes
# to allow user 'guest account' to print.
guest ok = yes
writable = no
write list = root @adm @wheel jacob
valid users = root @adm @wheel jacob

[jfshare]
path = /home/jacob/jfshare
comment = jfshare
available = yes
browseable = yes
writeable = yes
read only = no
valid users = jacob
[efshare]
path = /home/jacob/efshare
comment = efshare
browseable = yes
public = yes
writable = yes
valid users = jacob



2 questions:
How to get rid of MSHOME workgroup
How to connect to the printer connected to the USB port on Windows 10

JJF