Quantcast
Channel: Forefront TMG and ISA Server forum
Viewing all articles
Browse latest Browse all 3822

Exchange OWA publishing issue

$
0
0

I have setup a new Hyper-V test environment consisting of:
•      TMG 2010
•      Exchange 2010 Standard
•      Windows Server DC

So far I have:
•      Set up DNS (external & internal)
•      Created a self-signed certificate
•      Created an Exchange publishing rule complete with listener using the certificate
•      Enabled and configured all the relevant client access settings on Exchange
•      Made sure that the OWA web site in IIS was set to allow Windows and basic authentication

When I browse to our OWA site through TMG (either internally or externally) I get the usual certificate error (it’s a self-signed certificate so it’s ok) the OWA page appears but when I log on I get: "Error Code: 500 Internal Server Error. The target principal name is incorrect. (-2146893022)"

HOWEVER, when I connect to OWA on the Exchange server locally (https://127.0.0.1/owa) it all works fine so the credentials are correct.
So I think I have narrowed down the issue to TMG.

TMG shows the following entry in the log:
Failed Connection Attempt TEST2008TMG 06/07/2012 10:56:02
Log type: Web Proxy (Reverse)
Status: 0x80090322 
Rule: <Exchange> Outlook Web Access
Source: External (**.**.***.**:51656)
Destination: Local Host (192.168.51.3:443)
Request: GET http://mail.subdomain.domain.org/owa
Filter information: Req ID: 0b7caac3; Compression: client=Yes, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=yes, valid=yes, updated=no, logged off=no, client type=private, user activity=yes
Protocol: https
User: domain.org\user@domain.org
Additional information
Client agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
Object source: Internet (Source is the Internet. Object was added to the cache.)
Cache info: 0x0
Processing time: 31 MIME type:


Marco S


Viewing all articles
Browse latest Browse all 3822

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>