[Bug 1140907] New: Since recent update smb share no longer accessible to Windows10 guest running on same host

newer
[Bug 1141052] New: build package...

older
[Bug 1140401] Recoll web interface...

bugzilla_noreply＠novell.com

9 Jul 2019 9 Jul '19

15:45

http://bugzilla.suse.com/show_bug.cgi?id=1140907 Bug ID: 1140907 Summary: Since recent update smb share no longer accessible to Windows10 guest running on same host Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers@SuSE.de Reporter: brogers@suse.com QA Contact: samba-maintainers@SuSE.de Found By: --- Blocker: --- I always export a smb share of a host directory for my KVM based Windows 10 guest running on same host to consume. This stopped working when finally rebooting a few days ago. I see that a samba update was done recently, so I assume it's related. For the record, David Mulder helped me with some interactive debugging and indicated that the daemon which runs the smb service likely died. (I'll try to attach a supportconfig run - but in this initial bug creation, it's erroring out - so I'll try later)

...

From the Windows 10 side, this is what is reported: An error occurred while reconnecting Z: to \\192.168.100.1\SharedWithWindows Microsoft Windows Network: The network path was not found. This connection has not been restored.

For the record, I keep TW pretty up to date. The previous samba version running was v4.10.2, now is v4.10.5. -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 3.0 KB)

Show replies by date

bugzilla_noreply＠novell.com

9 Jul 9 Jul

15:48

New subject: [Bug 1140907] Since recent update smb share no longer accessible to Windows10 guest running on same host

http://bugzilla.suse.com/show_bug.cgi?id=1140907 http://bugzilla.suse.com/show_bug.cgi?id=1140907#c1 --- Comment #1 from Bruce Rogers --- Created attachment 809885 --> http://bugzilla.suse.com/attachment.cgi?id=809885&action=edit supportconfig output -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

15:49

New subject: [Bug 1140907] Since recent update smb share no longer accessible to Windows10 guest running on same host

http://bugzilla.suse.com/show_bug.cgi?id=1140907 http://bugzilla.suse.com/show_bug.cgi?id=1140907#c2 --- Comment #2 from Bruce Rogers --- Created attachment 809886 --> http://bugzilla.suse.com/attachment.cgi?id=809886&action=edit Samba log data in /tmp/samba.bfr.log -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:02

New subject: [Bug 1140907] Since recent update smb share no longer accessible to Windows10 guest running on same host

http://bugzilla.suse.com/show_bug.cgi?id=1140907 http://bugzilla.suse.com/show_bug.cgi?id=1140907#c3 David Mulder changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david.mulder@suse.com --- Comment #3 from David Mulder --- A tcpdump shows no smb traffic at all. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:04

New subject: [Bug 1140907] Since recent update smb share no longer accessible to Windows10 guest running on same host

http://bugzilla.suse.com/show_bug.cgi?id=1140907 http://bugzilla.suse.com/show_bug.cgi?id=1140907#c4 David Disseldorp changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ddiss@suse.com --- Comment #4 from David Disseldorp --- (In reply to David Mulder from comment #3)

...

A tcpdump shows no smb traffic at all.

Could be an issue with the firewall? -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:19

New subject: [Bug 1140907] Since recent update smb share no longer accessible to Windows10 guest running on same host

http://bugzilla.suse.com/show_bug.cgi?id=1140907 http://bugzilla.suse.com/show_bug.cgi?id=1140907#c5 Noel Power changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nopower@suse.com --- Comment #5 from Noel Power --- (In reply to David Disseldorp from comment #4)

...

(In reply to David Mulder from comment #3)

...
A tcpdump shows no smb traffic at all.

Could be an issue with the firewall?

or perhaps not getting the correct interface, since this is all host based probably this is going though lo also I'd a) bump the debug to 10 b) try smbclient locally too -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

16:48

New subject: [Bug 1140907] Since recent update smb share no longer accessible to Windows10 guest running on same host

http://bugzilla.suse.com/show_bug.cgi?id=1140907 http://bugzilla.suse.com/show_bug.cgi?id=1140907#c6 --- Comment #6 from David Mulder ---

...

...
Could be an issue with the firewall?

Firewall is off.

...

or perhaps not getting the correct interface, since this is all host based probably this is going though lo

He specified the interface in the tcpdump. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:06

New subject: [Bug 1140907] Since recent update smb share no longer accessible to Windows10 guest running on same host

http://bugzilla.suse.com/show_bug.cgi?id=1140907 http://bugzilla.suse.com/show_bug.cgi?id=1140907#c7 --- Comment #7 from Bruce Rogers --- I tried this: smbclient \\\\192.168.100.1\\SharedWithWindows <wrong-password> Unable to initialize messaging context Anonymous login successful tree connect failed: NT_STATUS_ACCESS_DENIED and this: smbclient \\\\192.168.100.1\\SharedWithWindows <appropriate-password> Unable to initialize messaging context Try "help" to get a list of possible commands. smb: \> ls . D 0 Tue Jul 9 08:41:15 2019 .. D 0 Tue Jul 9 10:33:43 2019 $RECYCLE.BIN D 0 Sun Jun 4 11:22:40 2017 .Trash-1000 DH 0 Sun Sep 17 08:43:14 2017 added-no-marr-or-children.ged N 1277 Fri Jan 1 09:26:12 2016 all-with-fsid.txt N 8426917 Tue Dec 29 16:40:58 2015 AMD SEV-ES.pdf A 887364 Wed Oct 17 09:19:02 2018 ... Hopefully that provides some useful feedback. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:18

New subject: [Bug 1140907] Since recent update smb share no longer accessible to Windows10 guest running on same host

http://bugzilla.suse.com/show_bug.cgi?id=1140907 http://bugzilla.suse.com/show_bug.cgi?id=1140907#c8 David Mulder changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #8 from David Mulder --- The box isn't even reachable by the Windows client. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

17:36

New subject: [Bug 1140907] Since recent update smb share no longer accessible to Windows10 guest running on same host

http://bugzilla.suse.com/show_bug.cgi?id=1140907 http://bugzilla.suse.com/show_bug.cgi?id=1140907#c9 Bruce Rogers changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED --- Comment #9 from Bruce Rogers --- (In reply to David Mulder from comment #8)

...

The box isn't even reachable by the Windows client.

Let me investigate the networking situation, and then provide more feedback here. Thanks for your help so far. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10 Jul 10 Jul

17:14

New subject: [Bug 1140907] Since recent update smb share no longer accessible to Windows10 guest running on same host

http://bugzilla.suse.com/show_bug.cgi?id=1140907 http://bugzilla.suse.com/show_bug.cgi?id=1140907#c10 --- Comment #10 from Bruce Rogers --- Although reboots of both host and guest never improved the situation, I just did a zypper dup, as there was another Tumbleweed release, and after that, and a reboot, the Windows10 guest could once again access the smb share. I don't now what changed this time (list of packages didn't call anything out in particular), but at least I'm working again. I guess it will remain a mystery what was broken and how it got fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1762

Age (days ago)

1763

Last active (days ago)

List overview

Download

10 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 1140907] New: Since recent update smb share no longer accessible to Windows10 guest running on same host

tags

participants (1)