Richard Andrews enscribed thusly:
> >I want to mount a winnt system in my office to my linux box at home. When
> >ever I try it dies with a mount error (no number smbmount just says mount
> >error). I can mount my win98 machine. Is there any registry settings I need
> >to change in order to mount the directory?

>   A friend told me that M$ have changed the SMB protocol standards with some 
> NT service packs and has refused to release details.

>   Does anyone know if this is true? If so for what bugfix (um ... I mean
> service pack) versions?

        No this is not quite true...  At least not the part about refusing
to release the details.  We've got all of that.

        Microsoft did make some changes in SP3 that made things more
complicated, but it was actually in reaction to some security holes that
they were getting beat up about.  This little thing about people putting
up web pages which could "trick" your Windows NT system into revealing
your password IN CLEAR TEXT was just a little too much even for them,
so they fixed it.  NT4.0 SP3 and later defaults to requiring a more
secure ( I didn't say totally secure :-) ) protocol when authenticating
users.  The latest samba code has all of that incorporated.

        From the description of the error, this sounds like the old smbmount
program from smbfs and a 2.0.x kernel.  I know for a fact that the smbmount
program from samba used with a 2.1.x kernel works just fine against NT 4.0
with SP3 and the various SP4 betas.  The smbmount program with samba will
NOT work with kernels prior to 2.1.70.  Conversely, the smbmount program from
smbfs will NOT work with kernels after 2.1.70.  I would guess that the
smbmount program from smbfs has not been update to handle encrypted password
challenges.  At this point, it probably never will be.

        Notes regarding the two versions of smbmount:

        The command syntax is different between the two.  If you upgrade
to the newer kernels and newer smbmount, you will have to change.

        As it stands, the smbmount program from samba will NOT work with
autofs, because of the syntax changes.  If you are using autofs, I have
a frontend script which replaces smbmount and can call either smbmount.smbfs
or smbmount.samba with appropriate translations to make autofs work.
That's available at:

        http://www.wittsend.com/mhw/smbmount.html

        The smbmount, smbmnt, and smbumount programs in the released samba
package, 1.9.18p10, will NOT compile under RedHat 5.x.  I've commited changes
into the Samba CVS tree to fix this and those changes are in the 2.0 alpha
release snapshots.  To get those programs to compile for any glibc2 system
you will either have to checkout the sources from the CVS tree or get one
of the snapshot tarballs.  The 2.0 Samba is now using autoconf instead
of the old way of configuring, so the sources can't just be copied back
into the older tarball (it would be close, but not quite there).

        Mike
-- 
 Michael H. Warfield    |  (770) 985-6132   |  [EMAIL PROTECTED]
  (The Mad Wizard)      |  (770) 925-8248   |  http://www.wittsend.com/mhw/
  NIC whois:  MHW9      |  An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471    |  possible worlds.  A pessimist is sure of it!

Reply via email to