[Samba] win 7 client can't map drive: getpeername failed

Ed Strong eds3141 at gmail.com
Fri May 3 08:42:55 MDT 2013


Hi,

I'm re-posting this (with some more info) as I don't think the original got
through as I wasn't
signed up to the samba list.

this is my first foray in samba (and newsgroups) so go easy :)

I'm trying to map a network drive from a windows 7 pro client to a QNAP NAS:
  net use s: \\qnap\share

I've posted on several forums and got good advice but the problem remains.
Rather than repost all the detail, please see my original posts:

http://forum.qnap.com/viewtopic.php?f=185&t=74639
http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/11d35b0c-ac95-489f-b5d1-0486b9774603
http://www.edugeek.net/forums/windows-7/112309-map-network-drive-nas-but-get-error-64-58-a.html

I've managed to ssh onto the QNAP via putty and found this in the logs
(getpeername failed)

[/var/log] # pwd
/var/log
[/var/log] # tail -f log.smbd
[2013/05/01 09:36:17.135999,  0] lib/util_sock.c:474(read_fd_
with_timeout)
[2013/05/01 09:36:17.136096,  0]
lib/util_sock.c:1440(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by
peer.
[2013/05/01 09:36:17.137700,  1] smbd/server.c:299(remove_child_pid)
  Scheduled cleanup of brl and lock database after unclean shutdown
[2013/05/01 09:36:17.178522,  1] smbd/service.c:1073(make_connection_snum)
  172.24.120.139 (172.24.120.139) connect to service Staff initially as
user DOMAIN+admin (uid=10001423, gid=10000514) (pid

25771)
[2013/05/01 09:36:17.179093,  0] lib/util_sock.c:474(read_fd_with_timeout)
[2013/05/01 09:36:17.179173,  0]
lib/util_sock.c:1440(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  read_fd_with_timeout: client 0.0.0.0 read error = Connection reset by
peer.
[2013/05/01 09:36:17.179289,  1] smbd/service.c:1254(close_cnum)
  172.24.120.139 (172.24.120.139) closed connection to service Staff
[2013/05/01 09:36:37.142714,  1] smbd/server.c:272(cleanup_timeout_fn)
  Cleaning up brl and lock database after unclean shutdown


and some version info:

[/var/log] # ps -ef | grep smb
 4016 admin      3104 S   /usr/local/samba/sbin/winbindd -s
/etc/config/smb.conf
 4017 admin      3728 S   /usr/local/samba/sbin/winbindd -s
/etc/config/smb.conf
 4366 admin      1840 S   /usr/local/samba/sbin/winbindd -s
/etc/config/smb.conf
 4877 admin      3300 S   /usr/local/samba/sbin/winbindd -s
/etc/config/smb.conf
 4902 admin      3952 S   /usr/local/samba/sbin/winbindd -s
/etc/config/smb.conf
 4978 admin      4132 S   /usr/local/samba/sbin/smbd -l /var/log -D -s
/etc/config/smb.conf
 4979 admin      3356 S   /usr/local/samba/sbin/winbindd -s
/etc/config/smb.conf
 4980 admin      1224 S   /usr/local/samba/sbin/winbindd -s
/etc/config/smb.conf
 4995 admin      1016 S   /usr/local/samba/sbin/smbd -l /var/log -D -s
/etc/config/smb.conf
 5063 admin      2068 S   /usr/local/samba/sbin/winbindd -s
/etc/config/smb.conf
 9509 admin      1664 S   /usr/local/samba/sbin/nmbd -l /var/log -D -s
/etc/config/smb.conf
25540 admin       544 S   grep smb
[/var/log] # /usr/local/samba/sbin/smbd -V
Version 3.5.2


Also installed MS network monitor on two clients and did a capture whilst
running the command
   net use s:\ \\saturn\staff

I've attached screenshots that may be of help:

Worked shows the SMB frames on a PC where the net use command worked
Failed shows the SMB frames on a PC where the net use command did not work

It looks to me like the first 6 SMB frames are identical. Then things start
to change

On the working client we continue with frame 10113 which is a
  Dfsc: Get DFS Referral Request

but the failing client continues with TCP frames (see screenshot) 154 to 157
before it seems to start the negotiation again at frame 158

Not sure how to troubleshoot this further so any advice welcome.

Thanks
Ed

PS I initially tried to post this on google group linux.samba but was
rejected by the
moderation robot which said "Please submit your message to the mailing list
address"


More information about the samba mailing list