| Author |
Message |
boofhead
Guest
|
 Posted:
Thu Dec 29, 2005 1:58 am Post subject:
E2K3 OWA "Bad Request (Invalid Hostname)" |
|
|
When I try to logon to my OWA server, doesn't matter it it's the FE
or BE server, I get the account login pop-up. After I type in the
'domain\username' and 'password' I get a page that shows only "Bad Request
(Invalid Hostname)". That is all that shows up in the window and I have
'Show friendly HTTP error messages' unchecked. I can't find the reason for
the error or what the meaning is. Below is a little background of the
environment.
I have an Exchange 5.5 server that is hosting 99% of our mailboxes.
OWA access is available fro one of our Web server which connects to the
5.5 server. About 5 months ago I upgraded to AD (W2K3) and about 3 months
later I added an Exchange 2003 server. A test account was
created and everything seems to be working fine. I'm able to access the
account on the new server from the old 5.5 OWA server. I tried to get
the OWA working on the new E2K3 server but wasn't successful. I installed a
FE server and tried OWA and once again it wouldn't work
with different errors. After some research I found out that on both servers
the 'ExchangeApplicationPool' wasn't running under the
'LocalSystem' account. Once I changed that on the FE server OWA started
working. The same was true when it was changed on the BE server.
When I tested the server the next day I started getting the above
mentioned error on both the FE and BE servers. The only thing that was
changed were some port locks so that Outlook can also work through a
firewall (KB270836). I have since deleted the registry entries and
restarted both server and I keep getting the errors.
Any help would be greatly appreciated.
Thanks,
Chris
|
|
| Back to top |
|
 |
Jonathan Norris
Guest
|
| Posted:
Thu Dec 29, 2005 1:58 am Post subject:
RE: E2K3 OWA "Bad Request (Invalid Hostname)" |
|
|
You might try to review the security settings on this site to ensure you have
your IIS/Exchange configured correctly. Most of these settings are done in
ESM.
http://www.msexchange.org/tutorials/Securing-Exchange-Server-2003-Outlook-Web-Access-Chapter5.html
Also are you running SSL, sometimes if the cert has the wrong FQDN it won't
work correctly.
--
Jonathan
No Warrenties Implied, Did you do a FULL backup today??????
"boofhead" wrote:
| Quote: | When I try to logon to my OWA server, doesn't matter it it's the FE
or BE server, I get the account login pop-up. After I type in the
'domain\username' and 'password' I get a page that shows only "Bad Request
(Invalid Hostname)". That is all that shows up in the window and I have
'Show friendly HTTP error messages' unchecked. I can't find the reason for
the error or what the meaning is. Below is a little background of the
environment.
I have an Exchange 5.5 server that is hosting 99% of our mailboxes.
OWA access is available fro one of our Web server which connects to the
5.5 server. About 5 months ago I upgraded to AD (W2K3) and about 3 months
later I added an Exchange 2003 server. A test account was
created and everything seems to be working fine. I'm able to access the
account on the new server from the old 5.5 OWA server. I tried to get
the OWA working on the new E2K3 server but wasn't successful. I installed a
FE server and tried OWA and once again it wouldn't work
with different errors. After some research I found out that on both servers
the 'ExchangeApplicationPool' wasn't running under the
'LocalSystem' account. Once I changed that on the FE server OWA started
working. The same was true when it was changed on the BE server.
When I tested the server the next day I started getting the above
mentioned error on both the FE and BE servers. The only thing that was
changed were some port locks so that Outlook can also work through a
firewall (KB270836). I have since deleted the registry entries and
restarted both server and I keep getting the errors.
Any help would be greatly appreciated.
Thanks,
Chris
|
|
|
| Back to top |
|
|
boofhead
Guest
|
| Posted:
Thu Dec 29, 2005 1:58 am Post subject:
Re: E2K3 OWA "Bad Request (Invalid Hostname)" |
|
|
We haven't installed SSL on this site as of yet. On the FE server I
turned it on thinking I could test it with Forms Based Authentication but
since I didn't load a Certificate it obviously wouldn't work. I then
reversed everything back. The SSL was never done on the BE server that is
showing the same error. This leads me to believe it's setting in Exchange
and not server installations.
I think I'm going to have to reload the FE server from scratch and see
what I can do. Since it's just a FE server I can just remove the Exchange
Software, Delete the Server from ESM and then unload IIS and start over
again and see what I get. My biggest concern is what caused the problem in
the first place.
-Chris
"Jonathan Norris" <JonathanNorris@discussions.microsoft.com> wrote in
message news:D686CFD7-B67F-4547-B3A2-071F7C4DC066@microsoft.com...
| Quote: | You might try to review the security settings on this site to ensure you
have
your IIS/Exchange configured correctly. Most of these settings are done
in
ESM.
http://www.msexchange.org/tutorials/Securing-Exchange-Server-2003-Outlook-Web-Access-Chapter5.html
Also are you running SSL, sometimes if the cert has the wrong FQDN it
won't
work correctly.
--
Jonathan
No Warrenties Implied, Did you do a FULL backup today??????
"boofhead" wrote:
When I try to logon to my OWA server, doesn't matter it it's the
FE
or BE server, I get the account login pop-up. After I type in the
'domain\username' and 'password' I get a page that shows only "Bad
Request
(Invalid Hostname)". That is all that shows up in the window and I have
'Show friendly HTTP error messages' unchecked. I can't find the reason
for
the error or what the meaning is. Below is a little background of the
environment.
I have an Exchange 5.5 server that is hosting 99% of our
mailboxes.
OWA access is available fro one of our Web server which connects to the
5.5 server. About 5 months ago I upgraded to AD (W2K3) and about 3
months
later I added an Exchange 2003 server. A test account was
created and everything seems to be working fine. I'm able to access the
account on the new server from the old 5.5 OWA server. I tried to get
the OWA working on the new E2K3 server but wasn't successful. I
installed a
FE server and tried OWA and once again it wouldn't work
with different errors. After some research I found out that on both
servers
the 'ExchangeApplicationPool' wasn't running under the
'LocalSystem' account. Once I changed that on the FE server OWA started
working. The same was true when it was changed on the BE server.
When I tested the server the next day I started getting the
above
mentioned error on both the FE and BE servers. The only thing that was
changed were some port locks so that Outlook can also work through a
firewall (KB270836). I have since deleted the registry entries and
restarted both server and I keep getting the errors.
Any help would be greatly appreciated.
Thanks,
Chris
|
|
|
| Back to top |
|
|
Jonathan Norris
Guest
|
| Posted:
Thu Dec 29, 2005 1:58 am Post subject:
Re: E2K3 OWA "Bad Request (Invalid Hostname)" |
|
|
From what you said its not working on either the BE or the FE.
Have you run any lockdown tools on your IIS? Do you have all the web
services to their default startup state? OWA should work out of the box so
if any settings were changed in IIS change them back to the recommended
settings in the article I sent you.
You may try to run MS Exchange Best Practice Analyzer it may give you some
solutions or ideas.
--
Jonathan
No Warrenties Implied, Did you do a FULL backup today??????
"boofhead" wrote:
| Quote: | We haven't installed SSL on this site as of yet. On the FE server I
turned it on thinking I could test it with Forms Based Authentication but
since I didn't load a Certificate it obviously wouldn't work. I then
reversed everything back. The SSL was never done on the BE server that is
showing the same error. This leads me to believe it's setting in Exchange
and not server installations.
I think I'm going to have to reload the FE server from scratch and see
what I can do. Since it's just a FE server I can just remove the Exchange
Software, Delete the Server from ESM and then unload IIS and start over
again and see what I get. My biggest concern is what caused the problem in
the first place.
-Chris
"Jonathan Norris" <JonathanNorris@discussions.microsoft.com> wrote in
message news:D686CFD7-B67F-4547-B3A2-071F7C4DC066@microsoft.com...
You might try to review the security settings on this site to ensure you
have
your IIS/Exchange configured correctly. Most of these settings are done
in
ESM.
http://www.msexchange.org/tutorials/Securing-Exchange-Server-2003-Outlook-Web-Access-Chapter5.html
Also are you running SSL, sometimes if the cert has the wrong FQDN it
won't
work correctly.
--
Jonathan
No Warrenties Implied, Did you do a FULL backup today??????
"boofhead" wrote:
When I try to logon to my OWA server, doesn't matter it it's the
FE
or BE server, I get the account login pop-up. After I type in the
'domain\username' and 'password' I get a page that shows only "Bad
Request
(Invalid Hostname)". That is all that shows up in the window and I have
'Show friendly HTTP error messages' unchecked. I can't find the reason
for
the error or what the meaning is. Below is a little background of the
environment.
I have an Exchange 5.5 server that is hosting 99% of our
mailboxes.
OWA access is available fro one of our Web server which connects to the
5.5 server. About 5 months ago I upgraded to AD (W2K3) and about 3
months
later I added an Exchange 2003 server. A test account was
created and everything seems to be working fine. I'm able to access the
account on the new server from the old 5.5 OWA server. I tried to get
the OWA working on the new E2K3 server but wasn't successful. I
installed a
FE server and tried OWA and once again it wouldn't work
with different errors. After some research I found out that on both
servers
the 'ExchangeApplicationPool' wasn't running under the
'LocalSystem' account. Once I changed that on the FE server OWA started
working. The same was true when it was changed on the BE server.
When I tested the server the next day I started getting the
above
mentioned error on both the FE and BE servers. The only thing that was
changed were some port locks so that Outlook can also work through a
firewall (KB270836). I have since deleted the registry entries and
restarted both server and I keep getting the errors.
Any help would be greatly appreciated.
Thanks,
Chris
|
|
|
| Back to top |
|
|
boofhead
Guest
|
| Posted:
Thu Dec 29, 2005 1:58 am Post subject:
Re: E2K3 OWA "Bad Request (Invalid Hostname)" |
|
|
The only thing that was changed in the OWA was the 'ExchangeApplicationPool'
which had it's identity set to the 'IWAM' identity by default. Once I
changed that to 'Local System', found it in KB829167, it started working on
both the FE and BE. I kept reading everywhere that OWA just works once its
installed but I could never jet get it to work until that item was changed.
The very next day that I tried to access the OWA site it stopped working.
I read the document that you mentioned last week when I first got the
OWA up and going and and reviewed it again and don't see anything that
pertains to this problem or a misconfigured OWA server. I will run the
Analyzer and see what it gives me.
The FE doesn't pass anything to the BE's web service correct? My
understanding is that the FE accesses the Information store directly so I
could in theory shut down the HTTP service on the BE all together.
Thanks for your help,
-Chris
"Jonathan Norris" <JonathanNorris@discussions.microsoft.com> wrote in
message news:F095828D-031D-4534-B8BA-EFF4972E88A3@microsoft.com...
| Quote: | From what you said its not working on either the BE or the FE.
Have you run any lockdown tools on your IIS? Do you have all the web
services to their default startup state? OWA should work out of the box
so
if any settings were changed in IIS change them back to the recommended
settings in the article I sent you.
You may try to run MS Exchange Best Practice Analyzer it may give you some
solutions or ideas.
--
Jonathan
No Warrenties Implied, Did you do a FULL backup today??????
"boofhead" wrote:
We haven't installed SSL on this site as of yet. On the FE server I
turned it on thinking I could test it with Forms Based Authentication
but
since I didn't load a Certificate it obviously wouldn't work. I then
reversed everything back. The SSL was never done on the BE server that
is
showing the same error. This leads me to believe it's setting in
Exchange
and not server installations.
I think I'm going to have to reload the FE server from scratch and
see
what I can do. Since it's just a FE server I can just remove the
Exchange
Software, Delete the Server from ESM and then unload IIS and start over
again and see what I get. My biggest concern is what caused the problem
in
the first place.
-Chris
"Jonathan Norris" <JonathanNorris@discussions.microsoft.com> wrote in
message news:D686CFD7-B67F-4547-B3A2-071F7C4DC066@microsoft.com...
You might try to review the security settings on this site to ensure
you
have
your IIS/Exchange configured correctly. Most of these settings are
done
in
ESM.
http://www.msexchange.org/tutorials/Securing-Exchange-Server-2003-Outlook-Web-Access-Chapter5.html
Also are you running SSL, sometimes if the cert has the wrong FQDN it
won't
work correctly.
--
Jonathan
No Warrenties Implied, Did you do a FULL backup today??????
"boofhead" wrote:
When I try to logon to my OWA server, doesn't matter it it's
the
FE
or BE server, I get the account login pop-up. After I type in the
'domain\username' and 'password' I get a page that shows only "Bad
Request
(Invalid Hostname)". That is all that shows up in the window and I
have
'Show friendly HTTP error messages' unchecked. I can't find the
reason
for
the error or what the meaning is. Below is a little background of
the
environment.
I have an Exchange 5.5 server that is hosting 99% of our
mailboxes.
OWA access is available fro one of our Web server which connects to
the
5.5 server. About 5 months ago I upgraded to AD (W2K3) and about 3
months
later I added an Exchange 2003 server. A test account was
created and everything seems to be working fine. I'm able to access
the
account on the new server from the old 5.5 OWA server. I tried to
get
the OWA working on the new E2K3 server but wasn't successful. I
installed a
FE server and tried OWA and once again it wouldn't work
with different errors. After some research I found out that on both
servers
the 'ExchangeApplicationPool' wasn't running under the
'LocalSystem' account. Once I changed that on the FE server OWA
started
working. The same was true when it was changed on the BE server.
When I tested the server the next day I started getting the
above
mentioned error on both the FE and BE servers. The only thing that
was
changed were some port locks so that Outlook can also work through a
firewall (KB270836). I have since deleted the registry entries and
restarted both server and I keep getting the errors.
Any help would be greatly appreciated.
Thanks,
Chris
|
|
|
| Back to top |
|
|
Jonathan Norris
Guest
|
| Posted:
Thu Dec 29, 2005 8:37 am Post subject:
Re: E2K3 OWA "Bad Request (Invalid Hostname)" |
|
|
Could it be something wrong with a domain policy or something? Problem is I
am not finding anything about this error and possible causes. Try doing
MSEXBPA it will check your configuration.
--
Jonathan
No Warrenties Implied, Did you do a FULL backup today??????
"boofhead" wrote:
| Quote: | The only thing that was changed in the OWA was the 'ExchangeApplicationPool'
which had it's identity set to the 'IWAM' identity by default. Once I
changed that to 'Local System', found it in KB829167, it started working on
both the FE and BE. I kept reading everywhere that OWA just works once its
installed but I could never jet get it to work until that item was changed.
The very next day that I tried to access the OWA site it stopped working.
I read the document that you mentioned last week when I first got the
OWA up and going and and reviewed it again and don't see anything that
pertains to this problem or a misconfigured OWA server. I will run the
Analyzer and see what it gives me.
The FE doesn't pass anything to the BE's web service correct? My
understanding is that the FE accesses the Information store directly so I
could in theory shut down the HTTP service on the BE all together.
Thanks for your help,
-Chris
"Jonathan Norris" <JonathanNorris@discussions.microsoft.com> wrote in
message news:F095828D-031D-4534-B8BA-EFF4972E88A3@microsoft.com...
From what you said its not working on either the BE or the FE.
Have you run any lockdown tools on your IIS? Do you have all the web
services to their default startup state? OWA should work out of the box
so
if any settings were changed in IIS change them back to the recommended
settings in the article I sent you.
You may try to run MS Exchange Best Practice Analyzer it may give you some
solutions or ideas.
--
Jonathan
No Warrenties Implied, Did you do a FULL backup today??????
"boofhead" wrote:
We haven't installed SSL on this site as of yet. On the FE server I
turned it on thinking I could test it with Forms Based Authentication
but
since I didn't load a Certificate it obviously wouldn't work. I then
reversed everything back. The SSL was never done on the BE server that
is
showing the same error. This leads me to believe it's setting in
Exchange
and not server installations.
I think I'm going to have to reload the FE server from scratch and
see
what I can do. Since it's just a FE server I can just remove the
Exchange
Software, Delete the Server from ESM and then unload IIS and start over
again and see what I get. My biggest concern is what caused the problem
in
the first place.
-Chris
"Jonathan Norris" <JonathanNorris@discussions.microsoft.com> wrote in
message news:D686CFD7-B67F-4547-B3A2-071F7C4DC066@microsoft.com...
You might try to review the security settings on this site to ensure
you
have
your IIS/Exchange configured correctly. Most of these settings are
done
in
ESM.
http://www.msexchange.org/tutorials/Securing-Exchange-Server-2003-Outlook-Web-Access-Chapter5.html
Also are you running SSL, sometimes if the cert has the wrong FQDN it
won't
work correctly.
--
Jonathan
No Warrenties Implied, Did you do a FULL backup today??????
"boofhead" wrote:
When I try to logon to my OWA server, doesn't matter it it's
the
FE
or BE server, I get the account login pop-up. After I type in the
'domain\username' and 'password' I get a page that shows only "Bad
Request
(Invalid Hostname)". That is all that shows up in the window and I
have
'Show friendly HTTP error messages' unchecked. I can't find the
reason
for
the error or what the meaning is. Below is a little background of
the
environment.
I have an Exchange 5.5 server that is hosting 99% of our
mailboxes.
OWA access is available fro one of our Web server which connects to
the
5.5 server. About 5 months ago I upgraded to AD (W2K3) and about 3
months
later I added an Exchange 2003 server. A test account was
created and everything seems to be working fine. I'm able to access
the
account on the new server from the old 5.5 OWA server. I tried to
get
the OWA working on the new E2K3 server but wasn't successful. I
installed a
FE server and tried OWA and once again it wouldn't work
with different errors. After some research I found out that on both
servers
the 'ExchangeApplicationPool' wasn't running under the
'LocalSystem' account. Once I changed that on the FE server OWA
started
working. The same was true when it was changed on the BE server.
When I tested the server the next day I started getting the
above
mentioned error on both the FE and BE servers. The only thing that
was
changed were some port locks so that Outlook can also work through a
firewall (KB270836). I have since deleted the registry entries and
restarted both server and I keep getting the errors.
Any help would be greatly appreciated.
Thanks,
Chris
|
|
|
| Back to top |
|
|
Jonathan Norris
Guest
|
| Posted:
Thu Dec 29, 2005 9:21 am Post subject:
RE: E2K3 OWA "Bad Request (Invalid Hostname)" |
|
|
I did find something that may be of interest to you it relates to the IWAM
and IUSER account and domain/local policies. They need certain permissions
to function properly. Perhaps something on your Domain Policy was changed to
cause this issue.
http://www.kbalertz.com/899300/Event.message.logged.Application.start.application.aspx
--
Jonathan
No Warrenties Implied, Did you do a FULL backup today??????
"boofhead" wrote:
| Quote: | When I try to logon to my OWA server, doesn't matter it it's the FE
or BE server, I get the account login pop-up. After I type in the
'domain\username' and 'password' I get a page that shows only "Bad Request
(Invalid Hostname)". That is all that shows up in the window and I have
'Show friendly HTTP error messages' unchecked. I can't find the reason for
the error or what the meaning is. Below is a little background of the
environment.
I have an Exchange 5.5 server that is hosting 99% of our mailboxes.
OWA access is available fro one of our Web server which connects to the
5.5 server. About 5 months ago I upgraded to AD (W2K3) and about 3 months
later I added an Exchange 2003 server. A test account was
created and everything seems to be working fine. I'm able to access the
account on the new server from the old 5.5 OWA server. I tried to get
the OWA working on the new E2K3 server but wasn't successful. I installed a
FE server and tried OWA and once again it wouldn't work
with different errors. After some research I found out that on both servers
the 'ExchangeApplicationPool' wasn't running under the
'LocalSystem' account. Once I changed that on the FE server OWA started
working. The same was true when it was changed on the BE server.
When I tested the server the next day I started getting the above
mentioned error on both the FE and BE servers. The only thing that was
changed were some port locks so that Outlook can also work through a
firewall (KB270836). I have since deleted the registry entries and
restarted both server and I keep getting the errors.
Any help would be greatly appreciated.
Thanks,
Chris
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in