v Review the Windows server event log for either communication errors or device driver errors. You can use the Windows server Event Viewer to do this. In Windows 2000, if you can not find text in event logs for the IBMTRP token-ring service, you need to make changes in the Windows 2000 Registry.
Note: If you are not familiar with the process for making changes in the Windows 2000 Registry, contact a service representative.
If you are familiar with this process, to make the text in the event logs viewable, complete the following steps:
1. From the Windows 2000 Start menu, click Run.
2. Type regedit.
3. In the Registry Editor, go toHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IBMTRP 4. Select EventMessageFile.
Note: If the EventMessageFile value does not exist, you must create it. From the Registry Editor Edit menu, select New, then String Value, and typeEventMessageFile.
5. From the Registry Editor Edit menu, select Modify.
6. Type %SystemRoot%\System32\netevent.dll;%SystemRoot%\System32\ibmsgnet.dll 7. Close the Registry Editor and restart Windows.
v When sharing adapters with OS/400, ensure that the drivers IBM iSeries Line Device Driver Port 1 and iSeries Line Device Driver Port 2 are listed and have a status of Enabled.
1. From Windows 2000 or Windows .NET Server, click on Start, then Programs, then Administrative Tools, then Computer Management.
2. Select System Tools; then click Device Manager.
3. At the top menu bar, select View and from the drop-down menu, select Show Hidden Devices to list all drivers.
4. Expand the Non-Plug and Play Drivers entry and locate in the list the iSeries Line Device Driver Port 1 and iSeries Line Device Driver Port 2.
5. Double-click on each driver and verify that the Device Usage is set to Enable.
6. Verify that the Device Status window indicates that This Device is working properly.
7. Click Cancel to terminate the verification.
v For Ethernet adapters, ensure that a driver with iSeries or AMD PCNET Family Ethernet Adapter (PCI) in its name is listed and has a status of started:
1. Click on Start, then Administrative Tools, then Computer Management, then System Tools, then Device Manager, then Network Adapters.
2. Ensure that a driver with iSeries or AMD PCNET Family Ethernet Adapter (PCI) in its name is listed and has a status of started.
v For token-ring networks, also in Device Manager, ensure that you have started the IBM High-Speed 100/16/4 Token-Ring PCI Adapter or IBM PCI Token-Ring Adapter.
Note: The start up setting should be Enable.
v For token-ring networks, ensure that the Network Data Rate setting is appropriate for your network.
v For Ethernet networks, ensure that the Link Speed and Duplex settings are appropriate for your switch or hub. If you have an IBM iSeries 1000/100/10 Ethernet Adapter, (Feature Code 5701) that does not connect with an early model of copper UTP gigabit Ethernet switch at speeds greater than 100 million bits per second, ensure that your switch is fully compliant with the IEEE 802.3ab standard for gigabit Ethernet on copper. Your switch manufacturer may be able to provide information about the standards compliance for your switch. If the switch is not fully IEEE 802.3ab compliant, the 5701 adapter may be limited to 100 million bits per second when running under Windows. This limitation generally does not apply to 5701 adapters running under OS/400 and Linux, however, as these environments include some support beyond the IEEE standard.
v If sharing adapters with OS/400, also ensure that you have set the Network Address to the same value that appears in theAdapter address field for the corresponding line description of OS/400. To review this, follow these steps:
1. Click on Start, then Programs, then Administrative Tools, then Computer Management, then System Tools.
2. Double-click Device Manager.
3. Expand Network Adapters, right-click on the adapter in the list, and select Properties from the menu.
4. Select the Advanced tab. From the list of parameters, find the Network Address and click to select. Ensure that the Values box is filled with the matching iSeries Line Description Local Adapter Address value.
5. Find and select the External Phy parameter. Ensure that the value is set to match the Line Speed and Duplex set in the iSeries Line Description.
6. On OS/400, use the WRKLIND command and select option 5 on the corresponding line to view the Local Adapter Address, Line Speed, and Duplex values.
v For token-ring networks, ensure that the Data Rate, Duplex, and Locally Administered Address settings match the values on the corresponding line description of OS/400: Line Speed, Duplex, and Adapter Address. To review this, follow these steps:
1. Select Control Panel, then Network, then the Adapters tab and press the Properties button.
2. Select the Advanced tab. From the list of parameters, find the Network Address (LAA) and click to select. Ensure that the Value Box is filled with the matching iSeries Line Description Local Adapter Address value.
3. Find the Data Rate and Duplex parameters. Select each and ensure that the value is set to match the Line Speed and Duplex set in the iSeries Line Description.
4. On OS/400, use the WRKLIND command and select option 5 on the corresponding line to view the Line Speed, Duplex, and Local Adapter Address values.
v Ensure that the IP Address, Subnet Mask, and Default gateway values are correct and that each adapter present has a unique IP addresss. To do this, do the following:
1. Click on Start, then Settings, then Network and Dial-up Connections.
2. Right-click on Local Area Connections and select Properties from the menu.
3. Select TCP/IP Protocol from the list of installed protocols and press the Properties button.
4. Check the values for the IP Address, Subnet Mask, and Default gateway. Also ensure that each adapter present has a unique IP addresss.
v Ensure that all iSeries Line Multi-Port Protocol Driver entry is present and enabled under all network adapters. To verify, open Network and Dial-up Connections, double-click on each connection, click on the Properties button, and ensure that the iSeries Line Multi-Port Protocol Driver is listed and selected.
v Test the communication link by using the PING command. You should be able to ping external systems as well as the external LAN port of OS/400 that shares the same physical network adapter.
v If the problem still persists, check the technical information databases at the IBM iSeries Support Web page . If you cannot find the solution there, contact your technical support provider.
Manually update LAN drivers in Windows 2000 or Windows .NET
Windows 2000 and Windows .NET generally automatically install LAN drivers that are appropriate for your LAN adapters and ports. However, if you have a special situation you can manually install or update a LAN driver.
To manually install or update a LAN driver for an adapter other than Virtual Ethernet in an externally attached Netfinity or xSeries server, go to the IBM Personal computing support Web site and select Servers, then Device driver file matrix.
To manually install or update a LAN driver for an adapter or port in an Integrated xSeries Server or for Virtual Ethernet, complete the following tasks:
1. “Begin the LAN driver installation or update”
2. “Select the adapter to install or update” on page 156
3. “Complete the LAN driver installation or update” on page 156
Begin the LAN driver installation or update: To begin the manual installation or update of the LAN driver or port in an Integrated xSeries Server or for Virtual Ethernet, complete the following steps:
1. From the Windows Start menu, select Settings, then Control Panel.
2. Double-click System.
3. In the System Properties window, select the Hardware tab.
4. If the new LAN driver is not digitally signed, or if you are unsure whether or not the LAN driver is digitally signed, ensure that the driver signing policy is set to Ignore:
a. In the System Properties window, click Driver Signing.
b. Note the current setting, then click Ignore, and then click OK.
5. Click Device Manager.
6. “Select the adapter to install or update” on page 156
Select the adapter to install or update: After you complete the steps to “Begin the LAN driver
installation or update” on page 155 of the LAN driver or port in an Integrated xSeries Server or for Virtual Ethernet, you will need to select the adapter.
To select the adapter that you want to install or update, complete the following steps:
1. In the Device Manager window, open Network Adapters.
2. Under Network Adapters, right-click the adapter that you want to update and select Properties.
3. In the Properties windows for the adapter, click the Driver tab.
4. Click Update Driver or Install Driver (only one will display).
5. In the Update Device Driver Wizard dialog, click Next.
6. “Complete the LAN driver installation or update”
Complete the LAN driver installation or update: Ensure that you have completed the first two tasks required to manually install or update the LAN driver or port in an Integrated xSeries Server or for Virtual Ethernet:
v “Begin the LAN driver installation or update” on page 155 v “Select the adapter to install or update”
To complete the LAN driver or port installation or update, use one of the following procedures that fits your situation:
v You are using Windows 2000, or have been directed to install the LAN driver from a specific folder for Windows .NET
v You are using Windows .NET and have not been directed to install the LAN driver from a specific location
If you are using Windows 2000, or if you have been directed to install the LAN driver from a specific location for Windows .NET.
To complete the LAN driver installation or update, perform the following steps:
1. Select Display a list of the known drivers for this device so that I can choose a specific driver and click Next.
2. Click Have Disk to open the Install From Disk dialog and specify the location of the driver:
v If you were directed to install the driver from a specific drive and folder, click Browse to specify the location, then click Open.
v Otherwise, click Browse to specify the location on the system drive (usually C:) of the driver that corresponds to the adapter that you are installing or updating. Use the following list to locate the folder that contains the driver for your specific hardware:
– \wsv\amd for hardware types 2723 and 2838 – \wsv\ibm for hardware types 2724 and 2744 – \wsv\alt for hardware types 2743 and 2760 – \wsv\itl for hardware types 2892, 5700, and 5701 – \wsv for Virtual Ethernet
3. Click OK.
4. In the Update Device Driver Wizard dialog, if the appropriate driver is not already highlighted, select it from the list, then click Next.
5. Click Next again.
6. If there is a Ret Code 22 when the Update Driver procedure completes, the adapter may be disabled.
To enable the adapter in this case, in the Device Manager window, right-click the disabled adapter and select Enable.
7. If you want to install or update more adapters, “Select the adapter to install or update” on page 156.
Note: If Windows indicates that a restart is needed after any driver update, defer the Windows restart until there are no more adapters to update.
8. If you changed the driver signing policy when you “Begin the LAN driver installation or update” on page 155, restore the original policy.
If you are using Windows .NET and you have not been directed to install the LAN driver from a specific location.
To complete the LAN driver installation or update, perform the following steps:
1. Select Search for a suitable driver for my device and click Next.
2. Click Next to show compatible hardware.
3. Deselect all Optional search locations, click Next, the click Next again.
4. If there is a Ret Code 22 when the Update Driver procedure completes, the adapter may be disabled.
To enable the adapter in this case, in the Device Manager window, right-click the disabled adapter and select Enable.
5. If you want to install or update more adapters, “Select the adapter to install or update” on page 156.
Note: If Windows indicates that a restart is needed after any driver update, defer the Windows restart until there are no more adapters to update.
6. If you changed the driver signing policy when you “Begin the LAN driver installation or update” on page 155, restore the original policy.