Hi, Example info ------------ EXT interface: ext.domain.com PSN interface: psn.domain.com PRO interface: pro.domain.com
server (PSN) server.domain.com external client extclient.domain.com protected client proclient.domain.com Here is the situation. When I connect from extclient.domain.com to server.domain.com, my originating hostname (FQDN) is displayed correctly as extclient.domain.com, as verified by typing "last -3 username". However, when I connect from proclient.domain.com to server.domain.com, my originating hostname is changed to psn.domain.com (since it comes thru the PSN gateway). We have some applications that use the originating hostname (FQDN) to determine the client's access privileges. However, all users are now listed as orginating from psn.domain.com rather than their true client hostname. Is there any way stop Gnatbox from overwriting the originating hostname with the PSN's interface hostname? Is this a DNS problem? This is driving me insane. I believe the problem used to occur when connecting from EXT to PSN. However, it's only happening now when I connect from PRO to PSN. CORRECTION: The first line in the previous paragraph is errant. This issue still exists when going from PRO to EXT, because the hostname is being changed to the EXT interface's address (ext.domain.com). Obviously, the Gnatbox can't give away the internal address. With Static Address mapping, I'm able to get around this for specific servers on the PSN that have IP Aliases setup. Any help would be greatly appreciated. Lowell [EMAIL PROTECTED]
