- 3com Network Interface Card User Guide
Table Of Contents
- About This Guide
- Introduction
- Overview
- 3CR990 NIC Features
- DynamicAccess LAN Agent
- Windows2000 Offload Features
- Installing and Connectingthe NIC
- Installing NICDrivers in Windows
- Installing DynamicAccess Software in Windows
- Overview
- Installing the DynamicAccess LAN Agent for a Client NIC
- Installing DynamicAccess Software for a Server NIC
- Configuring Groups and VLANs for a Server NIC
- Planning the Configuration
- Working With Server Features
- Creating a Group
- Adding NICs to a Group
- Specifying a Dedicated IP Address
- Changing an IP Address
- Creating a VLAN
- Specifying Traffic Priorities
- Saving the Configuration
- Disabling Load Balancing for a Group
- Changing the Primary NIC
- Removing a NIC from a Group
- Deleting or Editing a VLAN
- Displaying NIC Properties
- Displaying Group Properties
- Specifying Failover from Gigabit to 10/100 PCI
- Troubleshooting a Load Balancing Configuration
- Changing Windows2000 Property Settings
- Identifying Windows 2000 Miniport and LAN Connections
- Using Windows2000 Offload Features
- Installing DynamicAccess LAN Encryption Software
- Installing NetWare Client and ServerDrivers
- Overview
- Installing and Configuring the NetWare Server Driver
- Using the Latest Support Packs
- Obtaining NetWare Loadable Modules
- Server Software Installation Requirements
- Installing the NetWare 3.12 Server Driver
- Installing the Server Driver for NetWare 4.11 and 5.0 UsingINETCFG
- Installing the Server Driver and DynamicAccess Technology Using AUTOEXEC.NCF
- Installing Multiple Server NICs
- Verifying the PCI Slot Number
- Installing Server Features
- Configuring Groups
- Verifying the Installation and Configuration
- Changing NetWare Driver Configuration Parameters
- Maintaining Groups
- Configuring the NIC
- Configuring IP Security
- Troubleshooting the NIC
- Running NIC Diagnostics
- Obtaining Drivers
- Specifications and CablingRequirements
- Installing the 3ComDMIAgent
- EtherCD Content and Navigation
- Installing a 3Com NIC While Installing the NOS
- Technical Support
- Index
- FCC Class B Statement
- FCC Declaration of Conformity
- Industry Canada Class B Emission ComplianceStatement
- Avis de Conformité à la Réglementation d’IndustrieCanada
- VCCI Class B Statement
- 3Com End User Software License Agreement
- Product Registration
![](/manual/3com/3cr990svr95/3com-network-interface-card-user-guide/images/img-84.png)
84 CHAPTER 4: INSTALLING DYNAMICACCESS SOFTWARE IN WINDOWS
13 Verify that the displayed components are correct for
installation on your computer and click Next.
The system copies files from the EtherCD to the destination
location, sets up the registry, builds drivers, and updates
bindings.
Follow the rest of the setup wizard instructions to install
the software properly.
If you see “version conflict” messages, click Cancel to
continue.
When prompted to reboot, click Yes to continue.
If you see “Winsock 2 setup” error messages, reboot the
system and re-start the 3Com LAN Encryption installation.
If prompted to insert the Windows 98 CD, insert it so that
certain Windows files can be copied. (Prompting for the
Windows CD depends on your PC configuration.) Follow
the displayed prompts.
The setup program continues once the appropriate
Windows files have been located and copied to the
appropriate Windows folders.
The Setup Complete dialog box appears.
14 Select Yes, I want to restart my computer now and
click Finish to restart your computer.
If you have not yet created one or more connection
profiles, you will be prompted to use the DynamicAccess
LAN Client dialog box to create the profiles. See the
“Creating a Connection Profile” topic in the administrator’s
guide for more information.
After you have successfully installed the DynamicAccess
LAN Encryption client, the physical adapters (NICs) and
upper level protocols (TCP/IP, IPX, etc.) in your computer
bind to the virtual adapters created by the DynamicAccess
LAN Encryption software. The bindings of the upper level
protocols to the physical adapters are removed and
replaced with bindings to the virtual adapters.