Using the RTM version of Windows XP Professional, x64 Edition (AMD64), no
connection to the samba server 3.0.11 is possible. Windows returns the error message
"\\servername is not accessible. You might not have permission to use this
network resource. Contact the administrator of this server to find out if you
have access permissions.
The request is not supported."
Accessing the same server using Windows XP Professional (32-bit) is no problem.
/var/log/samba/uranos-64.log (name of my workstation) contains:
[2005/04/07 13:22:03, 0] lib/util_sock.c:write_socket_data(430)
write_socket_data: write failure. Error = Connection reset by peer
[2005/04/07 13:22:03, 0] lib/util_sock.c:write_socket(455)
write_socket: Error writing 4 bytes to socket 6: ERRNO = Connection reset by peer
[2005/04/07 13:22:03, 0] lib/util_sock.c:send_smb(647)
Error writing 4 bytes to client. -1. (Connection reset by peer)
please attach a raw ethereal trace to this report of
the failed connection attempt. Thanks.
Created attachment 1171 [details]
Failed connection attempt
This capture is worthless I'm afraid. We need a binary file containing the data,
not a truncated text file (why do people keep thinking that capture traces are
*text* files. It is still a mystery to me).
I'm regularly getting plain stdout of tcpdump. We should really document 'tcpdump -i eth0 -n -s 1500 -w /tmp/sniff' a lot more prominent -- any suggestions for a place to do it?
Created attachment 1215 [details]
Failed connection attempt, new format
I can reproduce it here. The session setup request for NTLMSSP_NEGOTIATE
contains another null byte terminator after the "native os" string which results
in "native lanmanager" being empty and "primary domain" being what should be
"native lan manager". Why the hell..?
fixed with svn r7708 , thanks Jeremy and Luke.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.