On Thursday 09 February 2012 14:00:24 you wrote:
> On 9 February 2012 12:09, JR van Rensburg <[log in to unmask]> wrote:
> > On Thu, 2012-02-09 at 12:02 +0000, Anne Wilson wrote:
> >> Just realised - my nfs mounts are fine, but this is my first attempt
> >> to mount with samba - so that's where I need to check next.
> > 
> > Samba has its own username/password list, unless you set it all up to
> > use ldap logins.
> 
> Yes.  I've set up samba several times before, but infrequently.  It's
> ~5 years since I did it last, so I've probably forgotten something
> vital.  I definitely have authentication problems.  I've checked that
> my unix users are properly converted to samba users, and that their
> passwords are known by samba.
> 
> testparm
> Load smb config files from /etc/samba/smb.conf
> rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
> Processing section "[homes]"
> Processing section "[Data 1]"
> Processing section "[printers]"
> Loaded services file OK.
> Server role: ROLE_STANDALONE
> Press enter to see a dump of your service definitions
> 
> [global]
>         workgroup = XXXX.LAN
>         netbios aliases = borg
>         server string = Samba Server Version %v
>         interfaces = lo, eth0, 192.168.0./24, 127.0.0./8
>         smb passwd file = /etc/samba/smbpasswd
>         log file = /var/log/samba/log.%m
>         max log size = 50
>         path = /Data1
>         force group = users
>         cups options = raw
> 
> [homes]
>         comment = Home Directories
>         read only = No
> 
> [Data 1]
>         comment = main Data repository
>         read only = No
> 
> [printers]
>         comment = All Printers
>         path = /var/spool/samba
>         printable = Yes
>         browseable = No
> 
> The log file shows
> 
> [2012/02/09 13:53:40.839234,  0] lib/util_sock.c:474(read_fd_with_timeout)
> [2012/02/09 13:53:40.839355,  0]
> lib/util_sock.c:1441(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.
> 
> I don't understand those entries - can you please explain?  And do you
> see other problems?
> 
For the sake of anyone else meeting the same problem here's what happened.

Further exploration of backup files suggested that Samba wasn't even configured 
on the old box.  It looks as though it may not be required.  Previously I had 
used "Map network drive" but I couldn't get past authentication that way, on 
this occasion.  Then someone had written on a forum that if the drives had 
been marked as shareable it was possible to simply go to the start menu search 
box and type in the IP address.  Sure enough, that worked, and from there I 
could map the drive for one-click access in future!

Thanks for trying to help.

Anne