Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3769 - samba-3.0.21a doesn't work in some situations

Attached to Project: Arch Linux
Opened by Scott Robbins (scottro111) - Saturday, 14 January 2006, 01:06 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

In some situations, after upgrading to 3.0.21a, samba will stop working. The MS clients will usually get an error message along the lines of "The network resource is no longer available." Tests in the latest Samba-HowTo Troubleshooting section will work on the samba server. Running nbtstat on the client, and pinging the samba server by name will also work, however, if one runs net view <samba server> one will get an error message that the resource isn't available. Any attempt to connect, whether through browsing the network or MS command line net use will also have an error.

The problem has been reported in samba's bugzilla.

https://bugzilla.samba.org/show_bug.cgi?id=3401

Although it is marked as fixed, (I'm the Scott who said that it worked in FreeBSD) applying the patch to the Arch sources didn't fix the problem. The panic that the bug mentions is lib.c/panic_smb2(1554).

The problem doesn't occur in a all situations--on a Debian list it was thought that it was related to setting security = server in smb.conf, but testing indicated that using the preferred "domain" or even "user" didn't solve the problem.

This task depends upon

Closed by  Judd Vinet (judd)
Thursday, 19 January 2006, 08:05 GMT
Reason for closing:  Fixed
Comment by Scott Robbins (scottro111) - Sunday, 15 January 2006, 18:55 GMT
Further investigation indicates this may be a different bug than the samba bug mentioned above. What makes it more difficult is that it's not consistantly reproducible.

It seems to happen on an NT domain, if the MS machine is on a different subnet. If I have time next week, I'll see if I can investigate further. With the fix listed in the samba bug, it now works on FreeBSD machines with an indentical smb.conf.



Comment by Scott Robbins (scottro111) - Monday, 16 January 2006, 16:45 GMT
Further research indicates that the attached patch fixes the problem, as it did on FreeBSD.
(application/octet-stream)    ntlmssp.c.patch (0.3 KiB)
Comment by Judd Vinet (judd) - Thursday, 19 January 2006, 08:05 GMT
Added for 3.0.21a-2

Loading...