Connection from a DOS-system to an NT4 Server
A DOS-based system can connect to a Windows95
or WindowsNT4 Workstation or a Windows NT server using the "Microsoft
Network Client 3.0".
To setup a connection, download from the Microsoft FTP-server:
ftp.microsoft.com in the directory /bussys/clients/MSCLIENT.the files:
( these files can also be found on the
NT4-server CD-ROM under \CLIENTS\MSCLIENT)
The files are Self-extracting, copy all extracted files to 2
floppies, but for an installation on a system WITHOUT Windows
3.1, only floppy #1 is required,
you will need the floppy#2 for installation of TCP/IP.
These SETUP-disks have not been updated by Microsoft with drivers
new Network-boards, you have yourself to Update Network Client 3.0 with
Sample installation (using a 3COM EtherLink III 3C509 at IRQ=10
and port=320) using NetBEUI protocol (I
have also documented the differences
on installing the DOS-client
using TCP/IP protocol and for creating
Bootable Floppy disk):
Start the setup from floppy (in some cases it "hangs",
try then from C:\ to run A:SETUP)
Press "ENTER" to continue.
By default, the setup-procedure will copy the Network-files into
Press ENTER to continue
It should only take a few seconds for this test (if it takes
longer, try to run setup from C:\)
If the system cannot detect itself the type of the network-board,
you will be prompted to define the Network-board:
(if your network-board is NOT in this list,
then exit now [F3] and first Update Network Client 3.0 with the new Network-board
Driver, then start the SETUP again).
Depending, on whether the CONFIG.SYS contains the
"FILES=" statement, you may get:
Press ENTER to accept the change.
You are then required to define the computer-name:
The summary screen is displayed:
Check under "Change Names":
and correct it to your "Workgroup-Name" or
This Network-Client can be used for
"Workgroup"-networking to Windows95,
WindowsNT4 Workstation and WindowsNT4 Workgroup-Server:
When connecting to a Windows NT4 Domain-Server, you need to
define the Domain-name:
Note: This option is not available, if the Network-Client is
configured for the Basic-Redirector (see below for details).
Then, check the "Setup-Options":
For "Workgroup"-networking, change to use the
"Basic Redirector" (to save memory):
When connecting to a Windows NT Domain-Server, you MUST
change the "Logon Validation" to "Logon to
Domain", which forces to use the "Full
Check under "Change Network Configuration":
Check under "Change Settings" for the proper
Port-address and IRQ:
Select "Change Network Configuration":
If required, use the option "Add Protocol" to add the
When using TCP/IP, please follow the TCP/IP configuration
Both protocols are now loaded:
To save (valuable DOS)memory, delete any unnecessary protocol:
Press the TAB-key to switch the windows and select the protocol
Press the TAB-key again to switch back to the
"Options"-windows and select the line
"Remove" to delete this protocol:
A last check, that the network is defined properly:
then let the system continue with the installation / copying of
Once all files are copied, you are asked to reboot:
Like usual, I suggest NOT to reboot, but to press F3 to first
check the installation by viewing AUTOEXEC.BAT and CONFIG.SYS:
This is fine, so reboot:
The network is activated, you are login by entering your Username
the use of the computer-name as login-name.
Use then the NET USE-command to map a
network drive to a resource on a Windows95
or Windows NT4 workstation or server, for which this system has
valid access permissions:
NET USE <drive>:
Example: mapping drive F: to the system "NTSERVER"
and the shared item "DATA":
This Microsoft network driver uses a lot of CPU memory:
80 Kbytes on using the "Basic Redirector"
170 Kbytes on using the "Full Redirector"
Some Memory optimization is required in AUTOEXEC.BAT and
(to take advantage of HIMEM.SYS / EMM386.EXE and DOS=HIGH,UMB)
by loading some driver into UMB (Upper Memory Blocks).
Note: such memory optimization requires a 386 or better CPU !
Note: memory optimizations and the use of the I-parameter on the
vary depending on the PC-model and other installed components.
This makes more DOS-memory available:
There should now be sufficient DOS-memory to run most
If there is NOT sufficient DOS-memory available to run a large
application, try configuring the networkClient (by running in
\NET the SETUP-program) for "Do Not Logon to Domain"
and then using the "Basic Redirector" to connect to the
NT-server (if Workgroup access is permitted by the NT-server
The Microsoft Network Client 3.0 installs the
Client-module, allowing a DOS-system to connect to shared
resources on a Microsoft network.
To allow other systems to access the disk and/or printer on a
you need to install the upgrade for the DOS-based Microsoft Network