Check the hostname entry in /etc/sysconfig/networking/devices/ifcfg-eth0 and make sure it is set correctly for the proper hostname of the server as configured in the RHEL OS. Run the command "hostname" to see what the RHEL OS says the hostname is and confirm that it matches the same in that file. If the hostname command gives a different output than what the hostname field shows in that file, then check the RHEL OS setting for the domain name of the DNS search domain and make sure it shows the correct domain name. IE: The hostname command shows this "salgwserver.customernetwork.custnet2.com" and the actual hostname in the /etc/sysconfig/networking/devices/ifcfg-eth0 file shows as "salgwserver.customernetwork.com". If this is the case, correct the DNS search domain name as it is more than likely "customernetwork.custnet2.com" and change it to "customernetwork.com" to match the actual domain name that the SAL Gateway is in. Also, log into the GUI interface of the SAL Gateway and make sure that the hostname seen in the upper right hand corner also matches the correct hostname for the server and then verify that the hostname on the SALGW managed element also matches the correct one. Do this by logging into the SALGW GUI and go under the "Administration" section then "Gateway Configuration" and select "Edit" to make changes then "Apply" to save them and go to "Apply configuration changes" at the bottom of the "Administration" section and click "Apply" then "OK". This will restart the SALGW services to apply the changes to the application. Then check remote access to the system and verify the Policy Server is in use by verifying you see "Asking permission" on your remote session.
