Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Mar 2006 08:45:11 -0500
From:      Scott Robbins <scottro@nyc.rr.com>
To:        freebsd-current@freebsd.org
Subject:   Re: smbfs regression in 6.1-PRE and 7-current
Message-ID:  <20060316134511.GC50512@mail.scottro.net>
In-Reply-To: <20060316122714.GA49023@stud.fit.vutbr.cz>
References:  <20060316081950.GA9304@stud.fit.vutbr.cz> <20060316111138.GC60688@mail.scottro.net> <20060316122714.GA49023@stud.fit.vutbr.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, Mar 16, 2006 at 01:27:14PM +0100, Divacky Roman wrote:
> On Thu, Mar 16, 2006 at 06:11:38AM -0500, Scott Robbins wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > On Thu, Mar 16, 2006 at 09:19:51AM +0100, Divacky Roman wrote:
> > > Hi,
> > > 
> > > I have a server running samba 3.x which offers some smb shares. From another
> > > machine which is running 6.1-PRE I am not able to mount that share, but it used
> > > to work when it was 6.0R, from yet another machine which is still 6.0R it can
> > > be mounted without problems.
> > > 
> > 
> > Could this have to do with the NETSMBCRYPTO issue of a couple of 
> > weeks ago?  
> > 
> > A few of us had a similar issue.  At the time, it was fixed by adding 
> > NETSMBCRYPTO to the kernel.  
> > 
> > Looking at UPDATING I see there's a note from 20060305 that the option
> > has been retired as it's being included in smbfs.ko now, however, in the
> > past, I had never loaded that module or included NETSMB in my kernel,
> > installing samba from ports had Just Worked(TM).  
> 
> I never had this in my kernel config. and now it doesn exist at all so I think
> it must be something else



I'm sorry, perhaps I wasn't clear.  I never did anything with the kernel
or loading modules either, installing samba from ports enabled me to
mount NTFS and other MS shares without problem.  

Then, a couple of weeks ago, the problem began.  There was a thread
about it and the solution was add to NETSMBCRYPTO to the kernel.  

The note in UPDATING came after that.  It was no longer, as near as I
see from UPDATING, necessary to add NETSMBCRYPTO but one would need
NETSMB or else kldload smbfs.   In my case, I haven't updated the
servers that needed this in a couple of weeks, so I haven't tested if it
can just be fixed by kldloading smbfs. 

Sorry for the lack of clarity in my earlier post.


- -- 

Scott Robbins

PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

Xander: Dinner is served. And my very own recipe.
Willow: Ooh, you pushed the button on the microwave that says
'popcorn'?
Xander: Actually, I pushed 'defrost', but Joyce was there in the
clinch.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (FreeBSD)

iD8DBQFEGWvn+lTVdes0Z9YRAgnQAKDCAzeJaF7HC2F4NKRHt3/U7m4rnACgncMK
UerBdPTBbMnTeM1DmDeHzio=
=RJb8
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060316134511.GC50512>