I have reported your issue for internal review.
While we investigate, please check your active enforcement policies. It is possible that a policy in place may be blocking by Destination IP or that there are limitations on which services are allowed. Additionally, ensure that Putty is set to the default settings for SSH.
We have internally tested using Putty for SSH access and it is compatible in it’s standard configuration.
Double check your network interfaces on the Policy Server / Sensor, and on the machine you are trying to access from, as well as the route between.
If they are properly configured, try clearing your approved SSH source forms so they are empty and applying. Then reboot the policy server and re enter the approve IP’s + subnet. (ex: “192.168.1.0/24″)
If you continue to experience issues, please contact us through our slack community at genians.slack.com for troubleshooting support from our engineers and other users.