Isa 2006 Error 14141
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeProductsLibraryLearnDownloadsSupportForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: ISA2006 - Problem Presents As Proxy Server Loop Forefront > Read Only - Forefront Edge Security - Installation, Upgrade, and Setup Question 0 Sign in to vote We are getting transitory error messages that indicate that a proxy server loop was detected. Problem is, we are using only one ISA server and all traffic into and out of the location is through this server. The following is a copy of one of the errors. When they appear, it is usually twenty or more error postings within a couple of minutes. Event Type: WarningEvent Source: Microsoft ISA Server Web ProxyEvent Category: NoneEvent ID: 14141Date: 7/25/2007Time: 11:12:21 AMUser: N/AComputer: MNOP2Description:ISA Server detected a proxy server loop. There may be a problem in the configuration of the ISA Server Web chaining policy. Alternatively, in Enterprise Edition, when CARP is enabled and there are intermittent interruptions of intra-array connectivity, array member A may forward a request to array member B according to the CARP algorithm, and array member B may forward the request to array member A in an endless loop. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. What else is observable but what is not showing up in the logs is that during this time that the ISA server is posting Event ID 14141 errors, HTTP traffic is not going through the ISA server. From a web browser, users get a page not found error. Going out to a command prompt, I can successfully ping external resources; trying to get to the same resource via a browser results in a page not found. There are three NIC in our configuration, two of which have gateways listed (the th
will cover how you can go about creating and editing custom error messages specific to your organization, from messages that are stored within ISA by default. These error messages are displayed when errors occur. I have found these messages to be very general and found them not to display comprehensive amounts of information. I have looked into ways of making the information more comprehensive and customized to suit your organization. To reduce helpdesk calls I have found this method to help enormously. Telling the user what he/she might be doing wrong by displaying a https://social.technet.microsoft.com/Forums/forefront/en-US/a22b3a76-423d-4548-a22c-e39e44489e1f/isa2006-problem-presents-as-proxy-server-loop?forum=Forefrontedgesetup custom error message with a picture normally gets his/her attention. Normally I also include the helpdesk phone number and email address. Once the user reads the custom message it helps them to understand where they have gone wrong and then what can be done rectify the problem them selves and continue browsing. Sometimes it becomes very difficult to http://www.isaserver.org/articles-tutorials/configuration-general/Custom_error_pages_within_ISA.html understand what the error message is trying to tell you, and so that is why microsoft has allowed you to be able to edit the default error messages, you can customize them in such a way that the error messages can point to your helpdesk or to specific tutorials on your intranet that will help you users in resolving the problem themselves. This time saving strategy has worked in many organizations. Try it! Questions users ask? 1. When I click a link it does not take me there. 2. I have typed in the URL that I visit everyday and am unable to get to it. 3. When I click refresh I am unable to get to the webpage I was on originally. 4. I keep getting an error that says that the domain name does not exist. 5. When going to a website that I visit frequently I get different error responses but mostly 403 errors. Answers to the top 5 questions. 1. The link may have been copied or sent to you incorrectly, look at the link and make sure it is not a java script link or a link to a webp
server pulls up an error page with the following message. Technical Information (for support personnel) * Error Code 12206: Proxy chain loop * Background: The gateway has detected a proxy chain loop. This condition might indicate a configuration problem on a proxy server. http://www.yqcomputer.com/145_9526_1.htm * Date: 9/22/2006 2:29:52 PM [GMT] * Server: isa2006.x.y.com * Source: Proxy Firewall Client is installed on the machine. If we set the 'Users' group to "All Users' in the rule we get the basic plain text block page with the correct URL denied error. The proxy error happens when we have "All Authenticated Users' in the rule. - Jeff Cohen Top Proxy Chain Loop Error by Pesach She » Tue, 26 Sep 2006 22:33:25 Hi Jeff, There is a description of a isa 2006 situation where this can occur in Troubleshooting Web Proxy Traffic in ISA Server 2004 ( http://www.yqcomputer.com/ ). In particular, you can get this error when you have a proxy application running on your ISA Server computer and/or Web chaining rules configured. HTH, Pesach Shelnitz [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. OR if you wish to include a script sample in your post please add "Use of included script samples are subject to the terms specified at http://www.yqcomputer.com/ Please isa 2006 error do not send e-mail directly to this alias. This alias is for newsgroup purposes only. Top Proxy Chain Loop Error by SmltIGluIE » Sat, 28 Apr 2007 00:56:00 Were running ISA 2000 on a Server 2000 machine. The last two nights, we have shut down our Exchange 2000 server for the night. The next morning, I've noticed that we do not have Internet access to the outside world. I have to stop and start the Firewall service on ISA to get the Internet back. When I looked at the event log, I see a lot of the following error msgs: Warning Microsfot Web proxy Error ID 14141 ISA Server detected a proxy chain loop. There is a problem with the configuration of the ISA server routing policy. Why would shutting down our Exchange server cause this to happen? Or is this just coincidental? Top 1. Proxy chain loop error in Event viewer 2. 12206 Proxy Chain Loop Error 3. Error 12206 Proxy Chain Loop in SBS Server 4. Error 12206 Proxy Chain Loop 5. Proxy chain loop 6. 12206 - proxy chain loop 7. Proxy chain loop bug in ISA SP1 8. isa server detected a proxy chain loop warning 9. Proxy chain loop... 10. 12206 - proxy chain loop 11. 12206 Proxy Chain Loop 12. 12206 - proxy chain loop 13. Proxy Chain Loop with EventID 14141 14. ISA 2004 EE and Proxy Chain Loop 15. ISA Server Proxy chain loop 3 post • Page:1 of 1 All times