Microsoft KB Archive/142857

From BetaArchive Wiki

Article ID: 142857

Article Last Modified on 2/22/2007



APPLIES TO

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows NT Workstation 3.5
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 3.5
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition



This article was previously published under Q142857


SUMMARY

This article explains how to add an NDIS driver for Network Interface Cards (NIC) that were not originally included in the Network Client Administrator. This information applies to the Network Client version 3.0 for MS-DOS and Windows Startup Disk.

Verify that the 3.5" HD disk to which the client files will be copied is a DOS system disk and formatted under DOS. If the disk is formatted under NT, the copy process will fail.

MORE INFORMATION

To configure this disk:

NOTE: The following example is for the Intel EtherExpressPro NIC; however, this example can serve as a template for all NDIS compatible drivers.

  1. Copy the Epro.dos driver to the A:\Net directory.
  2. Modify the Net\Protocol.ini file and change the [EPRO$] section to "drivername=EPRO$".


NOTE: The "drivername=" information is included on most manufacturers' disks in the sample Protocol.ini file that comes with the network card.

  1. Modify the Net\System.ini file and change the [network drivers] section to "netcard=Epro.dos".


NOTE: The file that the "netcard=" equals is also on the manufacturer's disk.

Additional drivers can be found on the Windows NT Server compact disc in the Clients\Wdl\Update directory.

For more information, please see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: 128800
TITLE : How to Provide Additional NDIS2 Drivers for Network Client 3.0


Sample Protocol.ini Entries

[network.setup]
version=0x3110
netcard=EPRO$,1,EPRO$,1
transport=ms$ndishlp,MS$NDISHLP
transport=ms$nwlink,MS$NWLINK
lana0=EPRO$,1,ms$nwlink
lana1=EPRO$,1,ms$ndishlp

[EPRO$]
drivername=EPRO$
; IRQ=3           <----------------- You may have to adjust this.
; IOADDRESS=0x330 <----------------- You may have to adjust this.
; IOCHRDY=Late
; TRANSCEIVER=Thin Net (BNC/COAX)

[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP

[MS$NDISHLP]
drivername=ndishlp$
BINDINGS=EPRO$

[ms$nwlink]
drivername=nwlink$
FRAME=Ethernet_802.2
BINDINGS=EPRO$
LANABASE=0
                

Sample System.ini Entries

[network]
filesharing=no
printsharing=no
autologon=yes
computername=TEST
lanroot=A:\NET
username=Administrator
workgroup=TESTDOM
reconnect=no
dospophotkey=N
lmlogon=0
logondomain=BOARD
preferredredir=full
autostart=full
maxconnections=8

[network drivers]
netcard=epro.dos     <----------- If the path is not set, specify the
                                   full directory (for example,
                                   c:\net\epro.dos).

transport=ndishlp.sys
devdir=A:\NET
LoadRMDrivers=yes

[Password Lists]
*Shares=a:\net\Share000.PWL
                


Additional query words: 4.0 make installation startup disk prodnt dos client unsupported kbfaqw2ksetup

Keywords: kbhowto kbnetwork KB142857