Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I am working with an administrator at my company. We recently added MS ISA 2006. I do not have access to the server, so my question is more theory based.

Is it possible to setup ISA to route HTTP traffic to the same physical server using both standard port 80 and nonstandard port, say 8989?

For example,

internally, the address


is pointed to by ISA externally as

But, we have not been able to route traffic to


successfully with ISA. Is this possible? If yes, do you have any tips for doing so that I can relay to the administrator?

share|improve this question
up vote 1 down vote accepted

Sounds like you have one Web Publishing rule already, for: /* -> myserver:80 /*

( is the Public Name) (The /* reflects a Paths entry of "everything")

You could easily change that to /* -> myserver:8989 /*

But now we're getting to what's probably the rub here - how are you disambiguating the exernal sites you want to publish?

You can only route one exernal namespace to one internal site at a time.

If, however, you wanted to do something like /app1/* -> myserver:8989 /* (or /app1/) / -> myserver:80 /*

You can (IIRC from years ago) - you just need to ensure your most specific rule is ordered first.

This will bounce requests for /app1/* to a different port internally (don't forget Link Translation in case of problems with internally-built URLs here), and allow all other requests to hit the other website.

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.