Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have an internal web app built on some custom Java stuff. The app listens on port 8080, but also uses IIS on port 80 to get user authentication.

Opening the site in a browser produces HTTP GETs to both ports/urls.

Is a case like this possible to publish with TMG?

share|improve this question
This should simply be a case of publishing both ports via the usual publishing routines for Forefront TMG. You'll need to create a second listener for one of the web apps/ports (and you may prefer to do that within a second firewall rule) but that should be about it. – RobM Nov 14 '12 at 12:39

Yup, probably (sight unseen, but it's probably fiddleable to get it working).

Create two Web Publishing listeners, one for each port.

Create a rule which uses the first listener to publish the website, and check that much works.

If it does, (I think you can probably just) copy and paste that rule, then:

  • change the listener over to the other one, and
  • change the target publishing port over

And you should be good to go.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.