This page was written by Christopher Spry and is a copy of the useful original page by Jacco de Leeuw at http://carol.wins.uva.nl/~leeuw/. I have copied it here for local use only. Please email him leeuw@wins.uva.nl, for further details.
This page is still under development. I welcome any additions or suggestions! Mail me!
[network] ; <= 16 (8) numdgrambuf=";" <="16" numservices=";" <="4096" ! numbigbuf=";">= 4096; <= 32768 (4096) sizbigbuf="numworkbuf=" ;>= 1024; <= 16384 (1024) sizworkbuf="1498"
If you would like to see a description of the parameters, refer to LAN Manager 2.xx documentation - the same parameters are used there.
The "Microsoft LAN Manager (version 2.0 Enhanced)" Windows 3.x network client
graphical user interface works with MSClient and SAMBA 1.9.16p11. This client is
distributed with Windows 3.x. For those interested, the following are the relevant
configuration file entries and drivi>
system.ini ---------- [boot] network.drv=lanman.drv [boot.description] network.drv=Microsoft LAN Manager (version 2.0 Enhanced) [386Enh] network=*vnetbios,*dosnet windows\lanman.hlp windows\winpopup.exe windows\winpopup.hlp windows\system\lanman.drv windows\system\netapi.dll windows\system\pmspl.dll
It may be a good idea to incorporate the [386Enh] settings from MSClient's own "system.ini" into your Windows one (normally C:\WINDOWS\SYSTEM.INI).
(more to come)
You can download the Microsoft LAN Manager Client for DOS (referred to as LanMan in the following) for free by clicking here. You need 4 files: DSK3-1.EXE, DSK3-2.EXE, DSK3-3.EXE, and DSK3-4.EXE. While you're in the downloading mood, there are two text files that you might find somewhat useful. The first is the README.NOW file found at ftp.microsoft.com/busys/clients, and the second is the readme.txt file that gets created in the LANMAN.DOS directory once you're done installing Lanman to the hard disk of your DOS machine. See below for further installation instructions.
There is one little problem in the Samba source code. LanMan cannot "see" the names of the available Samba servers on your network (but once you know the name of the Samba server, it will connect fine). There's now a fix available: you (or your friendly system administrator :-) probably will want to install the 'LM Announce' patch on the Samba server.
You need "NetBIOS over TCP/IP" (often called TCPBEUI or RFC/NetBIOS) only if you need to access a server that is located across an IP based router. Or if the server runs Samba, because Samba only supports "NetBIOS over TCP/IP".
Most people will choose MS Client over LanMan because Microsoft tells them so: "Microsoft has optimized this client to work with Windows NT version 3.5 servers, and will be the focus of future development efforts for MS-DOS - based clients for Windows NT". Yeah right. Do you honestly believe Microsoft is going to update their DOS software?!? They have told numerous times that "DOS is dead". Check the date of MS Client files: June 1995... The real reason I believe is that Microsoft wants to move you from the LAN Manager type of browsing protocols which OS/2 machines use. AFAIK, the MS LAN Manager Server runs under OS/2 so that too is something they don't like.
MS Client needs a Browse Master on the network. This means that in order to 'browse' the network (see which computers are connected to it) at least one computer running Samba, Windows for Workgroups, Windows 95 or Windows NT must be on the network and belong to the same workgroup as the computer running MS Client. LanMan on the other hand detects machines on the network by the broadcast messages they generate (you may need to switch on the 'LM Announce' option on these then). Conclusion: if you have Windows machines on your network, I recommend using MS Client, and if you have OS/2 machines on your network I recommend the LanMan client. Samba servers should work with either one, although for LanMan clients you need to install the 'LM Announce' patch (see below).
One thing Microsoft forgot(?) to mention is that MS Client does not support sending network messages ("WinPopup") using the NET SEND command. LanMan does. Network messages are very useful for a home network where the kids are using a DOS machine to run games located on a machine elsewhere, and you want to send messages ("Dinner's ready!")...
If you install the 'Basic' version (valid for both clients), e.g. to reduce memory usage, you can only access Samba if it is running in 'share level' mode. Not in 'user level' mode. This limits the security a lot. See the Samba documentation.
MS Client does not provide drivers for a Windows 3.x network client graphical user interface. You will therefore be unable to browse and (dis)connect resources (disks, printers) from within File and Print Manager, as you can with Windows for Workgroups. MS Client does provide WinSock etc. DLLs, however.
You can download it for free by clicking here.
Extract with DSK3-1.EXE -D and DSK3-2.EXE -D to 2 floppies. Speedup installation by extracting to a temp directory instead of floppies, install with SETUP.EXE and then delete the installation files in the temp directory.
Installation of the MS Client is very similar to the installation of the LAN Manager Client (see below) so look there for some tips. I only have instructions on the LanMan installation so far, because 1) I already had written them for the OS/2 version of LanMan and 2) Andrew DePaula had also written something for the DOS version. If you have instructions for installing the MS Client, please forward them to me.
François Visagie wrote the rest of this section:
MS Client works very well from the command line. It is not documented, but I did manage to find out more about its tunable parameters. These did not seem to have too much effect on performance, however. For what it's worth, here is the information.
These parameters appear in MSClient's "system.ini" in the section indicated. Each parameter is preceded by a comment indicating minimum and maximum values, where available. Default values are given in parentheses. To set a parameter to its default value, you could either specify the value directly, omit the parameter, or leave it empty as in the examples. When the installation suggestion of tuning for increased performance is accepted, "sizworkbuf" is set to 1498 as in the example, otherwise it's left at the default by omission:
[network] ; <= 16 (8) numdgrambuf=";" <="16" numservices=";" <="4096" ! numbigbuf=";">= 4096; <= 32768 (4096) sizbigbuf="numworkbuf=" ;>= 1024; <= 16384 (1024) sizworkbuf="1498"
If you would like to see a description of the parameters, refer to LAN Manager 2.xx documentation - the same parameters are used there.
The "Microsoft LAN Manager (version 2.0 Enhanced)" Windows 3.x network client g-serif">You can install from floppies or from hard disk. If you choose to install from floppies, get 4 blank disks and extract each of the 4 archive files to a disk. Installing from hard disk is much faster. Disk 4 contains many small files which makes the disk drive grind like crazy. Create a temporary directory on the hard disk and extract each of the 4 archive files to that directory. The archive files contain a couple of duplicate files so when you get a message that the file already exists, just say yes. Or no. Doesn't matter.
You unpack the archive files by executing them directly: DSK3-1.EXE -D etc. Or use Info-Zip's UNZIP or PKWare's PKUNZIP: UNZIP DSK3-1.EXE etc. Don't forget to specify the -D parameter if you execute them directly because otherwise the files will be extracted without their paths.
Goto A: or the temporary directory on the harddisk and execute SETUP.EXE. Follow the instructions on the screen. I won't explain here each and every screen you get. It is reasonably straightforward. You can use the mouse but you can also get around with the keyboard. Press Alt to get the menu. Navigate using the cursor keys and by pressing Tab, Return and Esc. You select choices with the spacebar.
Follow the instructions until it asks you to choose between the Basic or Enhanced Client installation. See the README.NOW mentioned above, under section III A (Planning for Lan Manager Instalation and Configuration on MS-DOS (R) Computers). If you want to run Samba in user level or server level security (which is normally the case; see also security_level in the Samba docs directory), you need to install the Enhanced Client. For share level security (= less secure but good enough for home use), you can do with the Basic Client (costs less conventional memory).
In the screen "Network Adapter Drivers" you get a list of drivers included with LanMan. Be warned that the list is very limited and that the drivers date from 1995, so they are quite old. You might want/need to use a (newer) driver from the disk supplied with your network card. In that case, go to "Other Driver" and press Enter. Specify the directory in which you can find the MSLANMAN.DOS directory. But if you have another driver located, say, in the directory MSLANMAN.DOS which can be found in C:\TEMP, select "Other Driver" and specify the path C:\TEMP.
The default domain/workgroup name used by Samba, WfWg and Win95 is WORKGROUP. For the English version of Warp 4 and Warp Connect is IBMPEERS. Use the name STANDALONE if you don't connect to big time servers such as NT, LAN Server, Warp Server. LanMan searches for these servers and it will timeout faster if you use STANDALONE.
NetBEUI ("NetBIOS over NetBEUI") is one of the supported protocols. The other one, "NetBIOS over TCP/IP" (TCPBEUI), is required is you want to connect to Samba servers. You can select it by checkboxing TCP/IP. If you enable both options, you get both "NetBIOS over NetBEUI" and "NetBIOS over TCP/IP". I have no idea what NetBIOS 3.0 is and what it is for. I don't change the other default settings.
At this point you'll need to provide the instalation program with all the IP information it needs. If there is a DHCP server on your network, the client can retrieve all its configuration information from this server. In this case, you can forget about all the entries in this dialog box except to make sure that automatic DHCP configuration is enabled and click OK at the bottom of the dialog box. If DHCP is not supported on your network, here's what to put in the first three fields of the dialog box:
IP Address: enter the IP address of your DOS machine here
Subnet Mask: enter your subnet mask here (e.g. 255.255.255.0)
Default gateway (router): if you have one, its IP address goes here
If you have a WINS server on your network (this can be a Samba server, if it is specifically configured as such!), enter the appropriate IP address(es) in the last two fields of the dialog box and click OK at the bottom. If you want to use a DNS server, then leave the WINS server fields blank and click Advanced at the bottom of the dialog box. This brings up a dialog box where you can configure Domain Name Resolution, and Socket Settings. Enter your username and hostname at the top. Enable use DNR for hostname resolution, and fill in the remaining fields as follows:
Primary Nameserver IP Address: Enter your primary DNS server IP address here
Secondary Nameserver IP Address: Enter your secondary DNS server IP address here
Domain Name Suffix: enter your domain name here (e.g. "wwc.edu")
Enable windows sockets at the bottom so that the DNR service gets loaded in the AUTOEXEC.BAT file (??? JdL) and click OK. Click OK again to exit the TCP/IP settings dialog box. Enter your computer name, username, and domain again in the workstation settings dialog box and click ok. Follow the rest of the instructions until installation is complete. Exit the installation program. Do not reboot yet.
You have to configure some settings (interrupt, DMA, I/O address etc.) for your network card in C:\LANMAN\PROTOCOL.INI. There should be an entry ("section") for that network card in the PROTOCOL.INI.
Now edit the section for your network card in C:\LANMAN\PROTOCOL.INI. If you have an NE2000 clone for example, you'll need to specifify the Interrupt (IRQ) and the I/O base address. Of course, they have to agree with the settings of your network card. In many cases, you set the IRQ and I/O base with jumpers on the card. Newer cards do not have jumpers on them, you have to use a DOS configuration program to change settings.
If you have an EtherLink III however, generally you don't have to edit the [ELNK3_NIF] section since this card is 'self-configuring'. It finds the IRQ and I/O base on its own.
The example PROTOCOL.INI on your network card's driver disk usually contains a description of all the "keywords" you can use for the network card's section. You can change the settings if it is needed. Since every network card is different, I can't really tell what to do, but in many cases the default settings should work.
...and watch any errors you get.
If you got this far, don't you sit there waiting! Try it out! Start with a simple case. For instance, if you installed the TCP/IP stack included with LanMan, try using its PING.EXE on the command prompt. Ping your gateway machine or your Domain Name Server (DNS) for example, using their numerical IP addresses. If that works, it means the software and the network card are working. Next, try to ping a machine using is alphanumerical name. If that works, it means that LanMan can find the DNS and it is working OK. Also try to access resources of a machine near you. See if NET VIEW works. Etc. etc.
Back to top
I won't discuss using LAN Manager in depth, but here are some tips and loose comments.
NET VIEW NET VIEW \\dadspc NET USE h: \\dadspc\drivec NET USE h: /delete NET USE lpt4 \\momspc\inkjetprinter NET SEND jacco Dinner's ready! NET HELP NET HELP xxxxx (where xxxx is a LAN Manager command such as USE) NET HELPMSG xxxxx (where xxxx is an error message number)
Andrew DePaula says that the password for the shared directory you're trying to access on the Samba server must consist of all upper case characters. If after typing the above net use command you get a DOS error 86, that's probably what's wrong. It could be that this is not needed if you use libdes (encrypted password support) with Samba. See also ENCRYPTION.txt . Another thing to try is Samba's password level configuration option.
You can issue many commands from the command line but if you start NET without any parameters you get a text window where you can perform most of these actions through a menu.
LanMan Client | LFNs | connecting to: | | ----------------+-------------------+-- Warp 4/Connect | no | ----------------+-------------------+-- Samba | opt. mangled 2) | ----------------+-------------------+-- Windows NT | mangled 2) | ----------------+---------------------- Windows for Wg | no | ----------------+-------------------+-- Windows 95 | mangled 2) |
1) Only if the shared disk which you connect to is a filesystem which supports LFNs, such as HPFS or Ext2FS. Not on FAT.
2) These operating systems can (optionally) "mangle" a LFN into a valid 8.3 filename so that DOS clients can access these files. Example: "My Graduation Thesis.DOC" is turned into "MY_GR~01.DOC". Other clients who do support LFNs can still access the file by its full name.
A DNS translates an Internet address which a human can understand (such as ftp.cdrom.com) into a numerical Internet address a computer can understand (such as 165.113.58.253).
There is a HOSTS file in C:\LANMAN\ETC\HOSTS. A HOSTS file is a simple set of lines. Each line contains a numerical IP address for a host and a alphanumerical hostname under which this host is known to your PC. There is also a file called LMHOSTS in the same directory. This file contains the mappings of IP addresses to computer (NetBIOS) names. If your Samba server is across a router from the DOS machine you are configuring, you must add a line similar to the following to the LMHOSTS file in the \LANMAN.DOS\ETC directory:
www.xxx.yyy.zzz SRV_NAME # SRV_NAME is my Samba server
(where www.xxx.yyy.zzz is the numerical IP address of the Samba server)
You need to add an entry for other machines to the HOSTS file if you want to bypass the DNS. For instance, if you don't have a DNS because you're on a simple network at home. The same goes up for the LMHOSTS if there is no big time server on the network.
Please note: the last line of the HOSTS and LMHOSTS files need to end with a Carriage Return/Line Feed, otherwise that line will not be recognized. And that can lead to strange errors which are difficult to trace.
I'd like to thank François Visagie for 'borrowing' his test of DOS clients (and all his other helpful posts!) on the Samba mailing list. Andrew DePaula posted instructions on how to install a LanMan client to the Samba mailinglist. He had some stuff I didn't have and I had some stuff he didn't have. This webpage now contains the stuff we both had :-) Thanks Andrew!
I'm a Computer Science student at the University of Amsterdam. If you want to contact me:
Jacco de Leeuw J.C. van Wessemstraat 54 1501 VM Zaandam The Netherlands Internet: leeuw@wins.uva.nl WWW homepage:http://carol.wins.uva.nl/~leeuw/ Fidonet:
If you email me and you get an "Unknown User" email message back, it could be that my account has been cancelled because I graduaded (especially if you are reading this months after the creation date of this document). A couple of times I received email from people who hadn't entered their return email address correctly, so I couldn't email them back with help. Please check your return address (especially if you're using a PC email client) or better yet, include it in the body of your email message.
Return to the 'home page
Return to the 'computer index page'
© cspry@sghms.ac.uk. Department of Biochemistry & Immunology, St. George's Hospital Medical School, London SW17 0RE, UK. Phone +44 20-8725 5819; fax +44 20-8725 5821. The page was updated on 10 December 2001 11:27:05