Jeremiahjpluimawtxglobalcom
Wed May 23 13:52:07 CDT 2007
I found my issue. It appears on the main default website in IIS on the back
end, there was a null header value. I removed that, restarted IIS and it
started to work correctly. So now I am able to
http:\\fe\exchange and it gets
the correct mailbox.
Thanks for all the input.
"Jeremiah <jpluim@awtxglobal.com>" wrote:
> I poked around some more and found a http error log in IIS, I see errors
> 80 HTTP/1.1 GET /exchange 400 - Hostname -
>
> Do I need to modify the host name on that back end exchange server?
>
> "Jeremiah <jpluim@awtxglobal.com>" wrote:
>
> > No SSL enabled. I did follow a document to reset OWA from msexchange.org same
> > results. We have 2 front end servers. They both can retrive any mailbox off
> > all the servers except the one i have onsite here. I can do a direct owa to
> > the exchange back server onsite with out issues.
> >
> > "Ed Crowley [MVP]" wrote:
> >
> > > Does your back-end require SSL? It can't.
> > > --
> > > Ed Crowley
> > > MVP - Exchange
> > > "Protecting the world from PSTs and brick backups!"
> > >
> > > "Jeremiah <jpluim@awtxglobal.com>"
> > > <Jeremiahjpluimawtxglobalcom@discussions.microsoft.com> wrote in message
> > > news:D313107B-F11F-4328-88E4-F79EA2999E6A@microsoft.com...
> > > >I was having issues of the Front End talking to the Back End server. I went
> > > > ahead and did a complete rebuild of that server, new name and new IP. I am
> > > > still unable to pull up a mailbox in our office. But if I pull up a
> > > > mailbox
> > > > that is over in our remote office, it works. I get HTTP error 400 when
> > > >
http:\\fe\exchange. The IIS logs or event viewer doesnt report anything.
> > > > Both
> > > > servers are in the same network. Both have Exchange SP2. I applied some
> > > > recent security updates, nothing. I ran Exchange BPAT that is reporting
> > > > minor
> > > > issues, nothing that would be related to this.
> > > > Any Ideas?
> > > >
> > >
> > >
> > >