OWA on different server than primary web server

[mpemberton]

This scenario is similar to some other posts, but not exactly, and I'm having a tough time finding a resolution.

We just moved OWA (Exchange 2000) to it's own server, separated from our primary web server. We use basic authentication requiring SSL to log in to the web server. We have a link on the web server that opens up OWA. When you click on the link, it brings up the login box to be authenticated again. It seems that I've tried every combination of authentication settings in ISM and ESM, but nothing has worked. I've also tried not using the fully qualified path to the OWA server, but that didn't work either. Any thoughts?

Some additional info:
IIS on the OWA server is set to require SSL so users don't have to go through the primary web server to get to their e-mail.
This is in a Win2000 Server domain environment, all on the same domain, using AD for account authentication.

I've struggled with this for some time and really need some help. Thanks.

 

[EdwinSKH]

You say the users currently can log in to the OWA server directly without going through the primary webserver? Then I think the problem lies with the link pointing to the OWA server on the primary webserver. For the link, did you specify a URL of the OWA server, or to the M: driver folder on the OWA Exchange server? If it is the URL, then I believe it should work.