This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
Unable to access K2 sites with the following error:
"A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond %K2_SERVER_IP%:5555"
When accessing K2 users receive the following error:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond %K2_SERVER_IP%:5555
You can use the following troubleshooting steps:
- Confirm that the K2 service is up and running and there are no errors in the host server logs, and that it can be restarted without any issues.
- Confirm that the K2 server with K2 service has the default ports configuration and is listening on port 5555 (netstat -na | find "your_port").
- Verify if a connection is allowed through this port, for example, using telnet host port command - if this test fails it means you have connectivity/firewall problems.
- Check Windows Firewall Configuration and look if allow rules are in place for port 5555. If allow roles do exist yet the telnet connectivity test is still failing it can mean that there is some other firewall or security software installed on the K2 server takes precedence over the default Windows firewall and is not configured to allow required connections (e.g. Windows Firewall can be managed by McAfee software etc.)
- Personnel responsible for network security should ensure that all firewall rules required for K2 are in place.
A quick reference to the ports commonly used in a K2 implementation can be found in Firewall ports and K2 section of K2 Five Installation and Configuration Guide.