DPA user interface will not launch with IP but works with localhost
Summary: DPA UI not launching with IP but works with localhost
Symptoms
Unable to connect to the DPA UI when attempting to launch from the DPA Application host itself using the following URLs:
https://<DPA Application IP>:9002
http://<DPA Application IP>:9004
https://<DPA Application hostname>:9002
http://<DPA Application hostname>:9004
Telnet to the following ports failed as well:
telnet <DPA Application IP> 9002
telnet <DPA Application IP> 9004
The following error was logged in the Windows event log:
"TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint.
This error typically occurs when outgoing connections are opened and closed at a high rate. This causes all available local ports to be used. It also forces TCP/IP to reuse a local port for an outgoing connection.
To minimize the risk of data corruption, TCP/IP requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint."
The DPA UI could be opened successfully and telnet when localhost was used instead of the hostname or IP address:
For Example, all these were successful:
https://localhost:9002
http://localhost:9004
telnet localhost 9002
telnet localhost 9004
However, not being able to use the DPA Application IP in the URL would prohibit launching the DPA UI remotely and keep DPA Agents from communicating with the DPA Application server.