The Samba-Bugzilla – Bug 6949
XP Home SP3 cause internal error in samba
Last modified: 2012-09-12 08:03:09 UTC
Access or authentication cause internal error in samba.
See logs here:
Same resource can be access from XP Pro.
Platform is debian
samba was installed from:
ii samba 2:3.4.3-1 SMB/CIFS file, print, and login server for U
ii samba-common 2:3.4.3-1 common files used by both the Samba server a
ii samba-common-bin 2:3.4.3-1 common files used by both the Samba server a
Can you try running this under valgrind ? Or if you can't do that can you try capturing this under gdb and getting a stack backtrace with complete symbols ?
Please upload a full debug level 10 log together with your smb.conf and a network trace of that failure. Information on how to create network traces can be found under http://wiki.samba.org/index.php/Capture_Packets.
I have included new logs with level 10:
Tried to reproduce with your smb.conf, but I could not so far. I have some comments though:
Your smb.conf has an error. You're using "security=server" without giving a password server. What did you intend by setting it to server?
Unfortunately the debug log is not level 10. Please set "log level = 10" and re-upload "log.mini".
Please also try to install the debuginfo .deb so that we get line numbers for the crash.
The problem seems to be misconfiguration. After fixing those things pointed out its started to work. Thank for you help!
I would still like to see the log files I asked for, we should never ever abort.
What log file would you like to see if its not crashing anymore?
I take it back. I could access using IP address in the url. It still does not work with NETBIOS name.
I would like to see a debug level 10 log of the panic. The one you uploaded was only debug level 1.
Ok. Here you are:
config with security=server:
log with PANIC:
config with security=user:
log, access to \\spidernest\tf failed
log, access to \\192.168.0.1\tf successful
Lowering severity as it works fine when the password server is set.
i think this is not an issue in current samba releases. if you still have the problem with latest 3.6, plrease reopen and attach a network sniff made on the client. Thanks!