DOS-based Microsoft Network Server

The "Microsoft Network Client 3.0" installs the Client-module, allowing the DOS-system to access shared resource on the Network.

To allow other systems on the Microsoft network to access the disk and/or printer on the DOS-system, you need to download from the Microsoft FTP-server: ftp.microsoft.com in the directory /Softlib/Mslfiles the:
"WG1049.EXE".
It is a self-extracting file, just run it:


and copy all the NET*.* files to your directory with the installed files of the
"Microsoft Network Client 3.0" (should be usually the default location C:\net)
(when copying, you will get some warning about replacing existing files, please allow the replacing, since some files of the network client need to be updated)

The NET-command has now a few more option, as shown by asking for
some help via: "NET ?"


You need first to make a small modification to the SYSTEM.INI-file:

In the section [network], you need to allow File-Sharing and/or Printer-Sharing by changing the option from "no" to "yes"

Please, view the Help-information about Sharing by typing: "NET ? SHARE"

	To be able to share, it is first required to start the Server-function: NET START SERVER (should be added to AUTOEXEC.BAT) Then, you can share (for example: C:\): NET SHARE <sharename>=<local path> (example: NET SHARE U66=C:\) Note: no blanks are allowed between <sharename>=<local path> ) just running NET SHARE displays the list of shared resources on the DOS-system
	The disk of the DOS-system (called "486" in my example) is then accessible on Windows systems and is displayed in the "Network Neighborhood".

The installation of the DOS-server modules takes an additional 20 KByte
of DOS-memory.
If you require the DOS-system to be a SERVER, but also need a lot of free
DOS-memory to run your applications and the Microsoft network software
takes too much memory, you could use Artisoft Lantastic as an alternative solution (requires much less memory for the DOS-network drivers).