Hello I've got several Win95 & WinNT machines accessing Samba 1.9.17p2 on Linux. When I try to add a DOS machine, it does not see Samba and does not connect to it. I can connect it to a Windows machine and get files. I am not using DHCP and I'm using msclient 3.0. Is there something specifically I'm doing wrong? John
> Date: Wed, 04 Mar 1998 10:57:02 -0600 > From: John Brown <jsbrown@niia.net> > To: samba@samba.anu.edu.au > Subject: Problems with DOS Clients > Message-ID: <34FD87DD.D1239066@niia.net> > > Hello > > I've got several Win95 & WinNT machines accessing Samba 1.9.17p2 on > Linux. When I try to add a DOS machine, it does not see Samba and does > not connect to it. I can connect it to a Windows machine and get > files. I am not using DHCP and I'm using msclient 3.0. Is there > something specifically I'm doing wrong? > > John >I've done this a couple of times with relatively no problem (other than the slow speed of the MS software, and its size). You should check the net submask definition in PROTOCOL.INI. It needs to match your other systems, and its usual value is "255 255 255 0" (no periods!) When its working, of course, you should be able to see the Samba server after issuing a "net view" command. However, browsing hasn't also worked well with MS Client for me. If you make the proper entry in the LMHOSTS file, you can also try "net view \\samba-server", for the appropriate value of "samba-server". You might try sending me your PROTOCOL.INI and SYSTEM.INI files - I could take a quick look.
> I've got several Win95 & WinNT machines accessing Samba 1.9.17p2 on > Linux. When I try to add a DOS machine, it does not see Samba and does > not connect to it. I can connect it to a Windows machine and get > files. I am not using DHCP and I'm using msclient 3.0. Is there > something specifically I'm doing wrong? >Are you using the full network redirector on the DOS client? If not serch the digest archives. One person reported that he had to use the full network redirector to access samba shares. Hope this helps. j- ________________________________________________________________________ Gerald ( Jerry ) Carter Engineering Network Services Auburn University jerry@eng.auburn.edu http://www.eng.auburn.edu/users/cartegw "...a hundred billion castaways looking for a home." - Sting "Message in a Bottle" ( 1979 )
On Wed, 4 Mar 1998, John Brown wrote:> Hello > > I've got several Win95 & WinNT machines accessing Samba 1.9.17p2 on > Linux. When I try to add a DOS machine, it does not see Samba and does > not connect to it. I can connect it to a Windows machine and get > files. I am not using DHCP and I'm using msclient 3.0. Is there > something specifically I'm doing wrong?Hi, Have you installed mstcp on the DOG box? It is a pre-requisite for samba. --- Peter Blake ppb@hft.co.uk ppb@baloo.tcp.co.uk
> From: Mac <dmccann@nibsc.ac.uk> > To: cartegw@eng.auburn.edu > Cc: samba@samba.anu.edu.au > Subject: Re: Problems with DOS Clients > Message-ID: <199803061010.KAA22562@chalsig.nibsc.ac.uk> > > Hi all, > > > > >Are you using the full network redirector on the DOS client? If not > >serch the digest archives. One person reported that he had to use the > >full network redirector to access samba shares. > > > My testing (against samba 1.9.17p-something) showed a rather interestign > fact. > > I hacked smbd to log the password string as sent by the client, and > spotted > that the BASIC redirector in the DOS client always sent 24 character > passwords. (24 characters is the length of an encrypted password) > > > Basically, irrespective of what the server wants to do, the BASIC > redirector always uses password encryption. Test this by following the > instructions in 'ENCRYPTION.txt' and you'll be able to connect from the > BASIC Redirector to Samba. > > The FULL Redirector will do both plain-text and encrypted passwords, and > since Samba defaults to plain-text, the myth has grown up that the FULL > Redirector is required. > > > If anyone knows how to stop the BASIC Redirector always using encrypted > passwords, then I for one would be delighted. >Very interesting. I'll have to try this again. I've been using encrypted passwords, but haven't been able to use the BASIC redirector. The FULL redirector is huge; it's an advantage to be able to use the much smaller BASIC redirector. I'd also be interested in hearing about other DOS clients that would allow connections to Win95 systems and Unix/Samba; the MS Client is horribly slow, especially for file copies from the client to a server.
> Date: Sat, 7 Mar 1998 18:29:46 +0100 (MET) > From: "F. G. P." <fgp@fgp.atnet.at> > To: Multiple recipients of list <samba@samba.anu.edu.au> > Subject: Re: Problems with DOS clients > Message-ID: <Pine.LNX.3.95.980307181920.711B-100000@fgp.atnet.at> > > Hi > > I was very interrested when I read your message, because I have the same > problem. I have installed Windows for Workgroups 3.11, together with MS > TCP/IP 32. I need TCP/IP 32 because Samba can only hande SMB over TCP, > and > not TCP over NetBEUI (Standard in Win95, and the only posibility for WFW > 3.11 without MS TCP/IP 32). So I think you cannot access Samba Servers > with the DOS-Client from Microsoft. However, maybe there is something > like > TCP/IP 32 also for the MS Dos-Client. > The Only solution I found for SMB over TCP under Dos was > LANMANAGER-Client from IBM (Free, like the MS-Client). I didn't try it > yet, but I will do so in the next days. > If you have further questions or you find other solutions, please > send me a mail (fgpqfgp.atnet.at) > > Greetings, fgp >MS Client 3.0 (available on the WinNT Server CDROM, and by ftp from Microsoft) includes TCP/IP. When you install it, the setup program allows you to 'Add Protocol'; select TCP/IP. I also then routinely edit the PROTOCOL.INI and AUTOEXEC.BAT files to remove IPX protocol and its associated programs to save space...