I Publish my Screen Connect server using a publishing rule in Microsoft ForeFront TMG. Everythign works as expected if I connect the server directly to the public IP address. When I am behind the firewall, however, everything works except for Unattended Build.

When I input the description and click on "Download for Windows (.MSI)" nothing happens. The Mac OSX (.pkg) works fine. Only the Windows link is not working.

I am guessing that the ForeFront TMG server is blocking the client from downloading .msi files. I have tried turning off all http filters in the gateway but it does not work. I need to be able to user ForeFront because I do the port forwarding based on the incoming host name, and Forefront allows me to do this. THis way I can have multiple web servers behind the firewall.

Does anybody know the correct configuration for FF TMG?

Is there anyway to vhange the name of the .msi to .zip or something that will allow it to go through and I'll rename it back in the Guest machine?

Thank you,

Mario

Hello Teejayuu,

The reason I needed a publishing rule was so that TMG could use the websites name in order to route the request to the correct server. I have SC working on port 80 and 443 to avoid having issues with client firewalls not allowing connections. What I did was a generic publishing rule forwarding port 80 and 443 to the screenconnect server. I then put this rule AFTER other websites publishing rules. This way I was able to make it work. Maybe TMG doesn't like .MSI files going over port 80 or something. This was the only way I could make it work.

Thanks again.