56, NT network card and Novell network card interoperability Hot Network
Recently, a computer training center to establish a diskless NT teaching network, because the NT diskless Workstation network card has strict requirements: the number of cards (Adapter ID, that is, node address, a total of 12 bytes) of the first 6 characters, must be the beginning of 0020AF or 00608C, and the network card must be installed RPL (Remote Initial program Load) to run and Support NT boot Rom (which records with NT communication programs) can be identified for NT remote boot server. We built the NT teaching network workstations with the network card to meet the above requirements, the establishment of a diskless NT teaching NET, has been operating normally. Since the operating speed of the Diskless NT Workstation is too slow, I would like to change to Novell diskless teaching network, the results found that the workstation without disk NT could not log on to Novell 3.12, Novell 4.10, Novell 4.11 Chinese version server. Another company, for training The need for Microsoft's family of Office software (which, after many trials, can only run windows3.x on a Novell Diskless station and not run WINDOWS95), must be changed to a Novell diskless teaching network to a diskless NT teaching network, with the result of a surprising discovery that The diskless workstation, which is logged on to the Novell Diskless Teaching network, also fails to log on to the NT Server4.0 server. After many experiments, the author has developed a method: to make the card number of the network card is not 0020AF or 00608C support RPL boot ROM network card with support NT boot ROM network card can also successfully login NT diskless networks; NT dedicated NIC can also successfully log on to Novell Diskless network. The detailed steps are described below.
First, so that does not meet the NT requirements of the network card successfully login NT Server
Currently, NT "Remote Boot service" supports only the following network adapters:
If the NT Server "remote Boot service" does not support your network card brand and model, or even if the remote boot service supports your network card brand and model, the first six characters of your NIC's adapter ID do not begin with 0020AF or 00608C, You can then use the RPLCMD.EXE in the NT installation directory to enable NT to support your network card. Rplcmd. EXE use as follows: At the DOS prompt, enter the following command:
Rplcmd [\ server computer name]
The following command options appear on the screen:
Adapter Boot Config profile Service vender Wksta [quit]
which
The adapter is used to modify the record that the workstation passes the adapter ID to the server on the first boot, and this record is an incomplete record;
Boot to modify the boot block record, its specific content for the network card brand and use which dosbb.cnf.
Config to modify the configuration record.
Profile Modify configuration file
Service Control Remote Boot services
Vender set the name of the network card manufacturer or the first 6 digits of the card number.
Wksta Modify Workstation Records
Depending on the remote boot workstation, use MS-DOS, WINDOWS3. X, or using Windows95 instead of different methods. Comparatively speaking, installing remote MS-DOS and windows3.x workstations is relatively simple, while installing WINDOWS95 workstations is much more complex. The following two situations are described:
Add network adapters for MS-DOS and windows3.x workstations
Step ①: Copy the new network adapter driver to the \winnt\rpl\bblock\ndis directory, typically with a. dos file name extension. Where Winnt is the name of the directory you chose when you installed Windows NT, the following is the same.
Step ②: Add a \winnt\rpl\bblock\netbeui\adapter directory where adapter is the name of the network adapter, which must contain the following two files: DOSBB. CNF and Protocol.ini. The two files are available in the driver disk with the network card, copied directly to this directory.
Step ③: Use the Rplcmd.exe program to add the vendor data for this network card:
C:\winnt>rplcmd
Adapter Boot Config profile Service vender wksta [Quit]
ADD Del enum:a
vendername=00b897 (first six characters of the adapter ID of my network card)
Vendercomment=topstar te-2000b hotspot Network
Where Vendername 00b897 is the first 6-bit code for the card number of the NIC being added; Vendercomment is an annotation description.
Step ④: 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\dosbb.cnf
Bootcomment=dos Topstar te-2000b
Windowsize=0
Where the value of Bootname can be set arbitrarily, Vendername 00b897 and ③ step vendername must be the same; Bbcfile in DirName is the directory name, different network cards will have different names; Bootcomment is a description of the annotation.
Step ⑤: Add the configuration of the network card
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\dos622.fit
Fitpersonal=fits\dos622p.fit
configcomment=dos6.22 for Topstar te-2000b
Where the value of ConfigName can be set arbitrarily, bootname must be the same as the value set in step ④.
Step ⑥: Perform the remote boot manager → configuration → check configuration.
To add a network card to the WINDOWS95 workstation
Step ①: First, according to the above method to set the workstation into a DOS workstation;
Step ②: Copy the dosbb.cnf in the \winnt\rpl\bblock\netbeui\adapter directory into W95BB.CNF, where adapter is the name of the network card.
Step ③: Modify W95BB. CNF, will
EXE bblock\i13.com
Changed into: EXE bblock\w95i13.com
Step ④: 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\w95bb.cnf
Bootcomment=dos Topstar te-2000b
Windowsize=0
Where the value of the bootname can be set arbitrarily, the remainder is visible in the preceding explanation.
Step ⑤: Add the configuration of the network card
C:\winnt>rplcmd
Adapter Boot Config profile Service vender wksta [Quit]
ADD Del enum:a
configname=w95x
bootname=w95x
Dirname=dos
Dirname2=win95 (must enter WIN95, cannot write other name)
Fitshared=fits\win95.fit
Fitpersonal=fits\win95p.fit
Configcomment=w95 for Topstar te-2000b
Where the ConfigName w95x can be set arbitrarily, bootname must be the same as the name set in step ④.
│ Step ⑥: Perform the remote boot manager → configuration → check configuration.
│
Second, the NT dedicated network card used in Novell Diskless network
When used on the Novell Diskless network with an NT dedicated network card, the following information is displayed on the screen (the NIC I use is Topstar te-2000b, and the RPL ROM on the NIC is the NT produced by Shanghai Scientific Electronics CO. Ltd). Special ROM):
NT RPL bootrom v1.00 (920626)
D-link DE-250 bootrom Driver mlid v2.02 (931101)
Copyright (C) d-link coorperation 1994.All right reserved.
What Server would been found,please Select a number which you want?
1.NetWare PRL Server
2.IBM LAN Server3.0
3.IBM LAN Server4.0
4.MS LAN man Server
5.The available Server
If no key Mapping,system would select 5 after 5 seconds.
rpl-rom-adr:0000 2101 183f
Rpl-rom-irq:3
rpl-rom-pio:0300
RPL-ROM-FFC: This number keeps growing.
The workstation was unable to log on to Novell 3.12, Novell 4, for a long time. 10, Novell 4.11 Chinese version of the server. You can resolve the problem by adding the following two command lines to the autoexec.cnf file on the server, or by entering the following two command lines on the server's console:
Load RPL hotspot Network
Bind RPL to Ne2000
Among them, Ne2000 is the driver name of the workstation network card, different network card will have different name. If the RPL ROM of the NIC is Novell-specific, the last two sentences should not be added.