Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Sep 2011 23:03:27 -0400
From:      Michael Powell <nightrecon@hotmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: Samba question
Message-ID:  <j4h80m$o0k$1@dough.gmane.org>
References:  <0EE458C34045A44DBC2CA2DC5CEB42B5232131B947@mercury.universe.galaxy.lcl> <20110911040939.78360716.freebsd@edvax.de>

next in thread | previous in thread | raw e-mail | index | archive | help
Polytropon wrote:

> On Sat, 10 Sep 2011 11:53:48 +0100, Graeme Dargie wrote:
>> I am trying to mount a samba share that is on a FreeBSD 8.2
>> server to another FreeBSD 8.2 server,
>> 
>> Mount_smbfs -I <IP> //user@host/share /mountpoint
>> 
>> It then asks for a password, I enter the users password
>> and then get mount_smbfs: unable to open connection:
>> syserr = Authentication error
>> 
>> Dmesg is showing smb_co_lock: recursive lock for object 1
>> 
>> I have samba integrated with Active Directory, so I then thought
>> ah maybe adding the user to AD would help, so I have done so
>> using the same password etc still no joy, I have make sure the
>> user has access rights on the samba share, restarted samba and
>> the same error persists, any ideas ?
> 
> Sorry, my indivudal knowledge on "Windows" related things
> is very limited, but maybe you need to add some information
> into /etc/nsmb.conf?
> 
> Maybe like this:
> 
> [default]
> workgroup=YOUR_WORKGROUP_NAME
> 
> [SERVERNAME]
> addr=192.168.2.2
> 
> [SERVERNAME:USERNAME]
> password=TOPSECRET
> 
> where SERVERNAME and USERNAME correspond to the server's name
> and the username you use to access the share (with the proper
> password).
> 
> See "man nsmb.conf" for details.
> 
> Parts of those information should then be reflected in /etc/fstab,
> maybe like this:
> 
> //user@SERVERNAME/share  /smb/share  smbfs  rw,noauto  0  0
> 
> This should allow you to use
> 
> # mount /smb/share
> 
> a bit easier (and automatically, if desired).
> 

Although it has been ages since I played with this, one thing I do recall: 
It matters that where indicated above the characters _must_ be in upper 
case. When I used to use such a setup I found it wouldn't work without it. 
Never knew exactly quite why. 

-Mike





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?j4h80m$o0k$1>