Solved

Exchange 2003 OWA - Bad Request (Invalid Hostname)

Posted on 2010-08-29
11
2,039 Views
Last Modified: 2012-06-27
Okay, This has tormented me long enough and I still don't know why it happened.

We have a 2 server network.
Server 1: Windows 2003 Domain Controller, ISA 2006 std, IP: 192.168.1.100, 172.22.6.1
Server 2: Exchange 2003, IP: 172.22.6.2

The way network setup: INTERNET <----->  ISA/DC <-------> INTERNAL NETWORK SWITCH
I published Exchange OWA to public port 80 fine, public name "mail.mydomain.com". The Listener: listens on port 80, FBA with AD authentication

In internal DNS, I set mail.mydomain.com to point to the 192.168.1.100 so that it also displayed the Form based authentication page of Exchange.

Everything works fine, and after yesterday It started reporting problem from firefox "Invalid request (Bad Hostname)" or from IE "HTTP 400 Bad Request".

By logging the request, I can see that the http request never actually got to Exchange Server, it only request to the ISA/DC and stopped there. Details below
Log type: Web Proxy (Forward)
Status: 400 Bad Request
Rule: Allow all
Source: External (111.111.111.111)
Destination: Local Host (192.168.1.100:80)
Request: GET http://192.168.1.100/exchange
Filter information: Req ID: 11f489f0; Compression: client=No, server=No, compress rate=0% decompress rate=0%
Protocol: http
User: anonymous

From within the company, I can actually type http://Server2/exchange and access webmail there, but this cannot be published to the internet.

Why is that ? Please assist me
0
Comment
Question by:Johnny_Nguyen
  • 5
  • 3
  • 2
  • +1
11 Comments
 
LVL 14

Expert Comment

by:Shabarinath Ramadasan
ID: 33555775
Seems an issue with ISA.
Which version of ISA you are using?

Are you able to browse mail.mydomain.com from your desktop ?
Are you able to browse this website from ISA using mail.mydomain.com?
Also, would suggest you to view the real time logging to understand if ISA is rejecting the requests due to some issues.

Thanks
Shaba
0
 
LVL 1

Author Comment

by:Johnny_Nguyen
ID: 33555789
I'm using ISA 2006 Standard SP1. And this isn't the first time it happened. The time logged on the ISA is real time.

From inside the network (from ISA and from other internal PCs), mail.mydomain.com cannot be browsed today, same error whereas previous I could do this (and see the form based authentication page from anywhere). Now I have to use http://server2/exchange to check webmail and it only valid for internal users.

What can be done in this case ?
0
 
LVL 1

Author Comment

by:Johnny_Nguyen
ID: 33555878
If I change the listener to listening to port 81, and browse it http://mail.mydomain.com:81/exchange from inside or outside the network, this allows me to view the FBA login page of outlook. But as soon as I logged in, every frame shows up as bad request (Invalid hostname) again. Just like they can't work on port 80 or something.
0
 
LVL 34

Expert Comment

by:Shreedhar Ette
ID: 33556034
Hi,

- Right Click the Exchange Virtual directory in the IIS.
- Click on properties.
- Go To Directoy Security> IP Address restrction> If any IP Address add remove them

Restart the IIS and then try to access the OWA.

Hope this helps,
Shree
0
 
LVL 9

Expert Comment

by:v_9mhdrf
ID: 33556087
Please check whether you have set any Host Header value in Default web site.
> Right click on default Web site go to properties.
> Click on Advanced button near IP address and check whether you have set any Host Header Value in port 80.
> If yes please remove the Host Header Value from it and check for OWA again.

check out and revert back
Thanks,
Mohammed
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
LVL 1

Author Comment

by:Johnny_Nguyen
ID: 33556102
Tried both without avail. Even then the Exchange Server is down, I should at least get to see the FBA authentication page via ISA, in this case absolutely NO.
0
 
LVL 34

Expert Comment

by:Shreedhar Ette
ID: 33556186
Are you able to access the OWA locally?
0
 
LVL 9

Expert Comment

by:v_9mhdrf
ID: 33556191
Alright please follow the kb- http://support.microsoft.com/kb/883380
Delete and recreate the Exchange related Virtual Directories and try internally first.
0
 
LVL 1

Author Comment

by:Johnny_Nguyen
ID: 33556199
If locally I type http://server2/exchange I can access email on it without problem.
But as soon as I used the published name http://mail.mydomain.com.vn/exchange then I got the error regardless locally or remotely.
0
 
LVL 9

Expert Comment

by:v_9mhdrf
ID: 33556531
Check whether you have any URL Scan software installed, and set the AntiVirus Exclusions.
Check for SSL should be disabled in Default website under Directory Security Settings.
0
 
LVL 1

Accepted Solution

by:
Johnny_Nguyen earned 0 total points
ID: 33687521
This is completely a ISA issue, and it only happened to port 80.
I removed the latest updates including SP1, then reinstalled them all, working fine.

This happened again in a week, I finally gave up and moved it to port 443 and it has been working well since
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now