Status remains Connecting

These are some solutions to problems that prevent the local console from connecting to the server or prevent the remote console from connecting to a local console due to incorrect hardware or software configurations.

Try these possible solutions:

• Verify that the PC resources are free of address or interrupt request (IRQ) conflicts. Operations Console uses addresses in the range of 192.168.0.0 to 192.168.0.255. If you run any software that makes your PC SOCKS-enabled, check your SOCKS configuration and make sure that the entry is:
  Direct 192.168.0.0 255.255.255.0

  Note: Use the Operations Console properties window to change the IP base address from 192.168.0.2. For example, you can use 192.168.1.2.

  A SOCKS-enabled PC accesses the Internet through a firewall, such as Microsoft^® Proxy Client, Hummingbird^® SOCKS Client, or others.

• For a remote console connecting to the local console, verify that the server name and the local console name are correct.
• For a local console on a network (LAN) configuration and you are using Ethernet for your network, you can use a crossover cable. This isolates the PC and server from any potential problems on your network that might interfere with correct operations.
  Note: A crossover cable is a standard network cable but has the transmit and receive signal wires reversed. This essentially allows each end to act as if a hub, switch, or router is between them.