
Failed connection attempt troubleshooting checklist (sender)
Use the following checklist to troubleshoot failed connection attempts from the sender side:
1. Verify the credentials for the user account you are trying to access from the receiver. The account
password cannot be blank.
2. Verify that RGS Sender has started on the sender (see RGS Sender overview on page 21 for more
information).
3. Verify that all tests pass on the Diagnostics panel of the RGS Sender Conguration tool.
4. If the sender is behind a rewall, verify that the rewall supports network address translation (NAT) and
port forwarding.
5. If you changed the network interface binding of RGS Sender from its default of listening to all network
interfaces, verify that the sender is listening on the correct network interface (see RGS Sender network
interface binding on page 66 for more information).
6. (Windows only)
Verify that the sender is not using Automatic Private IP Addressing (APIPA) by typing the following in a
command window:
netstat -n -a
If the IP address associated with the RGS Sender listening port (42966 by default) is private, APIPA is the
likely cause. For information about how to disable APIPA, go to http://support.microsoft.com/kb/
220874.
7. (Linux only)
Verify that the sender is not using an X desktop started on the command line. Outside connection
attempts might fail because of incomplete PAM session management and permissions for the console.
Login management should be handled by the display manager started by init run level 5.
NOTE: Make sure you log out of the sender before attempting an RGS connection again.
RGS Sender network interface binding
RGS Sender is set by default to listen to all network interfaces present on the sender. If this is undesirable, the
network interface binding can be manually recongured.
There are three methods to recongure RGS Sender network interface binding:
●
Disable the network interfaces that you do not want RGS Sender to listen to, and then restart the sender.
RGS Sender will then bind to the remaining enabled network interface. The disadvantage of this method
is that the other network interfaces will no longer be usable.
●
Manually congure the desired network interface to be the one listened to by RGS Sender. See
Reconguring network interface binding manually on page 67 for more information.
●
Use the RGS Sender Conguration tool to specify which network interface to listen to. See Reconguring
network interface binding using the RGS Sender Conguration tool on page 67 for more information.
If you enter a hostname instead of an IP address when establishing an RGS connection, it is possible that the
hostname will resolve to the IP address of an incorrect network interface. This could be caused by a number
of factors, including how your DHCP and DNS servers are congured.
66 Chapter 8 Performance optimization and troubleshooting
Kommentare zu diesen Handbüchern