Troubleshooting Incoming Connections

Incoming dedicated connections consist of terminals or PCs directly connected or dialed into the DTC server. They use the Telnet Port Identification feature, and are supported only for connections originating from DTC-attached devices to HP 9000 systems.

One common problem occurs whenever the user attempts to log into a system and is assigned an unexpected device file. Use the following list of tasks to verify that the user's port is correctly configured in the dp file.

Check that the entry in the dp file contains the proper configuration. Remember that entries for incoming connections do not require the specification of a port configuration file (pcf).
Make sure to execute the dpp utility after every update of the dp file. Dpp creates a binary file which is used by telnetd to assign the proper device files to incoming connections.
Check the version of the DTC Manager which manages DTC server ports. If the DTC Manager is PC-based, you should have version A.14.00 or later. If it is the host-based DTC Manager, you should have version A.03.00 or later.
Check the version of telnetd on the HP 9000 using the HP-UX what command.
what /usr/lbin/telnetd
On the $Header line display by the what command, the telnetd version should be 1.22.110.10 or later.
$Header: telnetd.c, v 1.22.110.10
Make sure that a Telnet connection can succeed.
telnet <host IP addr>

Remember that the assignment of dedicated ptys on the HP 9000 depends upon the successful exchange of DTC port information by the DTC Telnet subsystem and the Telnet daemon on the HP 9000 at connection establishment time. Only the correct versions of software are capable of exchanging this information.

If You Have to Call Hewlett-Packard

If your troubleshooting indicates that a serious problem has arisen and you need to call your Hewlett-Packard support engineer, please ask your system administrator to help you collect as many of the following items as possible. This list of items will greatly assist the support engineer in isolating and resolving DDFA problems.

A description of the problem and the conditions under which it occurred. For example, did it occur on a previous release of DDFA or HP-UX, can it be replicated, does the same problem occur with a MUX connection?
The following data taken while the problem is occurring:
1. a log file of an ocdebug run (/var/adm/ocd<pid>)
2. the syslog.log file from /var/adm/syslog
3. a nettl trace (see man pages for how to use nettl)
4. printout of spooler information by typing lpstat -t
5. printout of process information by typing ps -ef
6. printout of network status information from netstat -n
The complete DDFA data path configuration:
1. printout of the /etc/lp/interface file associated with the offending printer
2. listing of the dp files and pcf files used
3. version number of HP-UX by typing uname -a
4. hardware platform, such as HP 9000 Series 800 or 700, and the model number
5. version of DDFA used by typing what
6. list of installed DDFA patches from typing what
7. DTC Manager version. Refer to the appropriate DTC Manager manual for details.
8. map of your DTC or non-DTC configuration down to the port level
9. type of device to which you wish to send outgoing or transmit incoming data
10. map of your network between the system and the DTC or non-DTC terminal server
11. Non-DTC server information, including manufacturer, hardware and software versions and server configuration settings. Refer to the manufacturer's product documentation.

Troubleshooting Incoming Connections

Technical documentation

» Table of Contents

» Index

If You Have to Call Hewlett-Packard