Localy hosted ssl site unreachable from local lan.

[bitman2112]

I hope this is close to the right area to post this question.

We have a server on our lan that hosts ssl connectivity for owa. It works like it should outside of the lan by putting in

https://outlook.ourdomain.com/owa

but the browsers return a 404 when trying to go to to that same site when connected to the same lan segment as the server.

We have an A record in our dns server for outlook.ourdomain.com that points to it's public address and the connected workstations that cannot access the secure site, return the proper public ip when a ping outlook.ourdomain.com is run.

The boss has the only MAC on the lan and entourage is happy to connect when outside of the lan on the internet but can't connect when he is on our local lan.

The windows xp boxes can't get at

https://outlook.ourdomain.com

for inside either. If we fix one, we'll fix both. But I'm a bit stumped and need help fast.

Thanks in advance.

:Ron

https://outl

 

[jlh1]

Do you host your exchange server on your internal network or is it hosted offsite?

If you host it on you internal network can you access the owa with the internal IP number ex.

Https://xxx.xxx.xxx.xxx/owa?

You my have to update you internal dns with the internal IP number for teh exchange server because you firewall may have rules to not allow the loop connection from inside the firewall to the outside IP Number and back to the inside IP Number.

 

[bitman2112]

We fixed it by employing a split brain dns.

On the inside, the ssl server points to it's internal ip.
We did this by creating an alias for the fqdn in the windows dns server that points to the private nic address.

On the outside the internet dns servers point to the public ip.