The problem was that external clients were failing to access an internal Web server published on ISA 2004 server with HTTP 500 internal error. On an SBS server that was five years since it was installed with the option to auto renew certificates, it renewed the publishing cert (I think), though another admin was logged rerun the ICW and issued a > new local certificate for publishing.domain.local. Figure 10 Just as a reminder, the Action tab of the Web Publishing Rule looks like what you see in figure 11 (the only difference between the two tests was the http://rlegsoftware.com/500-internal/500-internal-server-error-windows-server-2008-iis-7.php
Even an IPhone synchronized fine. The answer to that was to copy it to the Trusted Root Certificate Authoritities container in Certificates MMC (opening Local Computer and not Local User) Reply Leave a Reply Cancel reply The target principal name is incorrect Page:  Jump to: Select a ForumAll Forums---------------------- [Threat Management Gateway (TMG) 2010] - - General - - Installation [Forefront Unified Access Gateway 2010] - The Web site on the domain controller/certificate server machine obtained a Web site certificate from the domain controller using the Web site Certificate Wizard found in the Internet Information Services console. https://support.microsoft.com/en-us/kb/841664
b) Then I decided to check the ETL trace that was also collected as part of ISA data packager. Example: So I focused on the relevant filter info and have seen the following problem there: (please note that the ETL output is much more detailed than shown below) … They have different certs obtained from the internal Cert authority.I exported the certs and imported them on the ISA as described in an article published by Thomas Shinder.
Note the Host: entry in the ASCII decode. The target principal name is incorrect. (-2146893022). Latest Contributions Product Review: Celestix HOTPin 24 Nov. 2009 Kicking the Tires on the TMG 2010 RC ISP Redundancy - Part 2: Enabling ISP Redundancy 10 Nov. 2009 Kicking the Tires The Target Principal Name Is Incorrect Cannot Generate Sspi Context The request included instructions to save the information in the machine’s certificate store.
Join the community of 500,000 technology professionals and ask your questions. What Does 500 Internal Error Mean If you bridge SSL as SSL, you may end up with a "target principle name" error because of a name mismatch between the FQDN in the request and CN on the Certificate errors followed as they >> were not from a trusted authority but I ignored them as we could access >> the site without problems. https://support.microsoft.com/en-us/kb/328917 But what type of SSL connections and Web Publishing Rules lead to this problem?
Figure 15 However, in order to make this work, you have to make sure that the ISA Server is able to resolve the FQDN in the redirect to the IP address Note that in this case the Host: entry says 10.0.0.2. ISA Server 2004 only supports wildcard certificates on the ISA Server computer. Server General HTTP Error 500.19 - Internal Server ErrorI am running Vista Ultimate.
In order to allow the external network client to establish an SSL connection to the Incoming Web Requests listener, the external client was connected to the internal network and requested a http://www.isaserver.org/articles-tutorials/publishing/error505.html SBS Server Publishing an Exchange Server In SBS2k3Hello all, my setup: 1 SBS2k3 premium server box 2 nics (1 internal 1 external) Netgear FVS318 Prosafe VPN Firewall to the internet running... Internet Explorer 500 Internal Server Error All three OWA sites behave in the same way although they have different certs. Destination Server Certificate Error Tmg Blog Archive ► 2011 (1) ► May (1) ► 2010 (14) ► November (1) ► October (3) ► July (1) ► May (5) ► April (1) ► January (3) ▼ 2009
In this test the external client establishes an SSL link with the Incoming Web Requests listener on the external interface of the ISA Server. The Web Publishing Rule is configured to forward SSL requests as HTTP requests (SSL to HTTP bridging) and its configured to forward the original Host Header. My blog aims to provide "notes from the field" in addition to covering general ISA Server concepts, best practice and my view on everything ISA. http://rlegsoftware.com/500-internal/500-internal-server-error-internal.php Anyway I finally got it working."Bill Gates works in mysterious ways" :-)btw I bought your book! (in reply to rodent) Post #: 6 Page:  << Older Topic Newer
For more information about configuring this scenario, see Publishing Multiple Web Sites using a Wildcard Certificate in ISA Server 2004 (www.microsoft.com). For example you connect to https://server.example.com and the ISA Server forwards this request to http://internalsrv. Figure 14 You have the choice as to whether or not you want to connect to the site when you access the Web site directly form the browser on the ISA
So, if the name on the certificate is www.msfirewall.org, then I must enter www.msfirewall.org on the To tab.4. While the coverage of SSL related topics such as secure OWA publishing and SSL bridging is very complete, but there was one thing I left out: the dreaded 500 Internal Server Figure 6 Test #2 – SSL to HTTP Bridging Sending Without Sending the Original Host Header Let’s repeat what we did in Test #1, except this time we’ll remove the checkmark The Page 1 of 6, previous page, next page not working, put me on the wrong track.
Also I made the mistake of having FBA on the ISA and exchange, can only be on one so I changed it to be on the exchange server. A new HTC with > Mobile 6.0 could not bypass this certificate error so I set out to correct > this issue by buying an official SSL certificate for mail.domain.com. > Later I created a local ms mail.domain.com certificate. get redirected here Even after rerunning the ICCW the ISA server does not redirect properly with: Error Code: 500 Internal Server Error.
Instead, on the internal Web server, create a new certificate that matches the name of the internal Web server, as specified on the To tab in the Web publishing rule. Checked the ISA web publishing rule settings, changed the SSL certificate to mail.domain.com, and changed the Public address to mail.domain.com. The tool could be downloaded from the below link: http://www.microsoft.com/en-us/download/details.aspx?id=811 - Collecting a network trace from the internal web server - Collecting a network trace and Fiddler trace from an external Long day ;-) removed the IIS SSL third party certificate.
The network logon failed. (1790) Posted on October 3, 2007 Brian ReidPosted in certificates, https, iis, ISA Server 2004, ISA Server 2006, SSL, Windows Server 2003 This is an error visible Get 1:1 Help Now Advertise Here Enjoyed your answer? As we close out the year 2003, I want to take this opportunity to thank everyone for the very kind words you’ve had for the ISA Server and Beyond book. As mail.domain.com is not internally resolved I tried by unchecking but no difference.
The Host Header received by the internal Web server may not be what you see in the URL contained in the Web Proxy service log entries. Post navigation Can't Update Media Player Library on Windows SmartPhoneExchange Server 2007 Rollup Update 5 One thought on “Error Code: 500 Internal Server Error. What's New? I moved a block of ASP.NET web content from my previous XP machine to a specific location on my Vista machine, and...
All information is provided on an as-is basis.The opinions expressed here and those providing comments are theirs alone, and do not reflect the opinions of Silversands, Microsoft or any employee thereof. Resource Guide for Using Microsoft NLB with ISA Server 2006 Enterprise Edition Of the many questions posted on ISA Server forums, a re-occurring subject that seems to cause confusion is that Your link states that the TO tab should remain publishing.domain.local in SBS without giving the future follow on for SBS with ISA. You’ll see this when you implement SSL bridging using Web Publishing Rules.
I installed the Root, Intermediate Certificates and Domain certificate following the directions of the CA and I also choose the proper certificate in the SBSweblistener. Certificate errors followed as they were not from a trusted authority but I ignored them as we could access the site without problems. Solved ISA 2004 - OWA 2003 - Web Error Code: 500 Internal Server Error. Judging from the intro I need to remove the third party certificate from the default site, leave the third party certificate in the SBSweblistener and re-issue a local one for the
I am also a former Microsoft Most Valuable Professional (MVP). Magalhaes Stefaan Pouseele Blogs Books Hardware ISA Appliances SSL Acceleration Links Message Boards Newsletter Signup RSS Feed Software Access Control Anti Virus Authentication Backup & Recovery Bandwidth Control Caching Content Security The domain > publishing.domain.local can be pinged and opens the site /exchange on the > lan. > > If I understand > http://technet.microsoft.com/nl-nl/l...49(en-us).aspx correctly > than the problem is caused by