Fellows, I need some help regarding this thing!1! I get tons of messages like this ? Can anyone help me with resolving this problem ? Dec 18 13:52:42 constellation smbd[8063]: [2005/12/18 13:52:42, 0] lib/util_sock.c:send_smb(647) Dec 18 13:52:42 constellation smbd[8063]: Error writing 4 bytes to client. -1. (Connection reset by peer) Dec 18 14:00:01 constellation crond(pam_unix)[8126]: session opened for user root by (uid=0) Dec 18 14:00:04 constellation syslogd 1.4.1: restart. Dec 18 14:00:04 constellation crond(pam_unix)[8126]: session closed for user root Dec 18 14:01:01 constellation crond(pam_unix)[8136]: session opened for user root by (uid=0) Dec 18 14:01:02 constellation crond(pam_unix)[8136]: session closed for user root Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:get_peer_addr(1150) Dec 18 14:24:55 constellation smbd[8333]: getpeername failed. Error was Transport endpoint is not connected Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:write_socket_data(430) Dec 18 14:24:55 constellation smbd[8333]: write_socket_data: write failure. Error = Connection reset by peer Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:write_socket(455) Dec 18 14:24:55 constellation smbd[8333]: write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer Thanks ! -- Franck
Fellows, I need some help regarding this thing!1! I get tons of messages like this ? Can anyone help me with resolving this problem ? Dec 18 13:52:42 constellation smbd[8063]: [2005/12/18 13:52:42, 0] lib/util_sock.c:send_smb(647) Dec 18 13:52:42 constellation smbd[8063]: Error writing 4 bytes to client. -1. (Connection reset by peer) Dec 18 14:00:01 constellation crond(pam_unix)[8126]: session opened for user root by (uid=0) Dec 18 14:00:04 constellation syslogd 1.4.1: restart. Dec 18 14:00:04 constellation crond(pam_unix)[8126]: session closed for user root Dec 18 14:01:01 constellation crond(pam_unix)[8136]: session opened for user root by (uid=0) Dec 18 14:01:02 constellation crond(pam_unix)[8136]: session closed for user root Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:get_peer_addr(1150) Dec 18 14:24:55 constellation smbd[8333]: getpeername failed. Error was Transport endpoint is not connected Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:write_socket_data(430) Dec 18 14:24:55 constellation smbd[8333]: write_socket_data: write failure. Error = Connection reset by peer Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] lib/util_sock.c:write_socket(455) Dec 18 14:24:55 constellation smbd[8333]: write_socket: Error writing 4 bytes to socket 24: ERRNO = Connection reset by peer Thanks ! -- Franck
Franck Y wrote:>Fellows, >I need some help regarding this thing!1! >I get tons of messages like this ? >Can anyone help me with resolving this problem ? > >Dec 18 13:52:42 constellation smbd[8063]: [2005/12/18 13:52:42, 0] >lib/util_sock.c:send_smb(647) >Dec 18 13:52:42 constellation smbd[8063]: Error writing 4 bytes to >client. -1. (Connection reset by peer) >Dec 18 14:00:01 constellation crond(pam_unix)[8126]: session opened >for user root by (uid=0) >Dec 18 14:00:04 constellation syslogd 1.4.1: restart. >Dec 18 14:00:04 constellation crond(pam_unix)[8126]: session closed >for user root >Dec 18 14:01:01 constellation crond(pam_unix)[8136]: session opened >for user root by (uid=0) >Dec 18 14:01:02 constellation crond(pam_unix)[8136]: session closed >for user root >Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] >lib/util_sock.c:get_peer_addr(1150) >Dec 18 14:24:55 constellation smbd[8333]: getpeername failed. Error >was Transport endpoint is not connected >Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] >lib/util_sock.c:write_socket_data(430) >Dec 18 14:24:55 constellation smbd[8333]: write_socket_data: write >failure. Error = Connection reset by peer >Dec 18 14:24:55 constellation smbd[8333]: [2005/12/18 14:24:55, 0] >lib/util_sock.c:write_socket(455) >Dec 18 14:24:55 constellation smbd[8333]: write_socket: Error >writing 4 bytes to socket 24: ERRNO = Connection reset by peer > > >Thanks ! >-- >Franck > >Does this happen when you are doing something in particular? --Dennis
Franck Y wrote:>Hello, >Thanks for your reply ! >Not something in particular but i get more when i was doing a backup.... >It s so weird. >I think it something with acces to files u don t know and it pi**ing me off... >Franck > >To my understanding Windows (XP at least) tries to connect to both port 139 and 445 (it sends the request to each port at basically the same time). If it receives a response on port 445 it will drop the connection to 139, but it doesn't do it gracefully and so the samba server just says "connection reset by peer". The default behavoir of samba is to listen on both ports (since it's the default for windows). You can override it in smb.conf and tell samba to only listen on one of the ports. It could also be a problem with oplocks, but I'm not familiar with those at all so somebody else will have to chime in. --Dennis