Re: ISA 2006 - Request appear to come from the original client
- From: "Phillip Windell" <philwindell@xxxxxxxxxxx>
- Date: Fri, 20 Jul 2007 09:54:40 -0500
"johnny_mango" <johnnymango@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:090BAAE4-35EA-403E-993B-FB413F05E311@xxxxxxxxxxxxxxxx
I have the same problem with SharePoint publishing, the SharePoint server
being in the internal network, without having the ISA as its default
gateway.
I have often heard that the server being published should have be
configured
as a secureNAT client, with its default gateway supposedly being the
router
nearest to it, and this router having the ISA as its default route (as per
the network within a network scenario.)
That would be correct in a permantent setup if that agreed with your LAN's
routing scheme,...but if you only want a "pilot" (test) situation you can
set the Rule so that "Request appeare to come from the ISA". As long as the
published server knows how to get to the ISA's internal Nic it won't require
any other special setup.
In our case I always use "Request appeare to come from the ISA" becuase our
ISA is never the Default Gateway of anything (we obviously have no SecureNAT
Clients either).
Therefore, my question would be, if I am staging a pilot, and do not wish
to
change the default route of the published server´s nearest router, what
should be my best approach? surely I would run into routing problems if I
just configured the default gateway of the published server as the ISA
server
internal interface, given it is on another segment....
For the record, I receive the 12028 error with the publishing rule being
as
"original client" and the 12202 error upon changing it to requests appear
to
come from ISA computer. I can access the page just fine directly from the
ISA
Server. I am using basic authentication, without forms.
What are you testing "from"? The Publishing only applies to external
Clients. Internal users don't use the Publishing,...they go directly to the
Sharepoint site independently of ISA. This typically requires Split-DNS.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html
Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------
.
- Follow-Ups:
- Re: ISA 2006 - Request appear to come from the original client
- From: johnny_mango
- Re: ISA 2006 - Request appear to come from the original client
- References:
- Re: ISA 2006 - Request appear to come from the original client
- From: McGee . Steven
- Re: ISA 2006 - Request appear to come from the original client
- From: Jim Harrison \(ISA SE\)
- Re: ISA 2006 - Request appear to come from the original client
- From: McGee . Steven
- Re: ISA 2006 - Request appear to come from the original client
- From: Jim Harrison \(ISA SE\)
- Re: ISA 2006 - Request appear to come from the original client
- From: johnny_mango
- Re: ISA 2006 - Request appear to come from the original client
- Prev by Date: Publishing ftp server
- Next by Date: Re: Publishing ftp server
- Previous by thread: Re: ISA 2006 - Request appear to come from the original client
- Next by thread: Re: ISA 2006 - Request appear to come from the original client
- Index(es):
Relevant Pages
|