[opensuse] latest samba online update 3.5 -> 3.6
Hi, Yesterday I've got samba auto-updated to 3.6 on an openSUSE 11.4 box. Now the shares are not accessible and not even browsable from our windows machines. I have this setup working since 5 years without any changes security = ADS realm = BLA.LOCAL encrypt passwords = yes password server = w2K3_sbs.bla.local username map = /etc/samba/smbusers Couldn't find anything useful in the logs. Downgrading to 3.5 fixed it again. I can't investigate the problem before weekend but maybe someone else had similar trouble and some hints for me. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Rudi, On Tue, Apr 17, 2012 at 11:54:42AM +0200, Ruediger Meier wrote:
Yesterday I've got samba auto-updated to 3.6 on an openSUSE 11.4 box. Now the shares are not accessible and not even browsable from our windows machines. I have this setup working since 5 years without any changes
security = ADS realm = BLA.LOCAL
While your workgroup setting is workgroup = BLA ? I've tested this with a fresh install before and after the update to Samba 3.6.3 (plus sec fix). It's working in both cases as expected. Was this a manual configuration or did you use the YaST Windows Domain Membership module? Please be this nice and report this via bugzilla.novell.com. You can assign it directly to me. Please also report the URL to the bug back to the list. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Tuesday 17 April 2012, Lars Müller wrote:
Hi Rudi,
On Tue, Apr 17, 2012 at 11:54:42AM +0200, Ruediger Meier wrote:
Yesterday I've got samba auto-updated to 3.6 on an openSUSE 11.4 box. Now the shares are not accessible and not even browsable from our windows machines. I have this setup working since 5 years without any changes
security = ADS realm = BLA.LOCAL
While your workgroup setting is
workgroup = BLA
?
Yes.
I've tested this with a fresh install before and after the update to Samba 3.6.3 (plus sec fix). It's working in both cases as expected.
Was this a manual configuration or did you use the YaST Windows Domain Membership module?
I think I never used yast. I guess I have added that machine from within SBS server.
Please be this nice and report this via bugzilla.novell.com. You can assign it directly to me. Please also report the URL to the bug back to the list.
I'll try to find out more next days when I have time and users are offline. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Might this be an AppArmor issue? If AppArmor is active you might be faced by the same trouble as described by https://bugzilla.novell.com/show_bug.cgi?id=758426 Comment #2 describes which information is needed. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2012-04-17 at 13:23 +0200, Lars Müller wrote:
Please be this nice and report this via bugzilla.novell.com. You can assign it directly to me. Please also report the URL to the bug back to the list.
How about: https://bugzilla.novell.com/show_bug.cgi?id=758426 - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk+T92sACgkQtTMYHG2NR9UO3ACghc9+IPPW5wQFyLBDS0hsLva3 jBcAnA+RF71kS1r3O4zVhiAUdMXCIerk =IxhN -----END PGP SIGNATURE-----
participants (3)
-
Carlos E. R.
-
Lars Müller
-
Ruediger Meier