Welcome to ISAserver.org

Web Publishing w/ Secondary Ports

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> Web Publishing w/ Secondary Ports

Page: [1]

Message

<< Older Topic Newer Topic >>

Web Publishing w/ Secondary Ports - 30.Aug.2005 4:58:00 PM

doppleclutch

Posts: 5
Joined: 4.Feb.2005
Status: offline

Hi All:

I have a scenario that will spin your collective brains. Let's say we have the following:

ISAServer
WebAppServer1
WebAppServer2

I have only 1 public IP address, and WebAppServer1 and WebAppServer2 are both behind the ISAServer.

I want publish both WebServer1 and WebServer2 to clients across the Internet. Sounds simple enough. Here's the twist: both WebServer1 and WebServer2 uses secondary connections after the inital connection to port 80, say ports 6666-6669. The user can connect to WebServer1 and WebSever2 directly, but as they navigate through the app, the links will call on both webservers at the nonstandard ports 6666-6669. I thougth it was going to be somewhat straightforward, unfortunately, there doesn't seem to be any easy way to redirect ports other 80, 443, or 21.

Should I be going with Server Publishing instead? Can ISA handle Web Publishing outside the standard ports, or am I barking up the wrong tree?

Though it shouldn't make a difference technically, the ISAServer in question is running on SBS and is currently publishing Remote Web Workplace.

Thanks in advance for any hints and tips.

Post #: 1

Featured Links*

RE: Web Publishing w/ Secondary Ports - 31.Aug.2005 9:03:00 AM

isawader

Posts: 420
Joined: 27.Apr.2005
Status: offline

Publish TCP ports 6666 to 6669 on ISA and forward the secondary connections to the webserver.

I don't think webproxy service handles secondary connections. You can redirect the primary connection to other ports.

[ August 31, 2005, 09:03 AM: Message edited by: ISAwader ]

(in reply to doppleclutch)

Post #: 2

RE: Web Publishing w/ Secondary Ports - 31.Aug.2005 11:13:00 AM

doppleclutch

Posts: 5
Joined: 4.Feb.2005
Status: offline

Hmmm....so you're saying I should use Web Publishing to publish port 80 for WebAppServer1 and WebAppServer2, AND use Server Publishing to publish ports 6666-6669 for WebAppServer1 and WebAppServer2?

Sounds like it makes too much sense not to work. I'll give it a go and see what happens.

Thanks!

(in reply to doppleclutch)

Post #: 3

RE: Web Publishing w/ Secondary Ports - 31.Aug.2005 11:26:00 AM

doppleclutch

Posts: 5
Joined: 4.Feb.2005
Status: offline

Spoke too soon. Sever Publishing does not parse or forward host headers. Because BOTH WebAppServer1 and WebAppServer2 uses the same port range of 6666-6669, Server Publishing cannot distinguish between the two. I'll try publishing only one of the two WebAppServers to see if I can get halfway there.

(in reply to doppleclutch)

Post #: 4