Quantcast
Channel: Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients forum
Viewing all articles
Browse latest Browse all 10580

Exchange 2013: Owa bad request 400

$
0
0

Hi Guys,

Need some timely advise.


Windows Server 2012 R2 and Exchange Server 2013

The exchange server has been working fine until we upgrade to Exchange CU6.

The scenario is this, we have an existing mail server using one domain name example: mail.domain.com

we added another one to use webmail.domain.com, everything was ok the only difference is when we added webmail.domain.com, when users connect to it it is still untrusted due to no certificates yet. We didnt add additional virtual directories but we were able to access OWA for both domains.

After installing CU6 somehow OWA broke, not sure if it is CU6 fault but so far that is the only change done and adding the certificate for webmail.domain.com. ECP works fine for both domains

I have recreated the virtual directories for both ECP and OWA but  to no avail. I have read somewhere to also update the cas file and make sure that authentication are ok.

Authentication for both ecp is currently using fba,basic.

When checked under IIS logs, i dont see the error bad request 400 at all.

Here is what the logs say:

2014-09-18 08:05:38 192.168.1.45 POST /owa/auth.owa &CorrelationID=<empty>;&cafeReqId=fb06e607-724d-4d54-9439-7df7f5f79434; 443 domain\admin 42.61.32.195 Mozilla/5.0+(Windows+NT+6.1)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/37.0.2062.120+Safari/537.36 https://mail.domain.com/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fmail.domain.com%2fowa%2f%23bO%3d1 302 0 0 78

tried creating a new cas server but no luck.

Any help would be appreciated.



Viewing all articles
Browse latest Browse all 10580

Trending Articles



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