Troubleshooting

 

ping IP address

 

If no ping reply is received, the Sender is

 

unreachable or is not running.

 

If a ping reply is received, the Sender software

 

may not be running on the remote computer.

 

2. A Sender is not running on the system you are

 

attempting to reach. Verify that the Sender is

 

running on the system.

 

3. The Sender system is not started or connected to

 

the network. You could try a basic connectivity

 

test, such as ping.

 

4. The network is not configured correctly. For

 

example, DNS may not have resolved the name

 

of the Sender system correctly or your /etc/hosts

 

file, if using UNIX, does not have the proper

 

ipaddress mapped to the hostname. Try entering

 

the ipaddress of the Sender.

 

5. The Sender is started and listening on a different

 

network interface than the one you are

 

attempting to reach. This could be the case if the

 

Sender system has multiple NICs, it is a multi-

 

homed system, or there is a virtual ethernet

 

device installed. If this is true you may need to

 

specify the binding order of hostnames to

 

ipaddress.

 

6. If you are attempting to connect to a UNIX

 

system you may have entered an incorrect

 

screen number.

 

7. If the Sender system has changed networks and

 

been assigned a new ipaddress after the Sender

 

was started then you'll need to re-start the

 

Sender service/daemon.

 

 

Authentication

The Remote Graphics Software Sender has refused to

failed!

allow a connection. Possible reasons include the

 

following:

 

1. The authentication credentials that you

 

entered, such as domain name, user name

 

and password, are not valid or recognized by

 

the Sender system.

 

2. The Sender's authentication is not configured

 

appropriately. Please consult the User's

 

manual and README.txt for the latest

 

directions and issues with respect to

 

configuring authentication.

 

 

139