tmg2010-publish_rdc_non_standard_port-1.png

 

 

  • Click “Publish non-Web server protocols

tmg2010-publish_rdc_non_standard_port-2.png

– click “next”

tmg2010-publish_rdc_non_standard_port-3.png

type IP address server on local network which you publish on non-standard port.

– click “next”

tmg2010-publish_rdc_non_standard_port-4.png

– click “New” !!! to create listener for our publish rule to listen on port 3390

tmg2010-publish_rdc_non_standard_port-5.png

– click “next”

tmg2010-publish_rdc_non_standard_port-6.png

Choose TCP protocol, Inbound direction and port 3390. Click OK.

– click “next”

tmg2010-publish_rdc_non_standard_port-7.png

we do not need secondary connection

– click “next” and “finish”

 

tmg2010-publish_rdc_non_standard_port-8.png

 our new protocol is on the list.

– click “Properties”

tmg2010-publish_rdc_non_standard_port-8a.png

associate traffic to standard protocol and click OK

– click Ports

tmg2010-publish_rdc_non_standard_port-8b.png

redirect traffic from port 3390 on firewall to port 3389 on server1.Click OK.

– click “next”

tmg2010-publish_rdc_non_standard_port-9.png

select network on which Forefront will listen for connections(by default on all ip on  external interface) but you can change it(see picture below).

tmg2010-publish_rdc_non_standard_port-10.png

– click “next”

tmg2010-publish_rdc_non_standard_port-11.png

– click “Finish”

– apply changes to firewall

tmg2010-publish_rdc_non_standard_port-12.png

  •  test connectivity

 

 dzbanek 2013-01-04