Results 1 to 2 of 2
I've got loads of the following in my logs, all day long it seems:
Code:
2006-06-06 17:36:45 smbd[20958]: [2006/06/06 17:38:06, 0] lib/util_sock.c:get_peer_addr(1136)
2006-06-06 17:36:45 smbd[20958]: getpeername failed. Error was Transport ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 06-06-2006 #1Linux Newbie
- Join Date
- Nov 2005
- Posts
- 225
getpeername failed. Error was Transport endpoint is not connected
I've got loads of the following in my logs, all day long it seems:
This machine is Suse 9.1 (x86-64) with samba-3.0.9-2.6.Code:2006-06-06 17:36:45 smbd[20958]: [2006/06/06 17:38:06, 0] lib/util_sock.c:get_peer_addr(1136) 2006-06-06 17:36:45 smbd[20958]: getpeername failed. Error was Transport endpoint is not connected 2006-06-06 17:36:45 smbd[20958]: [2006/06/06 17:38:06, 0] lib/access.c:check_access(328)
Why is samba generating these errors?
I think samba is probably one of the most complaining piece of software I've evver seen, couldn't have linux in anything but a unix-only shop without it though...
- 12-14-2008 #2Just Joined!
- Join Date
- Dec 2008
- Location
- Republic of Texas, Central
- Posts
- 12
getpeername failed. Error was Transport endpoint is not connected
It's probably a WinXP machine doing it... add this to smb.conf as long as it's not a PDC:
Originally Posted by humbletech99 
Code:smb ports=139
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
