Problem Solving

This topic describes some of the more common operating problems and suggests how they might be overcome.

Error Messages

If you receive a message that is not listed below, contact your network administrator.

Message - Authoritative Answer: Host not found

An IP address could not be found for the specified host.

  • The host you require does not exist on the LAN. Check that the host name is correct.
  • Your Domain Name Server is not responding. Contact your network administrator.
  • You are not connected to the LAN, or the LAN is inoperative. Contact your network administrator.
Message - Cannot find own IP address

Your TCP/IP software has not been set up correctly. Refer to your TCP/IP manuals.

Message - Cannot find WINSNI.DLL
Message - Unable to load CCIDDA.DLL error 2

If these two messages appear, you have not installed the PCSNI software.

Message - Cannot resolve host name
  • You are attempting to connect via TCP/IP to a host that does not support it. Check that you are using the correct protocol (refer to Configuration for details).
  • The host you require does not exist on the LAN. Check that the host name is correct.
  • The host you require is not responding. Contact your network administrator.
  • Your Domain Name Server is not responding. Contact your network administrator.
  • You are not connected to the LAN, or the LAN is inoperative. Contact your network administrator.
Message - Connection refused

The host has responded to your connection request, but has refused the connection for some reason.

  • Check that you are using the correct port number (normally port 23 for Telnet or port 1203 for DDATCP).
  • If the port number is correct, contact your network administrator.
Message - Connection timed out

The host you require is not responding. Contact your network administrator.

Message - Error in Route definition

The configuraton file cannot be found:

  • Check that your configuration file is called WINSNI.INI.
  • Check that your configuration file is in your Windows folder.
  • If necessary, create a configuration file.
Message - File Error: Cannot find CCITCP.DLL
Message - Unable to load CCITCP.DLL error 2

You have upgraded from version 2.0 of the SNI, and are attempting to use the RealLink Telnet over Winsock communications protocol. Change the protocol for that connection to LAN and create an entry for the host concerned in your SNI configuration file, specifying Telnet as the protocol.

Note

For information about how to set up your RealLink configuration with RealLink 4.x for Windows, refer to the RFW Help.

Message - File Error: Cannot find WINSOCK DLL
Message - Cannot load the winsock.dll library.

If these two messages appear, you are attempting to connect via TCP/IP, but have not installed the TCP/IP network software.

Message - Protocol specified is unknown. Must be TELNET, DDATCP, DDAOSI or ACIOSI

There is an error in your configuration file. Refer to Configuration for details of valid configuration file entries.

Message - Qualifier Overflow

You are using the DDATCP protocol to connect to the Telnet port. Check that you are using the correct protocol and port number (refer to Configuration for details).

Message - The virtual circuit was reset by the remote side

You are using a network replug and your destination host (specified in the Dbase entry) is not recognised by the replug host. Check that the host name you have specified is the name of an entry in the replug host's ROUTE-FILE.

Message - There is no useable WinSock

You are using an unsupported version of WinSock. Check that you have WinSock version 1.1 or later.

Message - Transport Error: Receive Failure

You are using a client server connection and the host has not responded to your connection request. Check that your user-id, password, account name and account password are correct.

Other Problems

No login prompt appears

You are using the Telnet protocol to connect to the DDATCP port. Check that you are using the correct protocol and port number (refer to Configuration for details).

Inconsistent PLID format

When using a telnet connection that uses location-based security, a PLID with the format UNIX-decimalAddress-Console can sometimes be generated instead of INET-DecimalAddress-Port.

Add the following entry to the [OPTIONS] section of your WINSNI.INI file (Windows folder):

CheckTSC=0