
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.
RGS Sender natively supports the following display managers:
●
GNOME Display Manager (GDM)
●
KDE Display Manager (KDM)
●
LightDM
If the sender system uses a dierent PAM-based display manager, you can try the following:
NOTE: This conguration might not work for some display managers.
a. Find the conguration les for the display manager in /etc/pam.d/.
b. Add the following line to the end of each le (create a backup of each le before modifying it):
session optional pam_rg.so
c. Restart the sender system.
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 72 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 72 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.
If the hostname resolves to the IP address of an incorrect network interface, do one of the following:
●
Enter the IP address that RGS Sender is bound to instead of the hostname when establishing an RGS
connection.
●
Recongure your DHCP and DNS servers so that the hostname resolves to the correct IP address.
●
Use the nslookup command to determine the IP address that the hostname resolves to, and then
follow the steps in Reconguring network interface binding manually on page 72 to set the
corresponding network interface to be listed rst in the list of connections.
Failed connection attempts 71
Comentários a estes Manuais