DOCUMENT ID: 1271-02

SYNOPSIS:    PC-X installation and debugging techniques

OS RELEASE:  any

PRODUCT:     SolarNet PC-X

KEYWORDS:    debugging pc-x problems


DESCRIPTION:

This product relies on Pcnfspro for network and system resources.  The
tools available will be used to diagnose problems.  Problems will be
addressed in several categories: local problems with host files, host
security, and X client start up.  Most of the host security and network
resources may be exercised by use of "PC side" functions. 

Network and Host resource problems:

The Solaris snoop function will allow tracing network transactions
between the "PC" and the Solaris host while using any of the functions. 

The ping function should be used to establish network viability and
operability.  Use first the IP address and then the host name.  If the
former works and the latter fails, make adjustments to the host file
using the configure function. 

The telnet function will help establish the ability to log into the
host.  Establish several telnet sessions (up to 10) to confirm the
Solaris host's ability to allocate necessary resources. 

Try using the login/logout function to test the host security in a
different manner. 

Try the ftp function to the host "ports" and other network resource
allocation. 

X client start up:

The PC-X icon should be selected and set as a background task.  All X
clients should use the xrun script for testing.  Be sure to specify the
display.  Both advanced features windows response and status should be
enabled. 

"Client startup" should be selected and several scripts and X clients
should be invoked on the host.  The functionally should build up to
capabilities required by X clients.  Some recommendations are to create
a simple file in /tmp; invoke an Xterminal with the full path name
 "/usr/openwin/bin/xterm";
try a simple client like xclock.

The tests may be executed using the "nohup" option, thus generating a
nohup.out file.  The benefit of nohup is the network connection remains
even after the startup command terminates.  Resulting errors are stored
in the user's home directory. 


DATE APPROVED: 03/26/95