[Samba] Connection from WinXP 64 Bit to Samba server broken?

Andreas Haumer andreas at xss.co.at
Wed Feb 7 17:25:40 GMT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

One of our users upgraded her Windows client from Windows XP 32 Bit
to windows XP 64 bit and can not connect to any samba server in the
network since, with one exception: there is one server, running
samba-3.0.20b, which works. With other servers, running various
samba versions up to samba-3.0.23c, the Windows client can not
connect anymore (there are about 10 samba servers in the network)
Windows just says "can not access" and "the request is not supported"
(this is a rough translation, the original messages are in german)

In the samba logfiles I see the following error (example logs
from server "CDROMSRV" at aaa.bbb.ccc.27):

[...]
[2007/02/02 15:00:32, 3] smbd/sesssetup.c:reply_sesssetup_and_X_spnego(660)
  Doing spnego session setup
[2007/02/02 15:00:32, 3] smbd/sesssetup.c:reply_sesssetup_and_X_spnego(691)
  NativeOS=[Windows XP 3790 Service Pack 1] NativeLanMan=[] PrimaryDomain=[Windows XP 5.2]
[2007/02/02 15:00:32, 3] smbd/sesssetup.c:reply_spnego_negotiate(551)
  Got OID 1 3 6 1 4 1 311 2 2 10
[2007/02/02 15:00:32, 3] smbd/sesssetup.c:reply_spnego_negotiate(554)
  Got secblob of size 40
[2007/02/02 15:00:32, 3] libsmb/ntlmssp.c:debug_ntlmssp_flags(63)
  Got NTLMSSP neg_flags=0xe2088297
[2007/02/02 15:00:32, 3] lib/util_sock.c:open_socket_out(874)
  Connecting to aaa.bbb.ccc.1 at port 445
[2007/02/02 15:00:32, 3] auth/auth_server.c:server_cryptkey(75)
  connected to password server SRVL12
[2007/02/02 15:00:32, 3] auth/auth_server.c:server_cryptkey(100)
  got session
[2007/02/02 15:00:32, 3] auth/auth_server.c:server_cryptkey(133)
  password server OK
[2007/02/02 15:00:32, 3] auth/auth_server.c:auth_get_challenge_server(183)
  using password server validation
[2007/02/02 15:00:32, 3] smbd/process.c:timeout_processing(1359)
  timeout_processing: End of file from client (client has disconnected).
[2007/02/02 15:00:32, 3] smbd/sec_ctx.c:set_sec_ctx(241)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2007/02/02 15:00:32, 3] smbd/connection.c:yield_connection(69)
  Yielding connection to
[2007/02/02 15:00:32, 3] smbd/server.c:exit_server_common(675)
  Server exit (normal exit)


This looks like the client just closes the connection before
it even authenticates. This is consistent with the network
traffic dump I took (the client in question has address aaa.bbb.ccc.125):
[...]
112.287218  aaa.bbb.ccc.125        aaa.bbb.ccc.27         TCP      jvserver > netbios-ssn [SYN] Seq=0 Len=0 MSS=1460
112.287241  aaa.bbb.ccc.27         aaa.bbb.ccc.125        TCP      netbios-ssn > jvserver [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460
112.287346  aaa.bbb.ccc.125        aaa.bbb.ccc.27         NBSS     Session request, to CDROMSRV<20> from PCI1HAG<00>
112.287362  aaa.bbb.ccc.27         aaa.bbb.ccc.125        TCP      netbios-ssn > jvserver [ACK] Seq=1 Ack=73 Win=5840 Len=0
112.305943  aaa.bbb.ccc.27         aaa.bbb.ccc.125        NBSS     Positive session response
112.306197  aaa.bbb.ccc.125        aaa.bbb.ccc.27         SMB      Negotiate Protocol Request
112.307402  aaa.bbb.ccc.27         aaa.bbb.ccc.125        SMB      Negotiate Protocol Response
112.307753  aaa.bbb.ccc.125        aaa.bbb.ccc.27         SMB      Session Setup AndX Request, NTLMSSP_NEGOTIATE
112.324275  aaa.bbb.ccc.27         aaa.bbb.ccc.125        SMB      Session Setup AndX Response, NTLMSSP_CHALLENGE, Error: STATUS_MORE_PROCESSING_REQUIRED
112.325025  aaa.bbb.ccc.125        aaa.bbb.ccc.27         SMB      Session Setup AndX Request, NTLMSSP_NEGOTIATE
112.339736  aaa.bbb.ccc.27         aaa.bbb.ccc.125        SMB      Session Setup AndX Response, NTLMSSP_CHALLENGE, Error: STATUS_MORE_PROCESSING_REQUIRED
112.340073  aaa.bbb.ccc.125        aaa.bbb.ccc.27         TCP      jvserver > netbios-ssn [FIN, ACK] Seq=678 Ack=716 Win=63797 Len=0
112.341426  aaa.bbb.ccc.27         aaa.bbb.ccc.125        TCP      netbios-ssn > jvserver [FIN, ACK] Seq=716 Ack=679 Win=8576 Len=0
112.341539  aaa.bbb.ccc.125        aaa.bbb.ccc.27         TCP      jvserver > netbios-ssn [ACK] Seq=679 Ack=717 Win=63797 Len=0
[...]


Before the upgrade to WinXP 64 bit, the client had no
problems to connect to any of the samba servers in the
network. Also all other (about 100) windows clients
(running WinXP and Win2K, all 32 Bit) do not show any
problems with any samba server.

The one server which still works with the 64Bit WinXP
works also as password server for the other samba servers
(using "security=server" in a workgroup environment)
This is at least suspect, because it seems to show a
pattern: samba servers which are using the password
server do not work with the new client, the samba
server acting as password server does work. But I can
not explain the difference and this setup works for
all other clients since more than one year now without
problems. The only change was the upgrade to 64 bit
windows on this one client machine.

Any ideas anyone?

- - andreas

- --
Andreas Haumer                     | mailto:andreas at xss.co.at
*x Software + Systeme              | http://www.xss.co.at/
Karmarschgasse 51/2/20             | Tel: +43-1-6060114-0
A-1100 Vienna, Austria             | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFyguSxJmyeGcXPhERAuHuAKC0+ldDyN9GnRIaEaaWmp3oTXe2sQCgpdHh
Vumg9rdGPU8fY5kRfBQRyAA=
=BMqz
-----END PGP SIGNATURE-----


More information about the samba mailing list