You have a proxy in the environment that permits cross-communication between IPv4 and IPv6. With this proxy enabled, you notice that access through a remote console to Symantec Endpoint Protection Manager (SEPM) 14.2 does not launch when you expect it to.
Remote consoles include Java Remote Console, Web Console, and Reporting console access.
When you enable cross-communication between IPv4 and IPv6 with any proxy, the following support matrix applies:
|Networking of Symantec
Endpoint Protection Manager
|IPv4 and IPv6||IPv4||Access through all remote consoles|
|IPv4 and IPv6||IPv6||Access through Reporting console
No access through Java Remote Console and Web Console
|IPv4 only||IPv4||Access through all remote consoles|
|IPv4 only||IPv6||Access through Web Console and Reporting Console
No access through Java Remote Console
|IPv6 only||IPv4||Access through Reporting Console
No access through Java Remote console and Web Console
|IPv6 only||IPv6||Access through all remote consoles|
* The client computer used to access the remote console.
Note: The server on which the Symantec Endpoint Protection Manager is installed must have the IPv4 stack installed, even if it is disabled. See the system requirements for Symantec Endpoint Protection Manager, under “Other environmental requirements.”
netsh winhttp set proxy IPv4_address_of_proxy_server:proxy_port
netsh winhttp set proxy [IPv6_address_of_proxy_server]:proxy_port