Welcome to ISAserver.org

Can this be done?

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 General] >> Web Publishing >> Can this be done?

Page: [1]

Message

<< Older Topic Newer Topic >>

Can this be done? - 2.Apr.2002 11:56:00 PM

ZexDelSol

Posts: 2
Joined: 2.Apr.2002
From: Orlando, FL
Status: offline

I want to be able to publish multiple sites, using multiple IP's, on multiple ports using ISA server on one server?

If so... how?, If not... What product can?

Any help would be greatly appreciated. Thanks.

[ April 03, 2002, 01:06 AM: Message edited by: ZexDelSol ]

Post #: 1

Featured Links*

RE: Can this be done? - 3.Apr.2002 6:17:00 PM

Robert

Posts: 43
Joined: 21.Aug.2001
From: Harrisburg, PA
Status: offline

Why do you want to use multiple ports? What you want to do seems doable using the same port for all IPs

(in reply to ZexDelSol)

Post #: 2

RE: Can this be done? - 3.Apr.2002 11:05:00 PM

ZexDelSol

Posts: 2
Joined: 2.Apr.2002
From: Orlando, FL
Status: offline

quote:
Originally posted by Robert:
Why do you want to use multiple ports? What you want to do seems doable using the same port for all IPs

I need it to be on seperate ports because the websites that were made by the client have the ports hard coded all throughout their code. Changing the code is not really an option.

(in reply to ZexDelSol)

Post #: 3

RE: Can this be done? - 11.Apr.2002 5:55:00 AM

ISAGuy

Posts: 4
Joined: 11.Apr.2002
Status: offline

I'd suggest using web publishing to publish everything of theirs that is on port 80, then use server publishing rules to redirect the other ports to the internal web server. In adition, I ber you could redirect anything incoming on a high external port to port 80, and then the incoming web requests listener could pick the :xxxxx (where xxxxx is the port number) out or something unique in the header, and use that to identify requests that have been redirected from the higher port. After they are identified, it could redirect them to an internal webserver with a header like <portnumber>.server.com.

(in reply to ZexDelSol)

Post #: 4