Results 1 to 3 of 3
I've just found the following errors in my logs:
Code:
hostname daemon 15:19:38 smbd[13919]: Error writing 5 bytes to client. -1. (Connection reset by peer)
hostname daemon 15:19:38 smbd[13919]: [2006/05/24 ...
- 05-24-2006 #1
smbd errors
I've just found the following errors in my logs:
What on earth does this mean?Code:hostname daemon 15:19:38 smbd[13919]: Error writing 5 bytes to client. -1. (Connection reset by peer) hostname daemon 15:19:38 smbd[13919]: [2006/05/24 15:20:10, 0] lib/util_sock.c:send_smb(647) hostname daemon 15:19:38 smbd[13919]: write_socket: Error writing 5 bytes to socket 24: ERRNO = Connection reset by peer hostname daemon 15:19:38 smbd[13919]: [2006/05/24 15:20:10, 0] lib/util_sock.c:write_socket(455) hostname daemon 15:19:38 smbd[13919]: write_socket_data: write failure. Error = Connection reset by peer hostname daemon 15:19:38 smbd[13919]: [2006/05/24 15:20:10, 0] lib/util_sock.c:write_socket_data(430) hostname daemon 15:19:38 smbd[13919]: Connection denied from 0.0.0.0 hostname daemon 15:19:38 smbd[13919]: getpeername failed. Error was Transport endpoint is not connected hostname daemon 15:19:38 smbd[13919]: [2006/05/24 15:20:10, 0] lib/util_sock.c:get_peer_addr(1136) hostname daemon 15:19:38 smbd[13919]: Denied connection from (0.0.0.0) hostname daemon 15:19:38 smbd[13919]: getpeername failed. Error was Transport endpoint is not connected hostname daemon 15:19:38 smbd[13919]: [2006/05/24 15:20:10, 0] lib/util_sock.c:get_peer_addr(1136) hostname daemon 15:19:38 smbd[13919]: [2006/05/24 15:20:10, 0] lib/access.c:check_access(328) hostname daemon 15:19:38 smbd[13919]: getpeername failed. Error was Transport endpoint is not connected hostname daemon 15:19:38 smbd[13919]: [2006/05/24 15:20:10, 0] lib/util_sock.c:get_peer_addr(1136)
- 05-24-2006 #2
More details perhaps?
Which version of Samba are you using?
Which distro?
Which kernel?
What is the content of your /etc/samba/smb.conf?
How many computers is your machine serving? For what use? Which OS those machines are using?
Have you tried reading some of Samba docs?
http://us2.samba.org/samba/docs/man/"To express yourself in freedom, you must die to everything of yesterday. From the 'old', you derive security; from the 'new', you gain the flow."
-Bruce Lee
- 05-24-2006 #3
suse 9.0 with samba-2.2.8a-234 (old samba and crappy distro I know, they were set up before my time here and will be replaced)
barely used much by 30-40 clients, using a bunch of shares on windows nt/2000/xp machines via smbfs.
It's a backup machine which hoovers files from ~50 workstations and servers during the night.
I am familiar with samba docs for winbind, wins etc and am quite familiar with writing smb.conf...
I've never seen these errors before, thought somebody else might have seen them...


Reply With Quote