[opensuse] Samba: I can not see a machine, yet I can connect to it.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Linux, on the same desktop machine, I can browse smb network and see myself, and connect to the directory share. But on Windows 10 I can not see this machine, but I can see another machine (both on openSUSE 42.2). On a virtual W10 machine (hosted on the desktop machine) I can not see the host machine. However, I can add a network drive by telling the name (\\telcontar\Pictures_share) and see the files in it. I don't see blocked packets on the firewall. aa-logprof shows nothing. Machine that I can see /etc/samba/smb.conf [global] workgroup = VALINOR passdb backend = tdbsam local master = yes os level = 65 printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = No domain master = No security = user wins support = Yes ldap admin dn = ... [hoard] comment = Hoard in Amon Lanc inherit acls = Yes path = /data/waterhoard/SambaHoard read only = No case sensitive = no strict locking = no valid users = cer write list = cer Machine that I can not see /etc/samba/smb.conf [global] workgroup = VALINOR # GONDOR passdb backend = tdbsam local master = yes # preferred master = yes os level = 64 printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$ domain logons = No domain master = No security = user wins support = Yes ldap admin dn = log level = 1 passdb:1 auth:1 winbind:1 #log level = 3 passdb:1 auth:1 winbind:1 #ldap suffix = #wins server = #wins support = No ... [Pictures_share] comment = For use by Windows machine to process the photos inherit acls = Yes path = /data/storage_b/cer/Pictures.share read only = No case sensitive = no strict locking = no valid users = cer write list = cer # "pdbedit -a -u cer" no estaba hecho y no iba. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloywqUACgkQtTMYHG2NR9WPmwCgkyHnN3lyWR/yMqdf/vpcHDpA 0rwAnj4uqscq86kdZtXkhdWjtCacbKQl =oyhZ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-12-14 19:27, Carlos E. R. wrote:
Hi,
On Linux, on the same desktop machine, I can browse smb network and see myself, and connect to the directory share.
But on Windows 10 I can not see this machine, but I can see another machine (both on openSUSE 42.2).
On a virtual W10 machine (hosted on the desktop machine) I can not see the host machine. However, I can add a network drive by telling the name (\\telcontar\Pictures_share) and see the files in it.
However, on my laptop, which is booted to Windows 10 this instant, I can not map to the same network share. Says "network path not found". It works using the IP number, though. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On 12/14/2017 10:27 AM, Carlos E. R. wrote:
Hi,
On Linux, on the same desktop machine, I can browse smb network and see myself, and connect to the directory share.
But on Windows 10 I can not see this machine, but I can see another machine (both on openSUSE 42.2).
On a virtual W10 machine (hosted on the desktop machine) I can not see the host machine. However, I can add a network drive by telling the name (\\telcontar\Pictures_share) and see the files in it.
Carlos, welcome to the mysterious world of Windows networking. Walk away, come back in 10 minutes and it will be fixed. OR, Make sure a Linux Samba Box wins all browser elections (OS Lever higher than 65) and then restart nmb on that machine when in a rush. systemctl restart nmb.service This is a maddening problem that people have been fighting for years. If you have a windows machine that is always on, and which wins browser elections (like a domain controller or some server machine) its not so bad, but for me, where windows machines only occasionally connect (and are usually in VMs) its a never ending pain in the neck. -- After all is said and done, more is said than done.
On 12/14/2017 03:48 PM, John Andersen wrote:
Make sure a Linux Samba Box wins all browser elections (OS Lever higher than 65) and then restart nmb on that machine when in a rush. systemctl restart nmb.service
How does one make sure Samba wins? Is there a setting somewhere? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott composed on 2017-12-14 16:00 (UTC-0500):
John Andersen wrote:
Make sure a Linux Samba Box wins all browser elections (OS Lever higher than 65) and then restart nmb on that machine when in a rush. systemctl restart nmb.service
How does one make sure Samba wins? Is there a setting somewhere?
As John tried to indicate, in smb.conf: os level = -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2017-12-14 at 17:09 -0500, Felix Miata wrote:
James Knott composed on 2017-12-14 16:00 (UTC-0500):
John Andersen wrote:
Make sure a Linux Samba Box wins all browser elections (OS Lever higher than 65) and then restart nmb on that machine when in a rush. systemctl restart nmb.service
How does one make sure Samba wins? Is there a setting somewhere?
As John tried to indicate, in smb.conf:
os level =
I have: os level = 64 - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloy9zcACgkQtTMYHG2NR9W6SwCfWRQCp0j0fVEGszkt0zPTSKf3 ZvkAnRRS/3wZVxEFIbi557nwU+wJwxPI =LulE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2017-12-14 at 16:04 -0800, John Andersen wrote:
On 12/14/2017 02:12 PM, Carlos E. R. wrote:
I have:
os level = 64
Samba set to 64 will lose an election to any true Server Class Windows machine (any product with server in its name).
I don't have any, but I'll raise the number. [...] Done. Restarted nmb and smb, but the virtual W10 machine doesn't see the host, although it connects to the maped share just fine. I will have to reboot the laptop later and see. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlozxroACgkQtTMYHG2NR9Vi9ACeOdCZlNiVJjipeRETAdNcl65X DBQAmgNx5dv3m6pu0n6sh2NT7Qp217kP =FgMe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/14/2017 05:09 PM, Felix Miata wrote:
James Knott composed on 2017-12-14 16:00 (UTC-0500):
John Andersen wrote:
Make sure a Linux Samba Box wins all browser elections (OS Lever higher than 65) and then restart nmb on that machine when in a rush. systemctl restart nmb.service How does one make sure Samba wins? Is there a setting somewhere? As John tried to indicate, in smb.conf:
os level =
I don't see that line in smb.conf. I'll try adding it, with level 70. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2017-12-14 at 12:48 -0800, John Andersen wrote:
On 12/14/2017 10:27 AM, Carlos E. R. wrote:
Hi,
On Linux, on the same desktop machine, I can browse smb network and see myself, and connect to the directory share.
But on Windows 10 I can not see this machine, but I can see another machine (both on openSUSE 42.2).
On a virtual W10 machine (hosted on the desktop machine) I can not see the host machine. However, I can add a network drive by telling the name (\\telcontar\Pictures_share) and see the files in it.
Carlos, welcome to the mysterious world of Windows networking. Walk away, come back in 10 minutes and it will be fixed.
Oh, I rebooted Windows. And it took an hour to think about it and some updates... ;-(
OR,
Make sure a Linux Samba Box wins all browser elections (OS Lever higher than 65) and then restart nmb on that machine when in a rush. systemctl restart nmb.service
Ah, nmb. I forgot. I was restarting smb only. I can't try just now, Windows is processing a batch of photos and I can't risk interruption.
This is a maddening problem that people have been fighting for years. If you have a windows machine that is always on, and which wins browser elections (like a domain controller or some server machine) its not so bad, but for me, where windows machines only occasionally connect (and are usually in VMs) its a never ending pain in the neck.
Yiks. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloy9vMACgkQtTMYHG2NR9Xj7ACeJQbh0cIrUTFjkr4tVVBSamgL bq4AoIdyu90e2bISFlOrLT9BA7D+OvmR =WsRt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 14/12/17 22:10, Carlos E. R. wrote:
This is a maddening problem that people have been fighting for years. If you have a windows machine that is always on, and which wins browser elections (like a domain controller or some server machine) its not so bad, but for me, where windows machines only occasionally connect (and are usually in VMs) its a never ending pain in the neck.
Yiks.
It gets worse. Some versions of Windows BY DESIGN cannot see other versions of Windows. It depends both on the OS (my father-in-law has a Win7 laptop and had an XP desktop) and connecting between those two machines was one-way only - can't remember which. And I believe home versions of Windows can no longer join/connect to a domain, so if your Pro version is configured to use a domain not a workgroup, it is likely to be invisible to a home machine (and/or vice versa). Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/16/2017 04:12 PM, Wol's lists wrote:
Some versions of Windows BY DESIGN cannot see other versions of Windows. It depends both on the OS (my father-in-law has a Win7 laptop and had an XP desktop) and connecting between those two machines was one-way only - can't remember which.
Even the same version. I have Windows 10 on my notebook, along with Linux. It can share with my Linux desktop, but not a Windows 10 VM on that same computer. When that notebook is booted into Linux, Linux and the W10 VM on the notebook can access both Linux and the W10 VM on the desktop system. I have absolutely no idea why that's happening, where one W10 system can't share with another. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2017-12-16 at 16:28 -0500, James Knott wrote:
On 12/16/2017 04:12 PM, Wol's lists wrote:
Some versions of Windows BY DESIGN cannot see other versions of Windows. It depends both on the OS (my father-in-law has a Win7 laptop and had an XP desktop) and connecting between those two machines was one-way only - can't remember which.
Even the same version. I have Windows 10 on my notebook, along with Linux. It can share with my Linux desktop, but not a Windows 10 VM on that same computer. When that notebook is booted into Linux, Linux and the W10 VM on the notebook can access both Linux and the W10 VM on the desktop system. I have absolutely no idea why that's happening, where one W10 system can't share with another.
My W10 laptop sees my Linux server machine samba shares and can connect to them. But it does not see my Linux desktop, although it can connect to it if I type the "\\share_IP\path". So it is a windows name "resolution" issue. My Windows 10 virtual machine hosted on the desktop does not see the desktop by name, but it can connect to a share by name if I type it in full (IP number not needed, name works). - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo1qCsACgkQtTMYHG2NR9XRNACfRo2PKYvFxL9e4SQzjZdijz04 z44Anie1pRmrlNAO22gNRzlWKah8BZQ4 =EZWn -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2017-12-17 at 00:11 +0100, Carlos E. R. wrote:
On Saturday, 2017-12-16 at 16:28 -0500, James Knott wrote:
On 12/16/2017 04:12 PM, Wol's lists wrote:
Some versions of Windows BY DESIGN cannot see other versions of Windows. It depends both on the OS (my father-in-law has a Win7 laptop and had an XP desktop) and connecting between those two machines was one-way only - can't remember which.
Even the same version. I have Windows 10 on my notebook, along with Linux. It can share with my Linux desktop, but not a Windows 10 VM on that same computer. When that notebook is booted into Linux, Linux and the W10 VM on the notebook can access both Linux and the W10 VM on the desktop system. I have absolutely no idea why that's happening, where one W10 system can't share with another.
My W10 laptop sees my Linux server machine samba shares and can connect to them. But it does not see my Linux desktop, although it can connect to it if I type the "\\share_IP\path". So it is a windows name "resolution" issue.
My Windows 10 virtual machine hosted on the desktop does not see the desktop by name, but it can connect to a share by name if I type it in full (IP number not needed, name works).
Telcontar:~ # aa-logprof Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. Enforce-mode changes: Profile: /usr/sbin/nmbd Capability: net_admin Severity: 8 [1 - capability net_admin,] (A)llow / [(D)eny] / (I)gnore / Audi(t) / Abo(r)t / (F)inish Adding capability net_admin, to profile. But still, no change from virtualized W10 guest. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo2YIIACgkQtTMYHG2NR9U8bgCfVnqOgXOCUdoFt5LhB7gjd35H +BUAn3ynMccGs1gIV+a8CxBeu3osYLZC =nmgo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday, 17 December 2017 22:48:03 ACDT Carlos E. R. wrote: [...]
Telcontar:~ # aa-logprof Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. Enforce-mode changes:
Profile: /usr/sbin/nmbd Capability: net_admin Severity: 8
[1 - capability net_admin,] (A)llow / [(D)eny] / (I)gnore / Audi(t) / Abo(r)t / (F)inish Adding capability net_admin, to profile.
But still, no change from virtualized W10 guest.
With Windows 7 there was a registry entry required to get it to enable older LanManager protocol/s and work correctly with Samba 3. With Windows 10 I'm pretty sure that's no longer supported - Win10 expects to see an AD DC for name resolution. Samba 4 can be setup to mimic an AD controller but it's a lot of work (needs a full openLDAP backend configured) and I've never bothered to work through it. I run Samba at home as a pre-AD PDC and Windows 7 clients join that domain OK (with the registry hack) but no go with Win 10 (yeah, domain logons are overkill for a home network, but it was a learning exercise). I'm pretty sure that it does relate to how later versions of Windows handle name resolution and service discovery - they rely pretty heavily on LDAP for that. WINS was still supported on Win 7, but I'm pretty sure it's gone for Win 10. At work, we run Windows DC's, so learning Samba 4 AD/LDAP has never really been a priority for me. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2017-12-18 at 01:18 +1030, Rodney Baker wrote:
On Sunday, 17 December 2017 22:48:03 ACDT Carlos E. R. wrote: [...]
Telcontar:~ # aa-logprof Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. Enforce-mode changes:
Profile: /usr/sbin/nmbd Capability: net_admin Severity: 8
[1 - capability net_admin,] (A)llow / [(D)eny] / (I)gnore / Audi(t) / Abo(r)t / (F)inish Adding capability net_admin, to profile.
But still, no change from virtualized W10 guest.
With Windows 7 there was a registry entry required to get it to enable older LanManager protocol/s and work correctly with Samba 3. With Windows 10 I'm pretty sure that's no longer supported - Win10 expects to see an AD DC for name resolution. Samba 4 can be setup to mimic an AD controller but it's a lot of work (needs a full openLDAP backend configured) and I've never bothered to work through it. I run Samba at home as a pre-AD PDC and Windows 7 clients join that domain OK (with the registry hack) but no go with Win 10 (yeah, domain logons are overkill for a home network, but it was a learning exercise).
I'm pretty sure that it does relate to how later versions of Windows handle name resolution and service discovery - they rely pretty heavily on LDAP for that. WINS was still supported on Win 7, but I'm pretty sure it's gone for Win 10.
At work, we run Windows DC's, so learning Samba 4 AD/LDAP has never really been a priority for me.
No, the issue is on the Linux side of things, as my laptop sees one Linux machine perfectly, but not another. Both running Leap 42.2. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlo2qO8ACgkQtTMYHG2NR9VyyQCeNhYAXLx8X2VVrA7Cac5362Eu LYwAn35B/wdk3hX9TsSB3r+YsE/M54bn =kNHq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-12-17 a las 13:18 +0100, Carlos E. R. escribió:
On Sunday, 2017-12-17 at 00:11 +0100, Carlos E. R. wrote:
On Saturday, 2017-12-16 at 16:28 -0500, James Knott wrote:
Telcontar:~ # aa-logprof Reading log entries from /var/log/audit/audit.log. Updating AppArmor profiles in /etc/apparmor.d. Enforce-mode changes:
Profile: /usr/sbin/nmbd Capability: net_admin Severity: 8
[1 - capability net_admin,] (A)llow / [(D)eny] / (I)gnore / Audi(t) / Abo(r)t / (F)inish Adding capability net_admin, to profile.
But still, no change from virtualized W10 guest.
But big change in the W10 laptop: it now can see both Linux machines. So that was it: restart nmbd, and that apparmor was blocking something. Plus the config changes I did, perhaps. - -- Cheers Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlo3E2UACgkQja8UbcUWM1zoZwD/eqBOZSumP0DBiQbihzLfVq7Q cg/gEUj2eOlgeu1/WGcA/iNhibUYm2OE5Y6PpSFJtFYg1abBaG0N8QXTohHUtRor =t8Bb -----END PGP SIGNATURE-----
participants (6)
-
Carlos E. R. -
Felix Miata -
James Knott -
John Andersen -
Rodney Baker -
Wol's lists