Indra Satriani

I'm not a geek!

[Samba] getpeername failed. Error was Transport endpoint is not connected

with 2 comments

nss_wins[31684]:   getpeername failed. Error was Transport endpoint is not connected

If you have something like that in your log, that is because the Windows client attempting to connect to samba on ports 445 and 139.

the XP Pro PC Client attempts to initially communicate with the
server over both ports 445 and 139 and that whichever port responds first
is used for further communication.

http://groups.google.com/group/linux.samba/msg/370a5eaded746ab2?pli=1

The workaround is either you disabled port 445 via iptables like the solution in here or simply by adding this line on your [global] stanza inside smb.conf

smb ports = 139

Edit:
Adding “smb ports = 139” may decrease your samba share performance. If you’re ok with that error above filling up your log, then its not necessary to add smb ports in your smb.conf. Your choice 🙂

Advertisements

Written by Indra Satriani

September 30, 2010 at 10:33 am

Posted in linux

Tagged with , ,

2 Responses

Subscribe to comments with RSS.

  1. good article, problem solved
    Thank’s a lot

    sonny

    November 1, 2011 at 2:23 pm

  2. Thank you a lot for your solution. You can leave both ports but put 139 first for both windows and samba to be happy :).
    smb ports = 139 445

    Eugen Mitu

    December 10, 2011 at 2:34 pm


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: