I need some major help. Our regular exchange 2k3 mail server (S1) has just
about died. I've moved all the M boxes over to another server (S2) that has
more power for the job. I'm using S2 for the backend now and whating to use
S1 for the front end. Mail is working great if your on the inside network;
but if you try to use the OWA I keep getting HTTP Error 404 even after I
supply username and password. If I login to S2 (using IIS) I can browse and
receive OWA fine. Any help would be great.
You only get the error if you try to access from the outside?
See if this article can help you:
"HTTP 401 or 404 error messages when you access OWA implicitly or
explicitly"
http://support.microsoft.com/kb/293386
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo
"Rob Howard" <RobHoward@discussions.microsoft.com> wrote in message
news:D269D3BE-E949-43D2-8DC2-008AD56C8358@microsoft.com...
I need some major help. Our regular exchange 2k3 mail server (S1) has just
about died. I've moved all the M boxes over to another server (S2) that
has
more power for the job. I'm using S2 for the backend now and whating to
use
S1 for the front end. Mail is working great if your on the inside network;
but if you try to use the OWA I keep getting HTTP Error 404 even after I
supply username and password. If I login to S2 (using IIS) I can browse
and
receive OWA fine. Any help would be great.
Sorry, I guess I forgot to say that if I'm on S1 using IIS and browse the
exchange Virtual Directory, I get the HTTP 401 Error as well as if I'm on the
outside trying to get in.
"Rui J.M. Silva" wrote:
You only get the error if you try to access from the outside?
See if this article can help you:
"HTTP 401 or 404 error messages when you access OWA implicitly or
explicitly"
http://support.microsoft.com/kb/293386
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo
"Rob Howard" <RobHoward@discussions.microsoft.com> wrote in message
news:D269D3BE-E949-43D2-8DC2-008AD56C8358@microsoft.com...
I need some major help. Our regular exchange 2k3 mail server (S1) has just
about died. I've moved all the M boxes over to another server (S2) that
has
more power for the job. I'm using S2 for the backend now and whating to
use
S1 for the front end. Mail is working great if your on the inside network;
but if you try to use the OWA I keep getting HTTP Error 404 even after I
supply username and password. If I login to S2 (using IIS) I can browse
and
receive OWA fine. Any help would be great.
Try to troubleshoot the issue using the article I mentioned.
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo/
"Rob Howard" <RobHoward@discussions.microsoft.com> wrote in message
news:C84741E4-B32B-4E76-A23D-675729269576@microsoft.com...
Sorry, I guess I forgot to say that if I'm on S1 using IIS and browse the
exchange Virtual Directory, I get the HTTP 401 Error as well as if I'm on
the
outside trying to get in.
"Rui J.M. Silva" wrote:
You only get the error if you try to access from the outside?
See if this article can help you:
"HTTP 401 or 404 error messages when you access OWA implicitly or
explicitly"
http://support.microsoft.com/kb/293386
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo
"Rob Howard" <RobHoward@discussions.microsoft.com> wrote in message
news:D269D3BE-E949-43D2-8DC2-008AD56C8358@microsoft.com...
I need some major help. Our regular exchange 2k3 mail server (S1) has
just
about died. I've moved all the M boxes over to another server (S2) that
has
more power for the job. I'm using S2 for the backend now and whating to
use
S1 for the front end. Mail is working great if your on the inside
network;
but if you try to use the OWA I keep getting HTTP Error 404 even after
I
supply username and password. If I login to S2 (using IIS) I can
browse
and
receive OWA fine. Any help would be great.
Thanks for the reply, but I've already completed those steps and still
receiving the message.
"Rui J.M. Silva" wrote:
Try to troubleshoot the issue using the article I mentioned.
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo/
"Rob Howard" <RobHoward@discussions.microsoft.com> wrote in message
news:C84741E4-B32B-4E76-A23D-675729269576@microsoft.com...
Sorry, I guess I forgot to say that if I'm on S1 using IIS and browse the
exchange Virtual Directory, I get the HTTP 401 Error as well as if I'm on
the
outside trying to get in.
"Rui J.M. Silva" wrote:
You only get the error if you try to access from the outside?
See if this article can help you:
"HTTP 401 or 404 error messages when you access OWA implicitly or
explicitly"
http://support.microsoft.com/kb/293386
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo
"Rob Howard" <RobHoward@discussions.microsoft.com> wrote in message
news:D269D3BE-E949-43D2-8DC2-008AD56C8358@microsoft.com...
I need some major help. Our regular exchange 2k3 mail server (S1) has
just
about died. I've moved all the M boxes over to another server (S2) that
has
more power for the job. I'm using S2 for the backend now and whating to
use
S1 for the front end. Mail is working great if your on the inside
network;
but if you try to use the OWA I keep getting HTTP Error 404 even after
I
supply username and password. If I login to S2 (using IIS) I can
browse
and
receive OWA fine. Any help would be great.
Let me ask you just one thing: did you explicitly configure S1 to be a
front-end, by going to server properties and putting a mark on the option
"This is a front-end server"?
How do you access the servers from the outside? Do you have firewalls? How
many?
Can you access S2 from the outside?
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo
"Rob Howard" <RobHoward@discussions.microsoft.com> wrote in message
news:8D00A5E2-3B8B-4997-90E5-47C4D849F5DC@microsoft.com...
Thanks for the reply, but I've already completed those steps and still
receiving the message.
"Rui J.M. Silva" wrote:
Try to troubleshoot the issue using the article I mentioned.
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo/
"Rob Howard" <RobHoward@discussions.microsoft.com> wrote in message
news:C84741E4-B32B-4E76-A23D-675729269576@microsoft.com...
Sorry, I guess I forgot to say that if I'm on S1 using IIS and browse
the
exchange Virtual Directory, I get the HTTP 401 Error as well as if I'm
on
the
outside trying to get in.
"Rui J.M. Silva" wrote:
You only get the error if you try to access from the outside?
See if this article can help you:
"HTTP 401 or 404 error messages when you access OWA implicitly or
explicitly"
http://support.microsoft.com/kb/293386
--
Blog "subject: exchange"
http://spaces.msn.com/members/ehlo
"Rob Howard" <RobHoward@discussions.microsoft.com> wrote in message
news:D269D3BE-E949-43D2-8DC2-008AD56C8358@microsoft.com...
I need some major help. Our regular exchange 2k3 mail server (S1) has
just
about died. I've moved all the M boxes over to another server (S2)
that
has
more power for the job. I'm using S2 for the backend now and whating
to
use
S1 for the front end. Mail is working great if your on the inside
network;
but if you try to use the OWA I keep getting HTTP Error 404 even
after
I
supply username and password. If I login to S2 (using IIS) I can
browse
and
receive OWA fine. Any help would be great.
Posting Permissions
Reply With Quote