TCP/IP Direct Connect

If TCP/IP Direct Connect is configured with a link type of HSAS or MPCPTP, please refer to the section titled “Troubleshooting” in the “ MPC+ for Windows NT Installation Guide”.

In Windows 2000 the easiest way to tell if TCP/IP Direct Connect has failed to activate is to look at the system’s console(Figure 6-4). Since TCP/IP Direct Connect is seen as a LAN connection by Windows 2000, a disconnect icon will display if TCP/IP Direct Connect is not active.

Figure 6-4. Windows 2000 Console

If TCP/IP Direct Connect fails to activate using a Channel-to-Channel (CTC) link type, here are some suggestions of things to look at:

1.Verify that the Mainframe IP address specified in the TCP/IP Direct Connect Properties screen (Figure 6-5) matches the IP address assigned as the Home address in the TCP/IP Profile on the mainframe (Figure 6-6).

Troubleshooting 51

Page 57
Image 57
Multi-Tech Systems 40-01459-D0-001 manual TCP/IP Direct Connect, Windows 2000 Console