ENet2.
ENet2.book Page ii Monday, May 4, 1998 9:53 AM Notices Copyright © 1998 Gateway 2000, Inc. All Rights Reserved 610 Gateway Drive N. Sioux City, SD 57049 USA All Rights Reserved This publication is protected by copyright and all rights are reserved. No part of it may be reproduced or transmitted by any means or in any form, without prior consent in writing from Gateway 2000. The information in this manual has been carefully checked and is believed to be accurate. However, changes are made periodically.
ENet2.book Page iii Monday, May 4, 1998 9:53 AM Contents Introduction.............................................................................................. 1 Connect the Network Cable.................................................................... 2 Configure the Controller and Install Drivers.......................................... 3 Windows 95...................................................................................... 3 Windows NT Server or Workstation.............................
ENet2.
ENet2.book Page 1 Monday, May 4, 1998 9:53 AM Introduction The OnBoard Ethernet Controller (OBEC) is an Intel 82558 ethernet controller device and may be detected by software as either and Intel EtherExpress PRO/100+ or an Intel 82558 ethernet controller. The OBEC may be enabled or disabled through the BIOS Setup utility. If you need to change the setting, refer to the system documentation for instructions on running the BIOS Setup utility.
ENet2.book Page 2 Monday, May 4, 1998 9:53 AM Connect the Network Cable To Connect the Network Cable 1. Connect a single network cable to the ethernet port as shown below. For 100BASE-TX, your network cable must be Category 5, twistedpair wiring. If you plan to run the controller at 100 Mbps, it must be connected to a 100BASE-TX hub or switch (not a 100BASE-T4 hub). For 10BASE-T, use Category 3, 4, or 5 twisted-pair wiring.
ENet2.book Page 3 Monday, May 4, 1998 9:53 AM Configure the Controller and Install Drivers Windows 95 Automatic Configuration This PCI computer automatically detects and configures the onboard PCIcompliant ethernet controller. The BIOS automatically sets the controller’s IRQ level and I/O address. If your computer displays an error while booting, it may require additional steps to configure. See “PCI Installation Tips” on page 28 for more information.
ENet2.book Page 4 Monday, May 4, 1998 9:53 AM Install the PROSet Software (Optional) PROSet is an enhanced utility you can use to easily configure and test your OBEC in Windows 95. PROSet also displays the computer resources that are assigned to each adapter you install. To Install PROSet 1. Insert the Configuration and Drivers disk in the disk drive. 2. From My Computer or the Windows Explorer, double-click the 3½ Floppy disk icon. 3. Click the PROSet icon or filename and click the right mouse button.
ENet2.book Page 5 Monday, May 4, 1998 9:53 AM 6. Select Network Adapters and click OK. 7. Click Have Disk. Insert the Configuration and Drivers disk and click OK. 8. Follow any prompts for Windows 95 installation disks and restart when prompted. Troubleshooting If you can’t connect to a server or if Windows 95 reports an error after you double-click Network Neighborhood, try the suggestions here first, then turn to Troubleshooting and FAQs on page 21 if necessary.
ENet2.book Page 6 Monday, May 4, 1998 9:53 AM Install Network Drivers - Windows NT Version 4.0 Only After enabling the ehternet controller in the computer and starting Windows NT, you need to install the correct drivers. Installing Windows NT 4.0 Drivers 1. Double-click the Network icon in the Control Panel. 2. Click the Adapters tab. 3. Click Add. You’ll see a list of adapters. 4. Don’t select an adapter from this list.
ENet2.book Page 7 Monday, May 4, 1998 9:53 AM Install Network Drivers - Windows NT Version 3.51 Only After enabling the OBEC in the computer and starting Windows NT, you need to install the correct drivers and test the controller. Installing the Windows NT 3.51 Drivers 1. Double-click the Network icon in the Control Panel. 2. Click Add Adapter. 3. When the list of adapters appears, scroll to the end of the list and select Requires disk from manufacturer. 4.
ENet2.book Page 8 Monday, May 4, 1998 9:53 AM Note: Windows 95 and Windows NT users: refer to the previous sections on Windows 95 and Windows NT. NetWare Client 32 users: refer to the NetWare readme files. • • Check the Windows NT Event Viewer for error messages. • Test the controller with PROSet. After installing the controller you can run PROSet from your hard disk. To do this, double-click the PROSet icon in the Control Panel. Click Test to run diagnostics.
ENet2.book Page 9 Monday, May 4, 1998 9:53 AM 2. Insert the Configuration and Drivers disk in a floppy drive, switch to that drive, and at the DOS prompt, type SETUP ENTER 3. If you have more than one PCI adapter in your computer, an adapter selection menu appears on the screen. Select the adapter you want by noting the Ethernet address. See “Installing Multiple Adapters” on page 11 for more information on multiple adapters. 4. Select Automatic Setup from the Main menu.
ENet2.book Page 10 Monday, May 4, 1998 9:53 AM • Test the adapter by running diagnostics in Setup. Additional testing is available by using a responder (see the next section). • Check the readme files. Responder Testing on the Network (Optional) Setup can test the OBEC more thoroughly if there is a responder on the network while you run the tests. Testing with a Responder on the Network 1. Go to a computer on the network with a comparable PCI adapter installed. 2.
ENet2.book Page 11 Monday, May 4, 1998 9:53 AM Installing Multiple Adapters All users: The system’s 12-digit, hexadecimal Ethernet address is printed on a sticker placed on the system board. The Ethernet address is sometimes called the node address or the MAC address. Note that the onboard PCI ethernet controller shares the PCI interrupt with PCI slot 1 (primary) and PCI slot 7 (secondary). NetWare users: The server drivers use the PCI slot number to identify each installed adapter.
ENet2.book Page 12 Monday, May 4, 1998 9:53 AM Select Duplex Mode (Optional) Duplexing is a performance option that lets you choose how the ethernet controller sends and receives data packets over the network. The ethernet controller can operate at full duplex only when connected to a full duplex 10BASE-T, 100BASE-TX switch, or another full duplex adapter. • Auto (requires a full duplex adapter or switch with autonegotiation capability).
ENet2.book Page 13 Monday, May 4, 1998 9:53 AM DOS ODI, NDIS 2.01 Clients Edit the NET.CFG or PROTOCOL.INI file. Add these keywords to the Link Driver section: FORCEDUPLEX 2 SPEED 100 (or 10 if 10BASE-T) NetWare Server In AUTOEXEC.NCF, load E100B.LAN and add the following statement (you must include the equal sign for servers): FORCEDUPLEX=2 SPEED=100 (or 10 if 10BASE-T) For more information, see the readme file for NetWare servers. Windows NT While running Windows NT: 1.
ENet2.book Page 14 Monday, May 4, 1998 9:53 AM Windows 95 While running Windows 95: 1. In the Control Panel, double-click the System icon. 2. Go to the Device Manager tab and select the controller. 3. Click Properties, then click OK to use the setup program (PROSet). 4. PROSet examines your system and displays the Adapter Setup window. If you have multiple adapters, click the adapter you are configuring (you can identify it by its Ethernet address). Each adapter must be configured separately.
ENet2.book Page 15 Monday, May 4, 1998 9:53 AM Choose Ethernet Controller Teaming Options The onboard PRO/100+ ethernet controller provides several options for increasing throughput and fault tolerance when running Windows NT 4.0 or NetWare 4.1x or newer: • Adapter Fault Tolerance (AFT) - provides automatic redundancy for your controller. If the primary controller fails, the secondary takes over.
ENet2.book Page 16 Monday, May 4, 1998 9:53 AM Note: For more information about Adapter Fault Tolerance, see the Adapter Fault Tolerance readme files on the Configuration and Drivers disk. To use Adapter Fault Tolerance, you must have at least two PRO/100+ adapters installed in your Windows NT 4.0 or NetWare 4.x workstation or server and they must be linked to the same network. Setting up Adapter Fault Tolerance in Windows NT 4.0 Setting up AFT in Windows NT 4.0 1.
ENet2.book Page 17 Monday, May 4, 1998 9:53 AM Setting up Adapter Fault Tolerance in NetWare Setting up AFT in NetWare 1. Copy the following lines from the EXAMPLES.TXT file (on the Configuration and Drivers disk) and paste them into the appropriate files. These commands assume the AFT.NLM and E100B.LAN files are in the system directory of your workstation. (Files must be copied from the Configuration and Drivers disk to your workstation's hard drive).
ENet2.book Page 18 Monday, May 4, 1998 9:53 AM 2. Modify the lines to match your workstation or server’s requirements. 3. Save the STARTUP.NCF and AUTOEXEC.NCF files and restart your server. Deleting a Team To remove a team in AFT, ALB or FEC mode, edit out the lines above. Or, temporarily remove the team by issuing the unbind command with the slot number for the primary controller in the group.
ENet2.book Page 19 Monday, May 4, 1998 9:53 AM 4. Click OK when prompted. You’ll see the Adapter Teaming Configuration window. 5. Follow the instructions to assign adapters to a team. ALB supports up to two adapter teams, with two, three, or four adapters per team. 6. Select Load Balancing in the Team Function area. 7. Click OK and then click Close to finish. When prompted, restart your computer. Deleting a Team Deleting a Team 1. Double-click the Network icon in the Control Panel. 2.
ENet2.book Page 20 Monday, May 4, 1998 9:53 AM Copy these lines into the AUTOEXEC.NCF file ;- Load LAN driver on 1st controller load e100b slot=7 frame=ethernet_802.2 name=pri_802.2 ;- Load LAN driver on 2nd adapter load e100b slot=8 frame=ethernet_802.2 name=sec_802.2 ;- Bind ipx to 1st controller bind ipx pri_802.2 net=2 ;- Set the 2nd adapter to be a Load Balancing Partner to ;- the first controller aft balance 7 8 Where: slot= the slot your PRO/100+ adapter is installed in, such as 7.
ENet2.book Page 21 Monday, May 4, 1998 9:53 AM Setting -Up Fast EtherChannel Fast EtherChannel (FEC) is a performance technology developed by Cisco to increase your workstation or server’s throughput. Unlike ALB, you can configure FEC to increase both transmission and reception channels between your workstation or server and switch. FEC works only with FECenabled Cisco switches, such as the Catalyst* 5000 series.
ENet2.book Page 22 Monday, May 4, 1998 9:53 AM Deleting a Team Deleting a Team 1. Double-click the Network icon in the Control Panel. 2. On the Adapters tab, select the FEC team to delete. 3. Click Remove. You’ll see a confirmation dialog. Click Yes. 4. Click Close. Restart when prompted. Setting up FEC in NetWare Setting up FEC in NetWare Note: Fast EtherChannel must be loaded before the PRO/ 100+ adapter driver, E100B.LAN, or any other LAN driver. 1. Copy the following lines from the EXAMPLES.
ENet2.book Page 23 Monday, May 4, 1998 9:53 AM Where: slot= the slot in which your PRO/100+ adapter is installed, such as 7. If you don’t know the number, load the driver without it. NetWare will prompt you with available PCI device numbers. frame= the frame type of the network segment the computer is on. 7 is the primary controller’s slot number. 8 is the secondary adapter’s slot number. 2. Modify the lines to match your server’s requirements. 3. Save the AUTOEXEC.NCF and STARTUP.
ENet2.book Page 24 Monday, May 4, 1998 9:53 AM Troubleshooting and FAQs If the OnBoard Ethernet Controller Can’t Connect to the Network Make Sure the Cable is Installed Properly The network cable must be securely attached at both RJ-45 connections (controller and hub). The maximum allowable distance from controller to hub is 100 meters. If the cable is attached and the distance is within acceptable limits but the problem persists, try a different cable.
ENet2.book Page 25 Monday, May 4, 1998 9:53 AM LED Indication Meaning LNK On The controller and switch are receiving power; the cable connection between the switch and controller is good. Off The controller and switch are not receiving power; the cable connection between the switch and controller is faulty; or you have a driver configuration problem. 100 On Operating at 100 Mbps. Off Operating at 10 Mbps.
ENet2.book Page 26 Monday, May 4, 1998 9:53 AM Frequently Asked Questions (FAQs) SETUP.EXE reports the controller is “Not enabled by BIOS”. • The PCI BIOS is not configuring the controller correctly. Try “PCI Installation Tips” on page 28. The computer hangs when the drivers are loaded. • Change the PCI BIOS interrupt settings. See “Technical Information” on page 28 for PCI installation tips. • If you are using EMM386, it must be version 4.49 or newer (this version ships with MS-DOS* 6.22 or newer).
ENet2.book Page 27 Monday, May 4, 1998 9:53 AM The controller stopped working when another adapter was added to the computer. • • Make sure the cable is connected to the controller. • Make sure the other adapter supports shared interrupts. Also, make sure your operating system supports shared interrupts — OS/2 doesn’t. • Try reseating the most recently installed adapter. Make sure your PCI BIOS is current. See “PCI Installation Tips” on page 28.
ENet2.book Page 28 Monday, May 4, 1998 9:53 AM Technical Information PCI Installation Tips PCI computers are designed to automatically configure add-in cards each time the computer starts. Your PCI computer sets the I/O address and IRQ level for your network controller when the computer starts. These values cannot be changed by Intel adapter software. If you experience a problem when the computer starts, additional configuration steps may be required.
ENet2.book Page 29 Monday, May 4, 1998 9:53 AM • Configure the slot for level-triggered interrupts. The slot the controller is using must be configured for level-triggered interrupts rather than edge-triggered interrupts. Check your PCI BIOS Setup program.
ENet2.book Page 30 Monday, May 4, 1998 9:53 AM Shared hubs In a shared network environment, computers are connected to hubs called repeaters. All ports of the repeater hub share a fixed amount of bandwidth, or data capacity. On a 100 Mbps shared hub, all nodes on the hub must share the 100 Mbps of bandwidth. As stations are added to the hub, the effective band-width available to any individual station gets smaller. Shared hubs do not support full duplex.
ENet2.book Page 31 Monday, May 4, 1998 9:53 AM Network Software License Agreement PLEASE REVIEW THE LICENSE AGREEMENT BELOW. BY OPENING THIS SOFTWARE OR PACKAGE OR OTHERWISE DOWNLOADING OR COPYING THIS SOFTWARE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. DO NOT USE THIS SOFTWARE UNTIL YOU HAVE CAREFULLY READ AND AGREED TO THE FOLLOWING TERMS AND CONDITIONS. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, DO NOT INSTALL OR USE THIS SOFTWARE.
ENet2.book Page 32 Monday, May 4, 1998 9:53 AM EXPORT LAWS: You agree that the distribution and export/re-export of the Software is in compliance with the laws, regulations, orders or other restrictions of the U.S. Export Administration Regulations. Some products may contain encryption technology. U.S. Department of Commerce Encryption Regulations are applicable on all products imported to and exported from the United States and Puerto Rico.
ENet2.
ENet2.
