Using Multiple Protocols with MS-DOS and Windows 3.1

A remoteboot MS-DOS or Windows 3.1 client always runs the NetBEUI protocol. This section describes how to install support for TCP/IP, DLC, and IPX protocols for use by remoteboot clients.

Installing TCP/IP Support

Before you set up clients to use TCP/IP, you must either enable DHCP to assign addresses automatically, or you must assign IP addresses and subnet masks for each client that will use TCP/IP. (See the Windows NT Server TCP/IP manual for more information about TCP/IP addresses.)

When you have arranged for addresses, you can then enable TCP/IP support.

To enable TCP/IP support

1. Edit the <systemroot>\Rpl\Bblock\Netbeui\adapter\Dosbb.cnf file, where adapter is the name of the network adapter. Remove the semicolon (;) in column one of this line:

;DRV BBLOCK\TCPDRV.DOS /I:C:\LANMAN.DOS ~ ~

2. For each profile (or personal copy of a profile) that will support TCP/IP, edit the following files as described:

In <systemroot>\Rpl\Rplfiles\Profiles\profile\Autoexec.bat, where profile is the name of the profile, enable umb.com, nmstr, and load tcpip by removing the REM designations at the beginnings of those lines.
In <systemroot>\Rpl\Rplfiles\Profiles\profile\Config.sys, where profile is the name of the profile, enable nemm.dos by removing the REM designation at the beginning of that line.

3. Boot a client using one of the profiles altered in the last step.

Installing MS-DLC Support

To install MS-DLC support

· At the client, type load msdlc.

Or, add this command to the end of the client's Autoexec.bat file.

Installing IPX Support

When you install IPX support, you will need the Microsoft Network Client version 2.2 NetWare Connectivity disk and the Novell NetWare SHGEN-1 and SHGEN-2 disks (or the WSGEN disk).

Note

IPX support is installed per adapter and is MS-DOS version specific. Follow the installation procedure for each adapter that will support IPX; define profiles for each version of MS-DOS that will support IPX.

To install IPX support

1. On the server, edit the <systemroot>\Rpl\Bblock\Netbeui\adapter\Dosbb.cnf file, where adapter is the name of the network adapter. Remove the semicolon (;) in column one of this line:

;DRV BBLOCK\IPXNDIS.DOS ~ ~ ~

2. Create a new profile with a name that describes IPX support (for example, DOS62IPX).

Note

IPX is MS-DOS version specific. You must create a separate profile for each version of MS-DOS that will support IPX.

3. Assign a client to the new profile.

4. Boot the client.

At the remoteboot logon prompt (the prompt that first appears when you start the client), supply the name and password of an account that is a member of the Administrators group on the Windows NT Server computer.

5. If the client does not have a floppy disk drive, use the floppy disk drive of a server on the network:

First, at the server (it doesn't have to be the remoteboot server), use File Manager or the net share command to share the server's floppy disk drive.
Then, at the client, use File Manager or the net use command to connect to the shared floppy disk drive.

6. Put the Microsoft Network Client NetWare Connectivity disk in the floppy disk drive.

7. On the client, run the NetWare Connectivity Setup program by typing a:nwsetup (use a different drive letter if needed).

When prompted, insert the Novell NetWare SHGEN-1 and SHGEN-2 disks (or the WSGEN disk).

8. Reboot the client.

Supply the client password (if any).

9. Log on to the client with a normal user account.

10. To start using the IPX protocol, type nwload. Or, add this command to the end of the client's Autoexec/bat file.

IPX is now installed on the client's profile and is available for use by other clients using this profile.