Remote control panel fails to start

 

If your remote control panel fails to start, verify these items.

• Verify that the cables are properly connected.

  Directly connected remote control panels are no longer supported.

• Verify that the resources of the PC 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

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

• If you are connecting via a network, another reason the remote control panel fails to start may be that either the user ID or service tools device ID being used does not have permission to use the remote control panel.

 

Parent topic:

Troubleshooting remote control panel and virtual control panel problems

 

Related reference

Installing an Operations Console cable