Content translations are temporarily unavailable due to site maintenance. We apologize for any inconvenience. Visit our blog to learn more.
11-01-2017 03:15 AM
Hi Guys,
I need some help dealing with CyberAck over VPN. The problem is that I created and established a VPN with a remote peer for CyberAck traffic. Service is Any but application is default. Traffic is allowed via the firewall but I get an error (tcp-rst-from-server) on both sides or server and client. Cyberack uses TCP ports 4118, 4119, 4120 which I custom created. This did not work so I set the service to any and application to default and still get the same error - tcp-rst-from-server.
But when I set the application to Any and service to Any, everything works fine. And this defeats my reason for a firewall in the first place. Monitoring the rule in action, I noticed that service is coming and going as 4120, 4118 etc and application is set to SSL. This is obviously not a default SSL so hence failing. I think what happens is this - https://10.10.10.25:4118.
Does anyone know how I can overcome this problem?
Any help will be much appreciated.
11-01-2017 09:32 AM
You'll need to create an application override policy to force that traffic to the application(s) you created. Here are the steps:
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
