I have 2 servers, both act as Samba server also. One is domain master (manages profiles, shares network drives). Users home directories are in second server. Second one has had Suse 9.1 for almost a year, and sometimes error messages like below appared. But now I moved first server from RH to Suse also, and now these messages occur often in both server log files. But everything seems to work nicely! Are they somekind warnings? Or something more serious? Mar 31 10:20:06 xxx smbd[29078]: [2005/03/31 10:20:06, 0] lib/util_sock.c:get_peer_addr(1136) Mar 31 10:20:06 xxx smbd[29078]: getpeername failed. Error was Transport endpoint is not connected Mar 31 10:20:06 xxx smbd[29078]: [2005/03/31 10:20:06, 0] lib/util_sock.c:write_socket_data(430) Mar 31 10:20:06 xxx smbd[29078]: write_socket_data: write failure. Error = Connection reset by peer Mar 31 10:20:06 xxx smbd[29078]: [2005/03/31 10:20:06, 0] lib/util_sock.c:write_socket(455) Mar 31 10:20:06 xxx smbd[29078]: write_socket: Error writing 4 bytes to socket 23: ERRNO = Connection reset by peer Mar 31 10:20:06 xxx smbd[29078]: [2005/03/31 10:20:06, 0] lib/util_sock.c:send_smb(647) Mar 31 10:20:06 xxx smbd[29078]: Error writing 4 bytes to client. -1. (Connection reset by peer)
On Thursday 31 March 2005 09:22, Taavi Dovnar wrote:
I have 2 servers, both act as Samba server also. One is domain master (manages profiles, shares network drives). Users home directories are in second server.
Second one has had Suse 9.1 for almost a year, and sometimes error messages like below appared. But now I moved first server from RH to Suse also, and now these messages occur often in both server log files. But everything seems to work nicely! Are they somekind warnings? Or something more serious?
Mar 31 10:20:06 xxx smbd[29078]: [2005/03/31 10:20:06, 0] lib/util_sock.c:get_peer_addr(1136) Mar 31 10:20:06 xxx smbd[29078]: getpeername failed. Error was Transport endpoint is not connected Mar 31 10:20:06 xxx smbd[29078]: [2005/03/31 10:20:06, 0] lib/util_sock.c:write_socket_data(430) Mar 31 10:20:06 xxx smbd[29078]: write_socket_data: write failure. Error = Connection reset by peer Mar 31 10:20:06 xxx smbd[29078]: [2005/03/31 10:20:06, 0] lib/util_sock.c:write_socket(455) Mar 31 10:20:06 xxx smbd[29078]: write_socket: Error writing 4 bytes to socket 23: ERRNO = Connection reset by peer Mar 31 10:20:06 xxx smbd[29078]: [2005/03/31 10:20:06, 0] lib/util_sock.c:send_smb(647) Mar 31 10:20:06 xxx smbd[29078]: Error writing 4 bytes to client. -1. (Connection reset by peer)
Try putting "smb ports = 139" in your smb.conf, i recently saw this on the samba mailing list - something to do with XP trying 445 as well, then dropping one of them, causing this message in the logs. It worked for me! Hope that helps H
Try putting "smb ports = 139" in your smb.conf, i recently saw this on the samba mailing list - something to do with XP trying 445 as well, then dropping one of them, causing this message in the logs. It worked for me!
Only 139 is necessary?
Try putting "smb ports = 139" in your smb.conf, i recently saw this on the samba mailing list - something to do with XP trying 445 as well, then dropping one of them, causing this message in the logs. It worked for me!
Well, I'm back with my problem. I added this to conf file. But now usually once a day with one specific XP computer and sometimes with other XP machines there is problem with loading profile, it says cannot find roaming profile etc... I noticed that this is in servers log file: Apr 27 09:34:06 tigger smbd[19208]: [2005/04/27 09:34:06, 0] lib/util_sock.c:read_socket_data(384) Apr 27 09:34:06 tigger smbd[19208]: read_socket_data: recv failure for 4. Error = No route to host Any suggestions what to do??
participants (2)
-
Hamish
-
Taavi Dovnar