Created attachment 8522 [details] Network traffic a smbd -b output We are using a samba 3.4.7 server compiled (smb -b output attached), with Windows XP everything is OK but with Windows 7 we have some problems after joining succcessfully to the domain, when logging in and logging off with a domain user it takes about 10 minutes and the client freezes and waiting endlessly. After 10 minutes has passed, the client works fine. We have used the settings from: http://wiki.samba.org/index.php/Windows7 We have checked the DNS and NTP settings and everything seems OK. The network traffic of the conection is attached .
You only included 2 minutes of network traffic from the smbd.log where nothing really is apparent. Just seeing the roaming profile copied to the samba server. My guess is that the client is attempting to connect the home share of that particular user. Is a \\servername\username share accessible for that user logging in/off ? Please test this.
The problem occurs when a domain user or local user log in or log out, and only the first time, after rebooting PC. This is odd, since we are planning to migrate our "old" and "very stable" samba version 3.0.22 to a new one, just to support Windows 7. We are working in the public administration in Spain and we have a big scenario, with 200 servers running Samba and 8000 clients running Windows XP. In the logs attached we saw intermitens messages while the PC is frozen, trying to start session: [2013/01/30 14:49:40, 0] lib/util_sock.c:539(read_fd_with_timeout) [2013/01/30 14:49:40, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was El otro extremo de la conexión no está conectado read_fd_with_timeout: client 0.0.0.0 read error = Conexión reinicializada por la máquina remota. [2013/01/30 14:49:40, 3] smbd/sec_ctx.c:310(set_sec_ctx) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2013/01/30 14:49:40, 3] smbd/connection.c:31(yield_connection) Yielding connection to [2013/01/30 14:49:40, 3] smbd/server.c:845(exit_server_common) Server exit (failed to receive smb request) [2013/01/30 14:50:04, 0] lib/util_sock.c:539(read_fd_with_timeout) [2013/01/30 14:50:04, 0] lib/util_sock.c:1491(get_peer_addr_internal) getpeername failed. Error was El otro extremo de la conexión no está conectado read_fd_with_timeout: client 0.0.0.0 read error = Conexión reinicializada por la máquina remota.
We have changed the client architecture, in fact is 32 bits.
In order to help you, could you please be so kind to answer the question from comment #1 ? Thanks.
Sorry, I was just gathering some aditional info. When the client takes so long for logging in/off it's frozen, and we cannot check whether the share is accesible, in the logs we didn't see any error related to an unaccessible share. Is there any way for testing it?
closing after years of inactivity, this is abviously a problem of this particular setup and not a generic problem also