Home > Error Code > Error Code: 500 Internal Server Error. The Target Principal Name Is Incorrect. (-2146893022)

Error Code: 500 Internal Server Error. The Target Principal Name Is Incorrect. (-2146893022)

Contents

You can see a capture taken from the internal interface of the ISA Server while this transaction took place. Regards, Amit Saxena. Privacy statement  © 2016 Microsoft. Categories ADFS BizTalk FEP 2010 Hyper V ISA-TMG-UAG MOSS 2007 SharePoint 2010 SiteMinder SQL Server Storage VMware Web Servers Windows OS Unordered List Pages Home About Terms Of Use Archives Blog http://odenews.net/error-code/tvpad-server-error-code-1.html

Also, please update the NIC drivers of the TMG Server. Extending a Web Application in SharePoint 2010 1. 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 Stop the traces and logging on TMG and Clilent. https://support.microsoft.com/en-us/kb/841664

Error Code: 500 Internal Server Error. The Target Principal Name Is Incorrect. (-2146893022)

Im getting tired of restarting the TMG server so I realy hope the fix works for you ...PB Wednesday, October 13, 2010 9:42 AM 0 Sign in to vote Hi Everyone! Test #1 – SSL to HTTP Bridging Sending Original Host Header In the first test we’ll look at how SSL to HTTP bridging works and also what happens when you Disable "Block high bit character" in the HTTP policy, did that, I even disabled the Webproxy Filter on HTTP/HTTPs. 2. newsgator Bloglines iNezha My Tweets @AskCiti CAN SOMEONE PLEASE ANSWER THE PHONE!!

Its working from inside the network (with out TMG) but it respons with an Error 500 from outside. All rights reserved.Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks|Site Feedback Home | Site Map | Cisco How To | Net How To | Wireless | Search | Forums | Services | Donations Leon Sunday, June 27, 2010 4:49 AM Answers 0 Sign in to vote Need more information. I'll check on answers on Monday and in case nobody has picked this up I'll also open a ticket with a reference to this thread.

The Web clients (and their users) expect the connection to be secure from client to server. Error Code 500 Internal Server Error Invalid Index 1413 Join Now For immediate help use Live now! Keep Walking! Is there a directory equivalent of /dev/null in Linux?

You actually encountered this error in our first ISA Server book, but because of time and space considerations for that book, we didn’t have the chance to expand on what the Note that while the original host header was sent to the internal network Web server, the GET request is denoted as http://10.0.0.2 in the Web Proxy service log entry. Post your questions, comments, feedbacks and suggestions Contact a consultant Related Topics This web is provided "AS IS" with no warranties. Take a look at the figure 1 to refresh your memory on this error.

Error Code 500 Internal Server Error Invalid Index 1413

The certificate was then imported into the ISA Server machine’s Personal Certificate store and then bound to the Incoming Web Requests listener. Copyright 2002-2017 ChicagoTech.net, All rights reserved. Error Code: 500 Internal Server Error. The Target Principal Name Is Incorrect. (-2146893022) In The Farm servers-> connectivity verification for send an htt/https get I have https://*/OWA/ it was by default with that path when the rule was created. My exchange CA was using the old ISA 2006 as GW I need to change it with the new one. :( The new exchange 2010 is not in production yet so

This is how video conferencing should work! http://odenews.net/error-code/the-operation-cannot-be-completed-because-an-unexpected-error-occurred-error-code-50.html Open Netmon on the client & TMG,select all interfaces and start the capture on both. Open Central Administration. It randomly throws out Error Code: 500 Internal Server Error. (-1073479663) and the page won't open till I refresh it for the next 10-20 seconds.

Internet Control Message Protocol (ICMP) network is un... Verify normalization will block URLs containing escaped characters after normalization. While we wanted to make the book a valuable reference on the finer points of ISA Server, I never expected so many people would write in about how much they liked have a peek at these guys Here’s how to do it right.

Stick this into a .vbs file on your TMG, and then run it: quote:Const SE_VPS_GUID = "{143F5698-103B-12D4-FF34-1F34767DEabc}" Const SE_VPS_NAME = "CookieFilterDecodeUEncoding" Const SE_VPS_VALUE = true Sub SetValue() ' Create the root Although I think it should work with owa too, but worth a shot 0 LVL 8 Overall: Level 8 Exchange 4 Message Expert Comment by:PaulD77 ID: 374644602012-01-19 Hmmm did you Contact the server administrator. (12202) From another internal client computer: http://public nameyields Error code: 12206 The page you requested could not be reached.

To troubleshoot Kerberos errors, first use NTLM authentication or allow the client to authenticate directly to the internal server.

The request was rejected by the HTTP filter. The solution is to prevent the host header mismatch, and the way you prevent the mismatch is to configure the Web Publishing Rule to use the FQDN listed in the Web The redirection and OWA publishing is Ok I am able to see the form but when I tried to login typing the credential I saw this error Page can not be You say HOST File works, which points that these are securenat and if it works, I suggest lets take an HTTPWatch & a netmon on client and a netmon on the

I got the dreaded 500 Internal Server Error – The target principal name is incorrect error that you saw in the very first figure in this article. Suppose you would want to publish OWA for Exchange 2007 CAS servers, for that you would ... I get the same error when I click on the "Browse on *:80 (http)" link in IIS Admin. check my blog Wednesday, September 08, 2010 8:08 AM 0 Sign in to vote Kurian, is the TMG server backlogging alot of packets when it's doing this?

You may also need to check the winsock at the time of the issue. I am using basic authentication at TMG so the Form is disabled at Exchange CAS farm. The certificate was exported along with its private key and copied to the ISA Server. When I simulate external http traffic in TMG, I get Allowed Traffic.

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. Click Filtering > Configure HTTP under the Traffic tab. Contact the server administrator. (12202) Previous steps: I have verified that the application pool identity has access to the inetpub/wwwroot folder I tried setting the Web Proxy Autodiscover port to 8080. Often, this is caused when a client request doesnt specify content encoding but the published server responds with a content-encoding specified in the HTTP response header.

Forum Software © ASPPlayground.NET Advanced Edition Tech News Articles Microsoft Exchange Server Cloud Computing Amazon Web Services Hybrid Cloud Office 365 Microsoft Azure Virtualization Microsoft Hyper-V Citrix VMware VirtualBox Servers Windows If you can, switch to HTTP temporarily to make sure everything else works properly. Recursive variable declaration more hot questions question feed default about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Internally is working ok. 0 LVL 8 Overall: Level 8 Exchange 4 Message Expert Comment by:PaulD77 ID: 374640272012-01-19 Okay.

Each of the Web Publishing rules required an SSL connection to the Incoming Web Requests listener. In this example, you do not want the www.internal.net request to be forwarded back to the Incoming Web Requests listener! Be careful when looking at those Web Proxy service logs during Web Publishing Rule troubleshooting! Try byname and IP. (IP of yahoo.com is 209.191.122.70).

Now, follow the TCP streams from your client to the TMG, right from the handshake for proxy and see where it fails. The reason for this is that we selected the Send the original host header to the publishing server instead of the actual one (specified above) option. It happens for all clients, Firewall Client, SecureNAT and even on the TMG host.