Oct 24 15:44:05 mainserver samba(pam_unix)[32338]: session opened for user magesh.prabhu by (uid=0)
Oct 24 15:44:22 mainserver samba(pam_unix)[32346]: session opened for user sujatha.p by (uid=0)
Oct 24 15:44:33 mainserver smbd[32351]: [2008/10/24 15:44:33, 0] lib/util_sock.c:get_peer_a
ddr(1224)
Oct 24 15:44:34 mainserver smbd[32351]: getpeername failed. Error was Transport endpoint is not connected
Oct 24 15:44:34 mainserver smbd[32351]: [2008/10/24 15:44:34, 0] lib/access.c:check_access(
327)
Oct 24 15:44:34 mainserver smbd[32351]: [2008/10/24 15:44:34, 0] lib/util_sock.c:get_peer_a
ddr(1224)
Oct 24 15:44:34 mainserver smbd[32351]: getpeername failed. Error was Transport endpoint is not connected
Oct 24 15:44:34 mainserver smbd[32351]: Denied connection from (0.0.0.0)
Oct 24 15:44:34 mainserver smbd[32351]: [2008/10/24 15:44:34, 0] lib/util_sock.c:get_peer_a
ddr(1224)
Oct 24 15:44:34 mainserver smbd[32351]: getpeername failed. Error was Transport endpoint is not connected
Oct 24 15:44:34 mainserver smbd[32351]: Connection denied from 0.0.0.0
Oct 24 15:44:34 mainserver smbd[32351]: [2008/10/24 15:44:34, 0] lib/util_sock.c:write_data
(562)
Oct 24 15:44:34 mainserver smbd[32351]: write_data: write failure in writing to client 192.168.10.140. Error Connection reset by peer
Oct 24 15:44:34 mainserver smbd[32351]: [2008/10/24 15:44:34, 0] lib/util_sock.c:send_smb(7
61)
Oct 24 15:44:34 mainserver smbd[32351]: Error writing 5 bytes to client. -1. (Connection reset by peer)
Oct 24 15:44:34 mainserver samba(pam_unix)[32352]: session opened for user selva.kumar by (uid=0)
Oct 24 15:44:34 mainserver samba(pam_unix)[24942]: session closed for user selva.kumar
Oct 24 15:44:34 mainserver samba(pam_unix)[25527]: session closed for user magesh.prabhu
Oct 24 15:44:34 mainserver samba(pam_unix)[25205]: session closed for user sujatha.p
Above is a sample of logs from the "messages" log file. We have a network with Windows XP systems (SP2) and patched for all critical updates.
The distribution of Linux we run is Red Hat Enterprise ES 4.0. The samba server has been configured as a domain controller (without LDAP). Of late we have observed that Windows XP client systems are posing problems while logging on to the domain. After entering the username and password, some client systems get stuck at the stage of "Loading Personal profile" and do not proceed further. Of course, we have figured a way out by unplugging the network cord and logging on and then connecting the cord so that the server can be accessed.
Can someone provide a hint or a solution to solve this problem?