Remote Control (NCS) Connections

This section discusses various symptoms of common problems related to remote control (NASI^TM Connection Services [NCS]) connections.

You cannot see ports under Win2NCS.

Not being able to see a list of NCS ports displayed in Win2NCS often indicates a security problem. If you enter an incorrect username or context in the Set Security window of the Win2NCS Mapping Utility, you are prevented from seeing NCS resources in the Map Communication Ports window. Verify that you have the proper context entered and that you have the proper rights to use the CONNECT Object.

Users dialing in with a remote control application have trouble connecting.

Use usernames and passwords that contain only alphanumeric characters without spaces. Enter the complete NDS name and remote client password when prompted. Also, consider reducing the baud rate.

Another troubleshooting tool is a null modem cable. Use a null modem cable for a direct connection to the remote access software to eliminate modem incompatibilities.

No NCS service names are displayed when a user dials in to remote access.

If the remote control software has just been started, wait a few minutes and retry the request. Service names might not have been broadcast to the network. Also, a user can only access sessions owned by the user or general sessions. Verify that such sessions have been brought up on the network.