Applying changes in RAS console makes DMZ gateways "Not Verified"

0 users found this article helpful


After doing any changes in RAS Console and pressing Apply, Forwarding Gateways located in DMZ are going not verified state and stop functioning.


Due to performance mechanism utilized by Gateway component it is constantly trying to connect to Publishing Agent server. Since Gateway is located in DMZ it fails to establish successful connection to Publishing Agent located within internal network.


Client Management feature is not supported for Gateways configured in forwarding mode.

Untick Client Manager Port option on the forwarding Gateway.


Was this article helpful?

Tell us how we can improve it.