Welcome to ISAserver.org

Web Publishing generates 12202 error

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> Web Publishing generates 12202 error

Page: [1]

Message

<< Older Topic Newer Topic >>

Web Publishing generates 12202 error - 26.Oct.2004 8:35:00 PM

michaelghoran

Posts: 2
Joined: 25.Oct.2004
Status: offline

Hello,

IÆm in the midst of an ISA 2004 deployment, and I am having some difficultly with Web Publishing. Here is an outline of my design I have three NICÆs but itÆs actually an edge design with two separate internal networks ~

(internet)
|
207.170.y.239
207.170.y.240
207.170.y.241
207.170.y.242
207.170.y.243
External ISA interface
|
ISA 2004 Standard running on 2003 Enterprise -- 2nd private network 131.107.y.z |
Private Network
10.10.y.4
|
Outbound Internet Access
Web Published Servers
10.10.y.10
10.10.y.12
10.10.y.27

I successfully published my first IIS 6 site from the Private network using the following settingsà..

Name û partner.mycomany.com
Action - allow
From û Anywhere
To û ru1.mycompany.local (internal DNS resolves to 10.10.y.27)
Forward original host headers û True
Requests appear to come from û ISA server
This rule applies to the following protocols û HTTP
Listener û 207.170.y.239, HTTP port 80, SSL disabled, authentication is integrated only
Public name û partner.mycompany.com
Path û <same as internal> /*
Bridging û redirect HTTP to port 80, redirect SSL to port 443, both enabled, but no certificate currently specified
Users û All users
Schedule û Always
Link Translation û replace absolute links in web pages set to False

I proceeded with web publishing another site with all the same settings except the ôListenerö (207.170.y.240), and the ôToö (go.mycompany.local) and the site would not come up, instead, I got the dreaded 12202 error, specifically 403 Forbidden - The server denies the specified Uniform Resource Locator (URL). Contact the server administrator. (12202)

We host our own external DNS zones. IÆm not attempting to publish by IP address, and the part of this site that presenting the symptom is not SSL enabled.

I started reading up on these message boards, and it seems that folks have addressed this problem in one of four ways
1. Set specific paths
2. Set a default document in IIS 6
3. DNS entry or routing table manipulation
4. Change the ôrequests appear to come fromö to client vs. ISA Server

So, I began working my way down this list. I have a third web site to publish, so I used it as a test. Its listener is 207.170.y.242 and it goes ôToö mail.mycompany.com (OWA). I once again used all the same settings, and initially got the 12202 error. I tried the first solution, i.e. I set the path page with three entries
/exchange/*
/exchweb/*
/public/*

And the problem went away! Woo-Hoo I cried, and set about building the go.mycompany.local Web Publishing Rule and used specific path entries instead of /*, and the 12202 error recurred. I remove the specific path entries from the publishing rule for mail.mycompany.com and added /* back and I canÆt get it to fail. So, IÆm no longer convinced that paths (by themselves) are the answer.

I will continue troubleshooting, but at this point I welcome any advise in clearing this 12202 error, I have a lot of other work in this deployment that is stacking up behind it.

Thanks very much,

Post #: 1

Featured Links*

RE: Web Publishing generates 12202 error - 27.Oct.2004 7:10:00 PM

michaelghoran

Posts: 2
Joined: 25.Oct.2004
Status: offline

The answer here is embarrassingly simple. In my write up I did not state ôfrom what networkö I was conducting my tests. I was testing from the internal 10. network behind the firewall, and my access rules did not include a "domain name set" for *.mycompany.com

I added the domain name set, and all tests work and all my web published sites come up just fine.

Why the first site I web published did not exhibit the 12202 symptom is interesting, but my project is back on track.

Thanks to all who post on these boards,

-Mike

(in reply to michaelghoran)

Post #: 2