Question Locked

OWA with External IP won't work! I've tried everything!

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have been trying to get my Outlook Web Access to work for my company with no success. I was hoping you'd be able to help me. My setup is this: I have a single-server that runs SBS 2003, Exchange 2003, ISA 2004, IIS 6.0. My internal IP is: 192.168.xx.x External IP: 71.xxx.xx.xx
I spoke with my ISP and mail.healthcare-lighting.com is directed to the external IP.

I ran the CEICW with full success using the mail.healthcare-lighting.com name for my web server address. I have gone through all the certifcates process and have a certificate issued to mail.healthcare.lighting.com and it is in place in all the virtual directories with SSL checked.

Lastly I went through the mail server publishing wizard in ISA 2004 and did everything you said and made the OWA SSL Rule and incorporated the certficate. I used mail.healthcare-lighting.com as my web server address.

I cannot get it to come up. I can't even get a login screen ever. I've tried to get on from my network and I've tried on other networks.

Since I was using my external IP, I tried setting up a DNS Zone for healthcare-lighting.com, Host (A) record with no name and the internal ip address, and a host (a) record for mail with the internal ip address.
I'm just running out of ideas and can't figure it out.

I'm not too experienced with DNS so I don't know if that's the problem. Also does FQDN have anything to do with it? I checked IIS and the ip is set to all unassigned, and I don't know if that means anything either.

Thank You,

Gene Zarnick
Healthcare Lighting

If you need any information or logs or anything then let me know.

8 replies

by dumphrey

is you made no mention of a firewall or port forwarding for http or https to the sbs server.
Is the SBS server firewall on and blocking?

Is IIS running, and is the outlook site running? (i know i know...but look anyway).

On the web site, under Directory Security, is the default ip and domain name restriction set to allow or deny?

Your FQDN for the cert should match what you have on your smtp virtual server, delivery, advanced, FQDN, but it does not have to match the local machine name.

by gz2525

My server is running ISA 2004 and everything is going through there. I ran CEICW well enabling the firewalls and everything was correct.

I went into ISA and did the Mail Server Publishing Rule and set up a OWA SSL Rule with a SBS Web Listener that contains the certificate in IIS.

IIS is running and so is the outlook site. I can get to it internally by using my internal ip, but not my external ip. I have tried both allowing to all computers and denying access to my internal ip and local host and neither work.

You may have figured out something with FQDN, but I need much help.

I am running 2 NIC's, so my network address is 192.168.1.2 my server address is 192.168.16.2

The SMTP Virtual Server is using the address 192.168.1.2

My certificate is using: mail.healthcare-lighting.com which is my external ip of: 71.116.30.98

I am able to remote into my server using mail.healthcare-lighting.com, but nothing else

Thanks for all the help

by churdoo

... will not be able to access your OWA using the public FQDN, UNLESS you put an A-record in your AD DNS to resolve the public FQDN to the server's INTERNAL IP.

Your internal clients SHOULD be able to OWA using https://servername.sbsdomain.local/exchange

It looks like you got it working externally as your link did present me with the typical certificate error (since I have not imported your SBS cert into my own store) and once I continued, was presented with the SBS forms based logon challenge.

You're awfully trusting; you may want to edit your posts and mask your public URL and IP before you have every hacker on the planet messing with you.

So what exactly is the remaining problem?

by gz2525

Everythings Working! Sorry I didn't get back.

Thanks.

P.S. I masked my IP's. Good call.

by Former member

Please post back if you have any more problems or questions.
If this info is useful, please give a thumbs up. Thanks

by bob

I just worked with a MS Tech on this issue. It seems you no longer need the Server_Name in the URL. Eliminating the Server name from the URL gets me in to OWA on all 5 clients. Something changed in SP2 but MS denies it. I wrote instruction 2 years ago which included the SErver Name and it worked for the two years.

This discussion is closed to new replies.