AnsweredAssumed Answered

how to access self-service interface using public IP address

Question asked by Xiaoli Ding on Dec 20, 2016
Latest reply on Feb 15, 2017 by Jay Guillette

We have a RSA SecurID 8.2 deployed on virtual machine. During installation, host name for internal access and private IP address are used for this server. But later, the client wants to allow end user to access the self-service console from Internet. And to do that, host name for external access and public IP address will be used. They don't plan to configure NAT for this situation. They only open the firewall to allow access to the server via public IP address. But the server was initially configured with private IP and internal host name, so it does not respond to the external access to the self-service console (via port 7004). What we should do about this situation? Please suggest, thanks.


And below is what the client said:


"we are not doing a NAT on the firewall. We are expecting the 169.x.x.x address (public) to be accessible and simply allowing the traffic through the firewall. The 10.x.x.x address (private, server was installed with this IP) should not be in play for the publicly accessible self service tool."