Hello, I use SAMBA under OpenBSD 2.8. When the clients log in some times they have a reject : Authentificate Failure... And in the log we can observe the same time : getpeername failed. Error was Socket is not connected ? Can somebody help me please ? Thanks -------------- next part -------------- HTML attachment scrubbed and removed
Hello, I use SAMBA under OpenBSD 2.8. When the clients log in some times they have a reject : Authentificate Failure... And in the log we can observe the same time : getpeername failed. Error was Socket is not connected ? Can somebody help me please ? Thanks
hi,
i upgraded from 2.0.7 to 2.2 last night hoping to lose these getpeername
errors that show up in my log.smbd.0.0.0.0 file (and now also
/var/log/messages YIKES!).
grepping on the time in my samba log files, i come up with at least three
different cases for when this error occurs: a denied connection because
the ip is not allowed; a bad user map (when 2.2 upgrade didn't restore
smbuser); and a successful connection. the first kind happens ALOT, though
i don't know why? perhaps the election process or some other such
windows magic?
i also include my smb.conf (which i did restore with path corrections),
perhaps with your experience you'll see something right away that escapes
me.
how can i get rid of these getpeername errors?
thanks!!
elena
[2001/05/01 02:08:25, 0] lib/util_sock.c:get_socket_addr(1084)
getpeername failed. Error was Bad file descriptor
[2001/05/01 02:08:25, 0] lib/util_sock.c:get_socket_addr(1084)
getpeername failed. Error was Bad file descriptor
[2001/05/01 02:08:25, 0] lib/access.c:check_access(324)
Denied connection from (129.24.181.51)
[2001/05/01 02:08:25, 1] smbd/process.c:process_smb(824)
Connection denied from 129.24.181.51
-----------
[2001/05/01 08:09:48, 0] lib/util_sock.c:get_socket_addr(1084)
getpeername failed. Error was Bad file descriptor
[2001/05/01 08:09:48, 0] lib/util_sock.c:get_socket_addr(1084)
getpeername failed. Error was Bad file descriptor
[2001/05/01 08:09:48, 1] smbd/password.c:pass_check_smb(526)
Couldn't find user 'pboyd' in UNIX password database.
[2001/05/01 08:09:48, 1] smbd/reply.c:reply_sesssetup_and_X(975)
Rejecting user 'pboyd': authentication failed
----------
[2001/05/01 07:32:17, 0] lib/util_sock.c:get_socket_addr(1084)
getpeername failed. Error was Bad file descriptor
[2001/05/01 07:32:17, 0] lib/util_sock.c:get_socket_addr(1084)
getpeername failed. Error was Bad file descriptor
[2001/05/01 07:32:17, 1] smbd/service.c:make_connection(638)
conf2 (129.24.176.41) connect to service conf as user slullie (uid=526,
gid=2\
40) (pid 30230)
/etc/samba/smb.conf:
# Samba config file created using SWAT
# from localhost.localdomain (127.0.0.1)
# Date: 2000/10/23 14:00:49
# Global parameters
[global]
workgroup = bsvcs-grp
netbios name = WhateverItTakes
server string = UNM Business Services
encrypt passwords = Yes
update encrypted = Yes
unix password sync = Yes
passwd program = /usr/bin/passwd
username map = /etc/samba/smbusers
log file = /var/log/samba/log.%m.%I
log level = 1
max log size = 15
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
load printers = No
domain logons = Yes
preferred master = No
domain master = No
dns proxy = No
name resolve order = lmhosts hosts bcast
invalid users = root bin daemon adm sync shutdown \
halt mail news uucp operator gopher \
nobody games ftp lp xfs named gdm \
piranha postgres pvm squid default \
autobot
hosts allow = 129.24.176. 127.0.0.1 EXCEPT 129.24.180.
129.24.178. 129\
.24.177. 129.24.179. 129.24.181. 129.24.182 129.24.183
directory mask = 0770
create mask = 0770
force create mode = 0770
force directory mode = 0770
[homes]
comment = Home Directories
read only = No
browseable = No
directory mask = 0700
create mask = 0700
force create mode = 0700
force directory mode = 0700
[support]
path = /home/support
comment = Tech Support
writeable = yes
valid users = @support
force group = support
[business]
path = /home/business
comment = Business Services
writeable = yes
valid users = @business @support
force group = business
.
.
.
[root@wit /etc]# testparm
Load smb config files from /etc/samba/smb.conf
INFO: Debug class all level = 1 (pid 30978 from pid 30978)
Loaded services file OK.
Anyone know what's up with this? Jun 20 09:48:37 alsi smbd[5235]: [2003/06/20 09:48:26, 0] lib/util_sock.c:get_socket_addr(895) Jun 20 09:48:37 alsi smbd[5235]: getpeername failed. Error was Transport endpoint is not connected Jun 20 09:48:37 alsi smbd[5235]: [2003/06/20 09:48:26, 0] lib/util_sock.c:write_socket_data(388) Jun 20 09:48:37 alsi smbd[5235]: write_socket_data: write failure. Error Connection reset by peer Jun 20 09:48:37 alsi smbd[5235]: [2003/06/20 09:48:26, 0] lib/util_sock.c:write_socket(413) Jun 20 09:48:37 alsi smbd[5235]: write_socket: Error writing 4 bytes to socket 17: ERRNO = Connection reset by peer Jun 20 09:48:37 alsi smbd[5235]: [2003/06/20 09:48:26, 0] lib/util_sock.c:send_smb(574) Jun 20 09:48:37 alsi smbd[5235]: Error writing 4 bytes to client. -1. (Connection reset by peer) I have redhat 9, and did a rpm -Uvh to the latest release. I am now seeing these errors quite often (didn't before upgrade) and I've also noticed some names aren't resolving like: 192.168.1.102.log instead of machine1.log. Samba is not the wins server (looks to a windows machine). Security is share. Any thoughts would be helpful! t o n y A.G. (Tony) Nichols I.S. Manager Appalachian Log Structures Inc. www.applog.com tony@mail.applog.com
Hi, I'm using Samba 3.0beta2, and I am getting the following errors in log.smbd every time a machine connects: [2003/07/10 15:09:22, 0] lib/util_sock.c:get_socket_addr(895) getpeername failed. Error was Transport endpoint is not connected At the same time I get a log.0.0.0.0 file, as well as a log.machinename and log.ip.addr.of.machine file. I did some searching and found some reports saying that this was a DNS reverse lookup problem. However, I have checked and nslookup machinename works, as does nslookup ip.addr.of.machine (although it returns "machinename.domainname." because that's what the W2K DNS server has defined automatically). WINS is not running on our network. The two machines in question (the server and the client machine connecting to it) are on the same domain and the same subnet - the client is running Windows 2000 Server and the Samba server is running on a fairly clean install of Red Hat Linux 9.0. There is no firewalling between the two machines. Samba 3.0beta2 was compiled from source. This problem does not appear to be adversely affecting Samba's operation, but it would be nice to figure out why it is occurring. Cheers, Paul --------------------------------------------------------- Paul Eggleton Ph: +64-9-4154790 Software Developer Fax: +64-9-4154791 CJN Technologies Ltd. DDI: +64-9-4154795 http://www.cjntech.co.nz Email: paule@cjntech.co.nz ---------------------------------------------------------