56. Interoperability of NT network cards and Novell network cardsHot Network
Recently, a diskless NT teaching network was established for a computer training center. Because the network cards on NT diskless workstations have strict requirements: the first 6 characters of the card number (Adapter ID, which accounts for 12 bytes in total) of the network card must start with 0020AF or 00608C, and the network card must be equipped with RPL (Remote Initial Program Load) and supports NT to be identified by the NT remote boot server. The network card used for the workstations we built for NT teaching network meets the above requirements, and the diskless NT teaching network established has been running normally. Later, because the diskless NT workstation runs too slowly, I wanted to change it to Novell diskless teaching network. As a result, I found that the workstations that run normally on the diskless NT teaching network cannot log in to the Chinese version of Novell 3.12, Novell 4.10, and Novell 4.11 servers; later, in order to train Microsoft series office software needs (after multiple experiments, it can only run on the Novell diskless station and cannot run Windows 95), I had to change a Novell diskless teaching network to the diskless NT teaching network. As a result, I was surprised to find that logging into a normal diskless workstation on the Novell diskless teaching network also cannot log in to the NT Server 4.0 server. After many experiments, the author has found a method: to enable the network card with the card number of the 0020AF or 00608C that supports RPL Boot Rom network cards and has a Boot Rom network that supports NT can also successfully log into the NT diskless network; similarly, the NT dedicated network card can also successfully log into the Novell diskless network. The detailed steps are now introduced as follows.
1. Make the network card that does not meet the NT requirements successfully log into the NT server
Currently, NT "Remote Start Service" only supports the following network cards:
If the NT server "Remote Start Service" does not support your network card brand and model, or even if the "Remote Start Service" supports your network card brand and model, the first six characters of your network card Adapter ID do not start with 0020AF or 00608C, you can use the NT installation directory to make NT support your network card. The method of use is as follows: Enter the following command at the DOS prompt:
RPLCMD [\\Server Computer Name]
At this time, the following command options will appear on the screen:
Adapter Boot Config Profile Service Vender Wksta [quit]
in:
Adapter is used to modify the record that passes the Adapter ID to the server when the workstation is first started. This record is an incomplete record;
Boot Modify Boot block record, the specific content is the network card brand and which one is used.
Config Modify the configuration record.
Profile Modify the configuration file
Service Control remote startup service
Vender sets the first 6 digit code of the network card manufacturer's name or card number.
Wksta Modify workstation records
Different approaches are adopted depending on whether the remote boot workstation is using MS-DOS, or Windows 95. In comparison, installing remote MS-DOS and workstations is relatively simple, while installing Windows 95 workstations is much more complicated. The following are two situations:
■Add network cards for MS-DOS and workstations
Step 1: Copy the driver of the new network card into the \winnt\rpl\bblock\ndis directory, and its file extension is generally .dos. Among them, winnt is the directory name selected when installing Windows NT, the following is the same.
Step 2: Add a \winnt\rpl\bblock\netbeui\adapter directory, where adapter is the name of the network card. This directory must contain the following two files: dosbb.cnf and. There are these two files on the driver disk with the network cartridge, and you can copy them directly to this directory.
Step 3: Use the program to add the manufacturer data of this network card:
c:\winnt>rplcmd
Adapter Boot Config Profile Service Vender Wksta [Quit]
Add Del Enum: a
VenderName=00b897 (the first six characters of the Adapter ID of my network card)
VenderComment=TopStar TE-2000B Hot Network
Among them, 00b897 of VenderName is the first 6 digits of the card number of the added network card; VenderComment is annotation description.
Step 4: Add the bblock of the network card:
c:\winnt>rplcmd
Adapter Boot Config Profile Service Vender Wksta [Quit]
Add Del Enum: a
BootName=DOSTOPSTAR
VenderName=00b897
BbcFile=bblock\netbeui\dirname\
BootComment=DOS TopStar TE-2000B
Windowsize=0
The value of BootName can be set arbitrarily, the 00b897 of VenderName must be the same as the VenderName in step 3; the dirname in BbcFile is the directory name, and different network cards will have different names; BootComment is the comment description.
Step 5: Add network card configuration
c:\winnt>rplcmd
Adapter Boot Config Profile Service Vender Wksta [Quit]
Add Del Enum: a
ConfigName=DOS622_TopStar
BootName=DOSTOPSTAR
DirName=DOS
DirName2=DOS622
FitShared=fits\
Fitpersonal=fits\
ConfigComment=DOS6.22 for TopStar TE-2000B
The value of ConfigName can be set arbitrarily; BootName must be the same as the value set in step 4.
Step 6: Execute “Remote Start Manager → Configuration → Check Configuration”.
■Add a network card for Windows 95 workstations
Step 1: First set the workstation as a DOS workstation according to the above method;
Step 2: Copy the directory \winnt\rpl\bblock\netbeui\adapter, where adapter is the name of the network card.
Step 3: Modify,
EXE BBLOCK\
Change to: EXE BBLOCK\
Step 4: Add the bblock of the network card:
c:\winnt>rplcmd
Adapter Boot Config Profile Service Vender Wksta [Quit]
Add Del Enum: a
BootName=W95X
VenderName=00b897
BbcFile=bblock\netbeui\dirname\
BootComment=DOS TopStar TE-2000B
Windowsize=0
The value of BootName can be set arbitrarily, and the rest can be seen in the previous explanation.
Step 5: Add network card configuration
c:\winnt>rplcmd
Adapter Boot Config Profile Service Vender Wksta [Quit]
Add Del Enum: a
ConfigName=W95X
BootName=W95X
DirName=DOS
DirName2=WIN95 (WIN95 must be entered, and cannot be written as other names)
FitShared=fits\
Fitpersonal=fits\
ConfigComment=W95 for TopStar TE-2000B
The W95X of ConfigName can be set arbitrarily; the BootName must be the same name as the one set in step 4.
│Step 6: Execute “Remote Start Manager → Configuration → Check Configuration”.
│
2. Use NT dedicated network card on Novell diskless network
When using NT dedicated network card on Novell diskless network, the following information will be displayed on the screen (the network card I use is Topstar TE-2000B, and the RPL ROM on the network card is NT dedicated ROM produced by Shanghai Scientific Electronics CO. LTD):
NT RPL BootROM v1.00 (920626)
D-link DE-250 BootROM Driver MLID v2.02(931101)
Copyright(C) D-Link Coorperation right reserved.
What Server will been found,please select a number which you want?
PRL Server
LAN Server3.0
LAN Server4.0
LAN MAN Server
first available Server
If no key mapping,system will select 5 after 5 seconds.
RPL-ROM-ADR:0000 2101 183f
RPL-ROM-IRQ:3
RPL-ROM-PIO:0300
RPL-ROM-FFC: This number is growing continuously.
After waiting for a long time, the workstation could not log in to the Chinese version of Novell 3.12, Novell 4.10, and Novell 4.11 servers. At this time, add the following two command lines to the file on the server, or enter the following two command lines on the server console, which can solve the problem:
Load rpl Hot Network
Bind rpl to Ne2000
Among them, Ne2000 is the driver name of the workstation network card, and different network cards will have different names. If the RPL ROM of the network card is Novell-specific, you do not need to add it as mentioned above.