Samba problems

Craig White craigwhite at azapple.com
Sun Feb 12 22:44:09 UTC 2006


On Sun, 2006-02-12 at 22:28 +0000, Anne Wilson wrote:
> On this mixed LAN I use samba for all connections, but at the moment I'm 
> having problems.
> 
> Smbd and nmbd are running on the server.  All users have accounts on the 
> server and are added to smbpasswd.  The printers are not broadcasting, and I 
> can't make samba connections from remote boxes.
> 
> /var/log/samba/0.0.0.0.log shows
> 
> [2006/02/12 21:27:28, 0] lib/util_sock.c:get_peer_addr(1150)
>   getpeername failed. Error was Transport endpoint is not connected
>   Connection denied from 0.0.0.0
> [2006/02/12 21:27:28, 0] lib/util_sock.c:write_socket_data(430)
>   write_socket_data: write failure. Error = Connection reset by peer
> [2006/02/12 21:27:28, 0] lib/util_sock.c:write_socket(455)
>   write_socket: Error writing 5 bytes to socket 5: ERRNO = Connection reset by 
> peer
> [2006/02/12 21:27:28, 0] lib/util_sock.c:send_smb(647)
>   Error writing 5 bytes to client. -1. (Connection reset by peer)
> 
> /var/log/samba/192.168.0.92.log shows
> 
> [2006/02/11 19:40:46, 0] smbd/service.c:make_connection_snum(615)
>   '' does not exist or is not a directory, when connecting to [homes]
> [2006/02/12 22:08:29, 0] smbd/service.c:make_connection_snum(615)
>   '' does not exist or is not a directory, when connecting to [homes]
> 
> SELinux is installed but disabled, as is the firewall (hardware firewall on 
> the LAN).
> 
> Any pointers, please?
----
ignore these messages...well perhaps the issue of homes you should fix
as your [homes] share isn't working right but the others are standard
fare.

to see a complaint about your [homes] share, try...
# testparm -s

A quick explanation of the 'Error was Transport endpoint'/error writing
5 bytes to... messages

Traditionally, SMB connections were on port 139. Win2K and WinXP will
connect simultaneously to ports 139 & 445 and rudely drop 445 when they
get what they want from port 139. The logged error is samba simply
logging the notice of the fact that the port connection simply dropped
communications, nothing more.

So if you really don't want these messages in your logs, you can add to
the [general] section of smb.conf

smb ports = 139

default 'smb ports = 445 139'

Craig




More information about the fedora-list mailing list