[opensuse] Trouble with samba, may be related to Windows 10 ?
At home, I run samba for sharing e.g. photos and printers with my wife who works mostly on Windows or Mac. Also for my son on Windows, for printers. This has worked very well for years, but has recently (in the last year or so) begun to wobble. My son can't access the printer, can't even see it. The printer is run via cups on a central print server, then shared out via samba. I run a samba locally on my workstation, for sharing photos. My wife can't see it anymore. Machines involved - File&print server - samba 3.6.12 - seen by my wife's Win10, not seen by Mac. (need to double check that). Not seen by my son's Win10. My workstation - samba 3.0.26a. Shares not seen anywhere, anymore. New fileserver - samba 4.9.5+git.176.375e1f05788. Not seen anywhere. Clients - Windows10, macOS, a couple of Linux laptops (no problem with them). Last night I started doing some research, but didn't make it very far. Some issue about which smb protocol version to use? Does that mean anything to anyone? "min protocol", "max protocol" ? I feel very reluctant to start debugging this, it'll only take hours and hours, and leave me with less hair than ever. -- Per Jessen, Zürich (2.6°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Disclaimer | Use of IBA e-communication<https://iba-worldwide.com/disclaimer> The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.
Philippe Andersson wrote:
Regarding your printer and depending on your requirements, you may not need to share it through Samba at all. Win7 at least could access a CUPS server directly (I haven't tested yet on Win10):
- Control Panel | Printers and Faxes - click "add printer" - select "Network Printer", next - select "Connect to a printer on the Internet" - type following URL: "http://<your.cups.server>:631/printers/<your-printer-queue> - click next - select printer brand and model, click next
HTH
Hmm, that's not a bad idea. Thansk, I think we'll try that on my sons Windows machine. -- Per Jessen, Zürich (3.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-12-10 05:16 AM, Philippe Andersson wrote:
Disclaimer | Use of IBA e-communication<https://iba-worldwide.com/disclaimer>
The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.
Why do you have this nonsense at the top of your posts? You are posting to a public forum and have no say whatever in what we do with your message. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10-12-2019 15:01, James Knott wrote:
On 2019-12-10 05:16 AM, Philippe Andersson wrote:
Disclaimer | Use of IBA e-communication<https://iba-worldwide.com/disclaimer>
The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.
Why do you have this nonsense at the top of your posts? You are posting to a public forum and have no say whatever in what we do with your message.
Had the same issue. It is because samba is not up-to-date. see https://github.com/christgau/wsdd works like a charm. --- Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Frans de Boer wrote:
Had the same issue. It is because samba is not up-to-date.
I did have that suspicion, but it doens't really explain the situation. office64 - older samba 3.0, not visible. Makes sense. heron - newest samba, not visible. Makes sense? rainbow - samba 3.6, visible .....
see https://github.com/christgau/wsdd works like a charm.
"Web Service Discovery Daemon". Same thing Herbert suggested. It requires python3, I'll try it on the new fileserver - yep, now one Windows system can see that server, that's cool. I was wondering if I might only need to run it on one system. -- Per Jessen, Zürich (4.0°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, Am 10.12.19 um 16:38 schrieb Per Jessen:
office64 - older samba 3.0, not visible. Makes sense. heron - newest samba, not visible. Makes sense? rainbow - samba 3.6, visible .....
only a suggestion: compare at all machines the samba conf. file. i guess there is a different configuration. /etc/samba/smb.conf i do not know anything about win10 (my virtual windows systems are older), but (my) older (and ported to newer samba versions) samba configuration files are much longer than new(er) created ones. good point from working samba version to newer one is to check changelog for samba, because i remember they often change standard configuration (mostly to improve security) and this leads in adding more config info's to still have the old behavior. (google for changelog samba) -> https://www.samba.org/samba/history/ check the main versions for "smb.conf changes" with other words, only copying the old configuration to the new samba could - but will not in all cases - lead in a working environment. simoN -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Simon Becherer wrote:
Hi,
Am 10.12.19 um 16:38 schrieb Per Jessen:
office64 - older samba 3.0, not visible. Makes sense. heron - newest samba, not visible. Makes sense? rainbow - samba 3.6, visible .....
only a suggestion:
compare at all machines the samba conf. file. i guess there is a different configuration. /etc/samba/smb.conf
Oh yes, been there, done that :-) 'heron' is a copy of 'rainbow', except it only has one file share.
with other words, only copying the old configuration to the new samba could - but will not in all cases - lead in a working environment.
Old (rainbow) global section that makes 'rainbow' visible in Win10: [global] workgroup = HERRLIBERG passdb backend = tdbsam 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 = Yes New (heron) global section that does not make 'heron' visible in Win10: [global] workgroup = HERRLIBERG passdb backend = tdbsam printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf I think the only significant difference is "usershare allow guests = Yes" in the old config. I have just added that line to the new config, stopped wsdd and restarted both smbs. 'rainbow' is now visible, 'heron' is not visible. -- Per Jessen, Zürich (1.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Dec 10, 2019 at 7:40 AM Per Jessen <per@computer.org> wrote:
At home, I run samba for sharing e.g. photos and printers with my wife who works mostly on Windows or Mac. Also for my son on Windows, for printers. This has worked very well for years, but has recently (in the last year or so) begun to wobble.
My son can't access the printer, can't even see it. The printer is run via cups on a central print server, then shared out via samba. I run a samba locally on my workstation, for sharing photos. My wife can't see it anymore.
Machines involved -
File&print server - samba 3.6.12 - seen by my wife's Win10, not seen by Mac. (need to double check that). Not seen by my son's Win10.
My workstation - samba 3.0.26a. Shares not seen anywhere, anymore.
New fileserver - samba 4.9.5+git.176.375e1f05788. Not seen anywhere.
I am running Tumbleweed with samba-4.11.2. I also cannot access shares from Windows 10. No idea why. When I looked for possible reasons, the version was always discussed. I have tried many versions, but it made no difference. I suspect that it is something else. And I suspect that it is related to authentication and the password. But I have not been able to see what is wrong. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
On Tue, Dec 10, 2019 at 7:40 AM Per Jessen <per@computer.org> wrote:
At home, I run samba for sharing e.g. photos and printers with my wife who works mostly on Windows or Mac. Also for my son on Windows, for printers. This has worked very well for years, but has recently (in the last year or so) begun to wobble.
My son can't access the printer, can't even see it. The printer is run via cups on a central print server, then shared out via samba. I run a samba locally on my workstation, for sharing photos. My wife can't see it anymore.
Machines involved -
File&print server - samba 3.6.12 - seen by my wife's Win10, not seen by Mac. (need to double check that). Not seen by my son's Win10.
My workstation - samba 3.0.26a. Shares not seen anywhere, anymore.
New fileserver - samba 4.9.5+git.176.375e1f05788. Not seen anywhere.
I am running Tumbleweed with samba-4.11.2. I also cannot access shares from Windows 10. No idea why. When I looked for possible reasons, the version was always discussed. I have tried many versions, but it made no difference. I suspect that it is something else. And I suspect that it is related to authentication and the password. But I have not been able to see what is wrong.
My main trouble seems to be getting Windows and Mac to see the amba shares. From Windows 10, I can still connect shares, but have to type in the URLs manually. I have not yet tried the direct Window-to-Cups trick that Philippe mentioned. -- Per Jessen, Zürich (5.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Dienstag, 10. Dezember 2019, 13:16:34 CET schrieb Per Jessen:
Roger Oberholtzer wrote:
On Tue, Dec 10, 2019 at 7:40 AM Per Jessen <per@computer.org> wrote:
At home, I run samba for sharing e.g. photos and printers with my wife who works mostly on Windows or Mac. Also for my son on Windows, for printers. This has worked very well for years, but has recently (in the last year or so) begun to wobble.
My son can't access the printer, can't even see it. The printer is run via cups on a central print server, then shared out via samba. I run a samba locally on my workstation, for sharing photos. My wife can't see it anymore.
Machines involved -
File&print server - samba 3.6.12 - seen by my wife's Win10, not seen by Mac. (need to double check that). Not seen by my son's Win10.
My workstation - samba 3.0.26a. Shares not seen anywhere, anymore.
New fileserver - samba 4.9.5+git.176.375e1f05788. Not seen anywhere.
I am running Tumbleweed with samba-4.11.2. I also cannot access shares from Windows 10. No idea why. When I looked for possible reasons, the version was always discussed. I have tried many versions, but it made no difference. I suspect that it is something else. And I suspect that it is related to authentication and the password. But I have not been able to see what is wrong.
My main trouble seems to be getting Windows and Mac to see the amba shares. From Windows 10, I can still connect shares, but have to type in the URLs manually. I have not yet tried the direct Window-to-Cups trick that Philippe mentioned.
For this the ws-discovery protocol can be used. I have found one implementation and packaged it: https://build.opensuse.org/package/show/home:hgraeber/wsdd There are other implementations as well and will try some of them in future. Herbert -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Per, [...]
Last night I started doing some research, but didn't make it very far. Some issue about which smb protocol version to use? Does that mean anything to anyone? "min protocol", "max protocol" ? I feel very reluctant to start debugging this, it'll only take hours and hours, and leave me with less hair than ever.
can't say anything regarding MACs, but as for Windows 10, you have to specify at least "max protocol = SMB2", better SMB3, to get it to work, because SMB1 in Windows 10 and Server 2016 ff. has been disabled by default. If one of your Windows 10 machines can see the network environment and others can't, you have to activate network discovery in Windows 10 itself. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Michael Hirmke wrote:
Hi Per,
[...]
Last night I started doing some research, but didn't make it very far. Some issue about which smb protocol version to use? Does that mean anything to anyone? "min protocol", "max protocol" ? I feel very reluctant to start debugging this, it'll only take hours and hours, and leave me with less hair than ever.
can't say anything regarding MACs, but as for Windows 10, you have to specify at least "max protocol = SMB2", better SMB3, to get it to work, because SMB1 in Windows 10 and Server 2016 ff. has been disabled by default.
Thanks Michael. I've added 'max protocol = SMB3' to the three machines running samba - rainbow, office64 and heron. 'rainbow' is the older fileserver, heron is new. Remarkably, 'rainbow' has always worked fine, could be seen by Windows (at least one of them). Adding 'max protocol = SMB3' does not seemn to have had any effect.
If one of your Windows 10 machines can see the network environment and others can't, you have to activate network discovery in Windows 10 itself.
Okay, that we'll have to try too. -- Per Jessen, Zürich (5.3°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/10/2019 12:40 AM, Per Jessen wrote:
Last night I started doing some research, but didn't make it very far. Some issue about which smb protocol version to use? Does that mean anything to anyone? "min protocol", "max protocol" ? I feel very reluctant to start debugging this, it'll only take hours and hours, and leave me with less hair than ever.
The smbauth versions have changed. Samba 4.5 has NTLMv1 authentication disabled by default. You can look at the changes in man smb.conf under client NTLMv2 auth. Windows 10 after 1803 update samba issues, see: https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/wind... and https://appuals.com/how-to-fix-the-windows-10-file-sharing-not-working-probl... and https://windowsreport.com/windows-unable-access-samba-share/ For general windows side issues, a good collection of information is at: https://itconnect.uw.edu/wares/msinf/other-help/lmcompatibilitylevel/ntlmv1-... Another good reference: https://wiki.archlinux.org/index.php/Samba -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
On 12/10/2019 12:40 AM, Per Jessen wrote:
Last night I started doing some research, but didn't make it very far. Some issue about which smb protocol version to use? Does that mean anything to anyone? "min protocol", "max protocol" ? I feel very reluctant to start debugging this, it'll only take hours and hours, and leave me with less hair than ever.
The smbauth versions have changed. Samba 4.5 has NTLMv1 authentication disabled by default. You can look at the changes in man smb.conf under client NTLMv2 auth.
Thanks for the pointers David. Thanks to everyone who offered advice and suggestions. Unfortunaterly I didn't get the answer I was hoping for - "you dimwit, just flip this bit and flap that config, and it'll work again". Sofar: - network browsing does not work (wsdd was a partial solution) - file sharing works for Windows, by specifying URLs. - printing will probably work by directly accessing the printserver. Thank you Microsoft&Apple for regularly reminding me why I gave up on your products. -- Per Jessen, Zürich (0.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
David C. Rankin -
Frans de Boer -
Herbert Graeber -
James Knott -
mh＠mike.franken.de -
Per Jessen -
Philippe Andersson -
Roger Oberholtzer -
Simon Becherer