Re: Server publishing of HTTP
- From: "ZVR" <nospamever@xxxxxx>
- Date: Sat, 10 Sep 2005 07:52:34 -0400
No. You can use either server publishing on port 80 or web publishing. The
moment you start using server publishing on port 80, you won't be able to
use web publishing anymore. That is because there can be only one listener
at port 80 on the external IP address of your ISA server. This is common
networking knowledge - you cannot have two services running at the same IP
address on the same port in the same time.
So if you start using server publishing on port 80 you lose the ability to
use web publishing on port 80 AT ALL because the web proxy service won't be
able to create its listener on port 80.
I don't understand why your server publishing rules on different ports (80
and 1081) don't work though, most likely you have a different problem there.
Last but not least you can use combinations of server- and web-publishing
rules as long as they are not using the same port (see above). For example
you could continue to use server publishing for port 80 and create a web
publishing rule for port 1081 (in that case you will need to change the web
listener to port 1081 as well).
One suggestion for your OWA publishing problem: is the OWA server using the
internal address of your ISA machine as its default gateway? That can be one
reason why the server publishing on port 1081 doesn't work.
And a final suggestion: you should consider upgrading to ISA2004 if your
licensing permits - for example if you are a SA (software assurance)
customer. There are many new features in ISA that help with server and web
publishing scenarios.
Virgil
"News Microsoft" <dabella@xxxxxxxxxxxxxxx> wrote in message
news:%23GsMOcbtFHA.664@xxxxxxxxxxxxxxxxxxxxxxx
> That makes sense to me.
> The problem is we create 2 different custom protocols, one in the :80 and
> the other in :1081
>
> Could it be that web publishing rules are bodering with this config? I
> mean, i disable the 2 web publishing rules and enable the new 2 server
> publishing rules and neither work.
> But, in my previous config, i had the owa publishing rule and the iis
> server publishing rule enabled. In this situation i was able to send port
> 80 traffic to the iis (but, ofcourse, the owa rule doesnt work because it
> was pointing to the same port (80).
>
> Perhaps i need a combination of server and web rules? hm, doesnt make
> sense...but...
>
> What u think?
>
> Daniel.-
>
>
>
> "ZVR" <nospamever@xxxxxx> escribió en el mensaje
> news:yNedneelm4ruK7zeRVn-vQ@xxxxxxxxxxxxx
>> OK, in this case you should not have any problem. Of course you need to
>> define another "custom" protocol, you can name it for example HTTP
>> Server[1081], with direction inbound, on port 1081 TCP. And use this one
>> in the server publishing rule.
>>
>> You are probably trying to use the same HTTP Server protocol as last
>> time, but it won't work because it does not have the proper port
>> definition and in fact will conflict with the existing rule so that is
>> why both rules don't work.
>>
>> Rule of thumb with ISA 2000 is that you have to create a new, custom
>> "inbound" protocol for each server listening on a "non-standard" port -
>> like 1081 in your case.
>>
>> Virgil
>>
>>
>>
>>
>> "News Microsoft" <dabella@xxxxxxxxxxxxxxx> wrote in message
>> news:uHMa1cVtFHA.3932@xxxxxxxxxxxxxxxxxxxxxxx
>>> Yes, the internal owa was changed in IIS to listen on port 1081.
>>>
>>>
>>> "ZVR" <nospamever@xxxxxx> wrote in message
>>> news:6_GdnXSxdeMFMrzeRVn-2A@xxxxxxxxxxxxx
>>>> On what port is your internal OWA server listening? I understand that
>>>> the external port should be 1081, in other words the users connect to
>>>> the OWA server from outside with something like
>>>> http://servername.domain.com:1081/exchange, but is the internal web
>>>> server configured to listen on the same port (1081)? This is very
>>>> important because ISA2000 does not have the capability to redirect
>>>> traffic to a different internal port than the external listener's port
>>>> (this capability is present in ISA2004 by the way).
>>>>
>>>> Virgil
>>>>
>>>>
>>>>
>>>>
>>>> "Microsoft News" <dabella@xxxxxxxxxxxxxxx> wrote in message
>>>> news:%23vx1UcNtFHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> Hi guys,
>>>>> On Sep2 i post a thread named "Original IP address to a web server..."
>>>>> that was replyed by Virgil.
>>>>> Virgil, thanks, i disable the web publishing rule, config the server
>>>>> rule with the 80 incoming definition and all works fine.
>>>>>
>>>>> BUT, now the scenario is a little more complex. In addition to this
>>>>> webserver, now they tell us they have OWA in another internal server
>>>>> and they need to redirect owa traffic there.
>>>>> All was working fine till we create a second server publishing rule
>>>>> (this one in port 1081) that redirect the incoming traffic from port
>>>>> 1081 to the 2nd web server (the Exchange/OWA server). When we enable
>>>>> this rule neither rules work (the first one stop working). So, my
>>>>> guess is ISA is having some trouble when i enable 2 rules that work
>>>>> with the same kind of protocol (this time http) regardless of the
>>>>> different ports used.
>>>>>
>>>>> Which will be the solution to redirect via server publishing traffic
>>>>> to 2 different servers?
>>>>> We are speaking about ISA 2000.
>>>>>
>>>>> Thanks for your help,
>>>>>
>>>>> Daniel.-
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
.
- Follow-Ups:
- Re: Server publishing of HTTP
- From: News Microsoft
- Re: Server publishing of HTTP
- References:
- Server publishing of HTTP
- From: Microsoft News
- Re: Server publishing of HTTP
- From: ZVR
- Re: Server publishing of HTTP
- From: News Microsoft
- Re: Server publishing of HTTP
- From: ZVR
- Re: Server publishing of HTTP
- From: News Microsoft
- Server publishing of HTTP
- Prev by Date: Re: Google Talk !!!
- Next by Date: Re: publishing windows media server
- Previous by thread: Re: Server publishing of HTTP
- Next by thread: Re: Server publishing of HTTP
- Index(es):
Relevant Pages
|
