Denied Connection - 12232
- Hi,
We have a web publishing rule that has worked fine for weeks/months. For the last few days the external application that regularly connects to our internal application via https POSTS (for which we have a web publising rule) I've noticed is getting a "Denied connection - 12232 The Server denied the specified URL" in our ISA. The URL in the error log seems to be correct (the domain name is correct as per the listener and public name tabs and the path match that in the path tab, all be the case does not match but it never has and I believe ISA does not bother about case sensitivy in the path).
Nothing has changed on our ISA server (connectivity verifiers to our back end servers all seem ok). The publishing rule does apply to a user in our AD that has a client certificate associated to it for when the source application connects to it - this cert hasn't expired.
Is there any other 'debugging' I can do or other ISA logs I can interrogate (the above errors are from the ISA monitoring section of ISA).
Also, when the denied connection is getting hit saying 'the server' denied the URL, is ISA 'the server' that is doing the denial or the destination server?
Many thanks
Answers
Hi,
· As this thread has been quiet for a while, we assume that the issue has been resolved. And I will change the status to "Marked as answer", please feel free to post here if you have any update.
Regards,
Nick Gu - MSFT- Marked As Answer byNick Gu - MSFTMSFT, ModeratorWednesday, October 21, 2009 10:02 AM
All Replies
Hi,
Thank you for your post.
Before going any further, I ‘d like to know more things:
1.Would you please look into the ISA web proxy logs? Tell us detailed error in the logs.
2.How do you configure the publish rule and listener?
3.What kind of client authentication method you have set in listener?
Regards,
What version of ISA Server are you running? If you have ISA 2006 SP1 it adds a "test rule" feature on the publishing rule. What is the result of that? Have you checked your IIS logs on the published server to see if there are any errors when that username tries to connect? That will give you a good indication of whether the traffic is getting to the published server.
Hi,
· As this thread has been quiet for a while, we assume that the issue has been resolved. And I will change the status to "Marked as answer", please feel free to post here if you have any update.
Regards,
Nick Gu - MSFT- Marked As Answer byNick Gu - MSFTMSFT, ModeratorWednesday, October 21, 2009 10:02 AM
