Microsoft KB Archive/190417

= Banyan VINES 16-Bit Network Client and Protocol Missing =

Article ID: 190417

Article Last Modified on 1/23/2007

-

APPLIES TO


 * Microsoft Windows 98 Standard Edition

-



This article was previously published under Q190417



SYMPTOMS
The Banyan DOS/Windows 3.1 Client and Banyan VINES protocol may be missing from Network properties after you install Windows 98 from a shared network drive on a Banyan VINES network.



CAUSE
This issue can occur if you start your computer using a Banyan VINES boot disk, and then install Windows 98 from a shared network drive to a new folder on your hard disk.



RESOLUTION
To work around this issue, install and configure the Banyan VINES 16-bit network client and the appropriate protocol after Windows 98 is installed. To do so, follow these steps:

Installing the Banyan VINES 16-Bit Network Client

 * 1) Click Start, point to Settings, and then click Control Panel.
 * 2) Double-click Network.
 * 3) On the Configuration tab, click Add.
 * 4) Click Client, and then click Add.
 * 5) In the Manufactures box, click Banyan, click Banyan DOS/Windows 3.1 Client in the Network Clients box, and then click OK.
 * 6) On the Configuration tab, click Add.
 * 7) Click Protocol, and then click Add.
 * 8) In the Manufactures box, click Banyan, click Banyan VINES Ethernet Protocol or Banyan VINES Token Ring Protocol in the Network Protocols box, and then click OK.
 * 9) Click OK, and then restart your computer when you are prompted to do so.

Configuring the Banyan VINES 16-Bit Network Client
The following sections list the entries required in the Autoexec.bat, Config.sys, and Protocol.ini files to use the Banyan VINES 16-bit network client in Windows 98. The entries differ depending on whether Banyan VINES is installed as the primary network client (connecting to a Banyan VINES server) or with the Microsoft Client for Microsoft Networks.

NOTE: These entries apply only to Network Device Interface Specification (NDIS) drivers. If you are using monolithic Banyan VINES drivers, you must use Banyan's PCConfig utility to change Banyan drivers to NDIS drivers. Make sure the section name in the Protocol.ini file matches the driver name.

Banyan VINES as the Primary Network Client:

  The Autoexec.bat file should contain the following lines: cd \banfiles ban ndisban ; ndtokban for token ring redirall netbind arswait z:login c:     cd\   The Config.sys file should contain the following lines: device=c:\banfiles\protman.dos /i:c:\banfiles device=c:\banfiles\ndis2driver eg: exp16.dos   The Protocol.ini file should contain the following lines: [PROTOCOL MANAGER] drivername=protman$

[VINES_XIF] drivername=ndisban$ ; ndtokban$ for token ring bindings=MS$EE16

[MS$EE16] drivername=EXP16$ interrupt=5 ioaddress=0x300 iochrdy=late 

Banyan VINES with Microsoft Client for Microsoft Networks:

  The Autoexec.bat file should contain the following lines: c:\windows\net initialize cd \banfiles ban ndisban ; ndtokban for token ring redirall c:\windows\net start arswait z:login c:     cd\   The Config.sys file should contain the following lines: rem device=c:\banfiles\protman.dos /i:c:\banfiles rem device=c:\banfiles\ndis2driver eg: elnkii.dos </li>  The Protocol.ini file should contain the following lines: [NDISBAN$] ; NDTOKBAN$ for token ring drivername=NDISBAN$ ; NDTOKBAN$ for token ring bindings=ELNKII$

[NWLINK$] drivername=NWLINK$ frame_type=4 cachesize=0 bindings=ELNKII$

[NETBEUI$] drivername=NETBEUI$ lanabase=0 sessions=10 ncbs=12 bindings=ELNKII$

[ELNKII$] drivername=ELNKII$ transceiver=external interrupt=2 ioaddress=0x280 maxtransmits=12 datatransfer=pio_word xmitbufs=2

[PROTMAN$] priority=ndishlp$ drivername=protman$

[NDISHLP$] drivername=ndishlp$ bindings=ELNKII$ </li></ul>

<div class="moreinformation_section">

MORE INFORMATION
For more information about how to install and configure the Banyan VINES 16-bit network client in Windows 98, please see Chapter 17 of the Microsoft Windows 98 Resource Kit.

Keywords: kb3rdpartynetclient kbprb kbsetup KB190417

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.