samba - Jun 1998 - MS DOS client : solution

Hello,
	
	I finally found a solution to allow basic MS DOS client 3.0 redirector to work
with Samba.
I'm sure you'll find it ugly, but it works. Under CORE protocol, the
$"#&^ MS client sends unencrypted
passwords to the samba server (maybe there is no support of encryption in CORE,
I don't know).
	So as my clients are either W95, WfW, NT or DOS machines, I simply remove the
support
of LANMAN1 and LANMAN2 protocols in the negotiation between Samba and the
client. All machines
which are not DOS will agree on a higher protocol anyway ...
	The only trade-off (?) is that at the first time, the DOS clients have to
connect with the
syntax : net use \\machine\share%username [password], no big deal. But I have
more than 590 k
of free memory under DOS ...

	Philippe

>Date: Sat, 6 Jun 1998 00:01:21 +-200
>From: Philippe GUILLEMETTE <philippe.guillemette@wavecom.fr>
>To: "'Samba'" <samba@anu.edu.au>
>Subject: MS DOS client : solution
>Message-ID: <01BD90DE.3D84E160@wmp_pc01.wavecom.fr>
>
> Hello,
>	
>I finally found a solution to allow basic MS DOS client 3.0 redirector to
work with Samba.
>I'm sure you'll find it ugly, but it works. Under CORE protocol, the
$"#&^ MS client sends unencrypted
>passwords to the samba server (maybe there is no support of encryption in
CORE, I don't know).
>So as my clients are either W95, WfW, NT or DOS machines, I simply remove
the support
>of LANMAN1 and LANMAN2 protocols in the negotiation between Samba and the
client. All machines
>which are not DOS will agree on a higher protocol anyway ...
>The only trade-off (?) is that at the first time, the DOS clients have to
connect with the
>syntax : net use \\machine\share%username [password], no big deal. But I
have more than 590 k
>of free memory under DOS ...
>
>Philippe
I just had the same problem, and I set up the basic-redirector of
MS-TCPIP-Client with encrypted passwords, saving lots of memory as described.
Maybe this is pointless, but I just would like to understand it better, what
advantages does the solution described above have vs. using encrypted passwords.

Christoph Mueller
mueller-dlg@t-online.de