Path: wins.uva.nl!sun4nl!EU.net!main.Germany.EU.net!main.de.uu.net!Dortmund.Germany.EU.net!Dortmund.de.uu.net!Uni-Dortmund.DE!news From: none@no.junkmail.com (ET/LS MAL) Newsgroups: comp.protocols.smb Subject: Re: DOS client (alone) Date: Wed, 17 Sep 1997 06:01:31 GMT Organization: Uni Dortmund Lines: 72 Message-ID: <341f7195.793614@news> References: <341E6DFD.B9BB0C7D@iele-ab.uclm.es> NNTP-Posting-Host: hiwi3.e-technik.uni-dortmund.de X-Newsreader: Forte Free Agent 1.11/32.235 Xref: wins.uva.nl comp.protocols.smb:1185 Francisco Garcia Sevilla wrote: >Is it possible to conect a PC running DOS 6.2 with a Samba server? >Which software I need? Below is an answer that was posted here recently. BTW - why does your message appear 7 times? Now here's the text: Get the DOS Workgroup Client from ftp.microsoft.com, in directory /bussys/clients/MSCLIENT. Get both files. They're self-extractors. Extract all the files, run SETUP. Now your DOS machine is a client on your Windows P-t-P network. Go back to ftp.microsoft.com, and get WG1049.EXE, from /softlib/mslfiles. It's another self-extractor. Run it in your /NET directory, and let it overwrite whatever it wants to. Now you HAVE TO enable the sharing of their Hard drive (and LPT's if you wish). If you take a look in SYSTEM.INI you will see the two lines near the top: [network] directhost=yes sizworkbuf=1498 filesharing=yes <<-------- printsharing=yes <<-------- autologon=yes These two lines are NO as the default... just change them to YES. Note that IF you make any future changes via SETUP (for the dos client/server) it WILL change things back to NO (trust me on this one)... Also in your Autoexec.bat file you have to tell the system what to share and what it's name is. An example is: C:\NET\net initialize C:\NET\nwlink C:\NET\net start net share Printer=Lpt1 /full /yes net share C-Drive=C:\ /full /yes In other words, you 'assign' C-Drive as the log in name for other system to map to (ie: map E: as \Sys2\C-Drive)... And as you can see, you 'NEED' to assign a name for your LPT1 as wall. In the example above, I've assigned 'printer' for LPT1 and 'c-drive' for the Hard drive (this is what is needed for mapping and port capturing - identical as for Windows Networking). Once you've assigned the above, AND your SYSTEM.INI file has the correct Dos machine Name and Workgroup, then you 'should' be able to see the Dos machines! Here is an example of my System.Ini for the above: computername=RFA8 lanroot=C:\NET username=PLOTTER workgroup=WORKGROUP reconnect=yes dospophotkey=N lmlogon=0 logondomain=WORKGROUP We have 12 machines (RFA1 to RFA12). This machine is used for a Laser Server (so instead of a User 'name' like BRUCE, I call it PLOTTER). And we use the default Workgroup name.