OWA 404 using SSL

[Paul @ SL]

Dear all,

I have setup OWA fine and using it well. However I have just activated SSL
and want to use FBA.

However, when I activate FBA using SSL I get 404 Url not found after
agreeing to the certificate.

Any ideas as im stumped!

Cheers
Paul

[Paul @ SL]

Also worth stating this is a Exchange 2003 server.

Cheers.
"Paul @ SL" <pa...@servlan.co.uk> wrote in message
news:%23iaVOz0...@TK2MSFTNGP04.phx.gbl...

[a@tleederbyshired.0.tc.0.m Lee Derbyshire [MVP]]

"Paul @ SL" <pa...@servlan.co.uk> wrote in message
news:%23iaVOz0...@TK2MSFTNGP04.phx.gbl...

If you are sure that it worked before you enabled FBA, then make sure that
you have Active Server Pages set to 'Allowed' in your Web Service Extensions
in IIS Manager. Having ASP disabled can produce a misleading 404 error when
you ask the server for an .asp page, which is what the FBA logon page is.

Lee.

--
_______________________________________

Outlook Web Access for PDA, OWA For WAP:
www.leederbyshire.com
________________________________________

[Paul @ SL]

Hi Lee,

I have checked this out and already have:

ASP - Allowed
ASP.net 1.1 - Allowed
ASP.net 2.0 - Allowed...

Strangly enough, if I access OWA with FBA on the internal side then it
works, if I do this externally (ie internet) then it comes up with the 404
Url not found message.

I have checked my firewall and Port mapped 443 onto the internal
address.....

Any other suggestions???

Cheers
"Lee Derbyshire [MVP]" <email a@t leederbyshire d.0.t c.0.m> wrote in
message news:OJhNuB6A...@TK2MSFTNGP02.phx.gbl...

[a@tleederbyshired.0.tc.0.m Lee Derbyshire [MVP]]

You'll need to check your IIS logs, and see exactly which resource request
is returning the 404. Past the entries here if you can find them.

"Paul @ SL" <pa...@servlan.co.uk> wrote in message

news:%23wriNRA...@TK2MSFTNGP06.phx.gbl...

[Paul King]

Lee,

Found out what the issue was... After investigating, I thought I would see
where my certificate was being issued from. Instead of showing StartCOM
which is the free SSL certificate - it was coming up with Vigor SSL
certificate - this is my routers manufacturer.

Anyways, I remembered that the management console of the router has a
default HTTP setting of 80 and HTTPS port of 443 - thus if you don't change
these ports on the router any inbound request on the external address will
automatically go to the router itself! I have since changed these ports to
non standard numbers and everything works fine.

Sorry for being a pain, but at least got there!!

Cheers
Paul.

"Lee Derbyshire [MVP]" <email a@t leederbyshire d.0.t c.0.m> wrote in

message news:%23eN1zJF...@TK2MSFTNGP06.phx.gbl...