Hi,

We have an AD domain with 4 sites. On 3 sites I can use external IP
address for OWA and it will work with no problems, this is a link from
our external website.

At one site however the external IP address will not work, and I need
to use something like https://servername/exchange.

It must be something to do with a setting on our router or DNS but I
not quite sure what.

Can anyone please?

Thanks.

In news:1166546214.286615.263430@48g2000cwx.googlegro ups.com,
gdf1903@hotmail.com <gdf1903@hotmail.com> stated, which I commented on
below:
> Hi,
>
> We have an AD domain with 4 sites. On 3 sites I can use external IP
> address for OWA and it will work with no problems, this is a link from
> our external website.
>
> At one site however the external IP address will not work, and I need
> to use something like https://servername/exchange.
>
> It must be something to do with a setting on our router or DNS but I
> not quite sure what.
>
> Can anyone please?
>
> Thanks.

Were you able to do this prior to today and this just started happening or
is this a new implementation?

If it is able to resolve to an IP address and the connection is successful,
however it will not open the page, then I would assume either port 443 is
not remapped to the internal server IP address, or SSL is not configured on
the website, or both.

--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

This has never worked. But as I said they get around it by using the
internal server name as the URL. The problem is that on the website the
link is for the external IP address.

The website definitely works because other users can use it from home
and other subnets and it works fine.

Thanks.


Ace Fekay [MVP] wrote:
> In news:1166546214.286615.263430@48g2000cwx.googlegro ups.com,
> gdf1903@hotmail.com <gdf1903@hotmail.com> stated, which I commented on
> below:
> > Hi,
> >
> > We have an AD domain with 4 sites. On 3 sites I can use external IP
> > address for OWA and it will work with no problems, this is a link from
> > our external website.
> >
> > At one site however the external IP address will not work, and I need
> > to use something like https://servername/exchange.
> >
> > It must be something to do with a setting on our router or DNS but I
> > not quite sure what.
> >
> > Can anyone please?
> >
> > Thanks.
>
> Were you able to do this prior to today and this just started happening or
> is this a new implementation?
>
> If it is able to resolve to an IP address and the connection is successful,
> however it will not open the page, then I would assume either port 443 is
> not remapped to the internal server IP address, or SSL is not configured on
> the website, or both.
>
> --
> Ace
> Innovative IT Concepts, Inc (IITCI)
> Willow Grove, PA
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> Having difficulty reading or finding responses to your post?
> Instead of the website you're using, I suggest to use OEx (Outlook Express
> or any other newsreader), and configure a news account, pointing to
> news.microsoft.com. This is a direct link to the Microsoft Public
> Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
> to easily find, track threads, cross-post, sort by date, poster's name,
> watched threads or subject.
> It's easy:
>
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Infinite Diversities in Infinite Combinations
> Assimilation Imminent. Resistance is Futile
> "Very funny Scotty. Now, beam down my clothes."
>
> The only constant in life is change...

I am no expert but it sounds to me like you have a redirect page working for
the 3 sites that is not on the fourth.

"gdf1903@hotmail.com" wrote:

> This has never worked. But as I said they get around it by using the
> internal server name as the URL. The problem is that on the website the
> link is for the external IP address.
>
> The website definitely works because other users can use it from home
> and other subnets and it works fine.
>
> Thanks.
>
>
> Ace Fekay [MVP] wrote:
> > In news:1166546214.286615.263430@48g2000cwx.googlegro ups.com,
> > gdf1903@hotmail.com <gdf1903@hotmail.com> stated, which I commented on
> > below:
> > > Hi,
> > >
> > > We have an AD domain with 4 sites. On 3 sites I can use external IP
> > > address for OWA and it will work with no problems, this is a link from
> > > our external website.
> > >
> > > At one site however the external IP address will not work, and I need
> > > to use something like https://servername/exchange.
> > >
> > > It must be something to do with a setting on our router or DNS but I
> > > not quite sure what.
> > >
> > > Can anyone please?
> > >
> > > Thanks.
> >
> > Were you able to do this prior to today and this just started happening or
> > is this a new implementation?
> >
> > If it is able to resolve to an IP address and the connection is successful,
> > however it will not open the page, then I would assume either port 443 is
> > not remapped to the internal server IP address, or SSL is not configured on
> > the website, or both.
> >
> > --
> > Ace
> > Innovative IT Concepts, Inc (IITCI)
> > Willow Grove, PA
> >
> > This posting is provided "AS-IS" with no warranties or guarantees and
> > confers no rights.
> >
> > Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> > Microsoft MVP - Directory Services
> > Microsoft Certified Trainer
> >
> > Having difficulty reading or finding responses to your post?
> > Instead of the website you're using, I suggest to use OEx (Outlook Express
> > or any other newsreader), and configure a news account, pointing to
> > news.microsoft.com. This is a direct link to the Microsoft Public
> > Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
> > to easily find, track threads, cross-post, sort by date, poster's name,
> > watched threads or subject.
> > It's easy:
> >
> > How to Configure OEx for Internet News
> > http://support.microsoft.com/?id=171164
> >
> > Infinite Diversities in Infinite Combinations
> > Assimilation Imminent. Resistance is Futile
> > "Very funny Scotty. Now, beam down my clothes."
> >
> > The only constant in life is change...
>
>

In news:1166547322.936011.304380@79g2000cws.googlegro ups.com,
gdf1903@hotmail.com <gdf1903@hotmail.com> stated, which I commented on
below:
> This has never worked. But as I said they get around it by using the
> internal server name as the URL. The problem is that on the website
> the link is for the external IP address.
>
> The website definitely works because other users can use it from home
> and other subnets and it works fine.
>
> Thanks.

If I understand you correctly, you are saying people internally cannot
connect from that specific internal subnet. This is because internal
requests to an outside interface on their router cannot work because the
router cannot do a "U-turn". This is a NAT limitation. Easiest solution is
to connect to the internal name of the server or use it's internal FQDN
name, such as https://internalname.domain.com/exchange.

Ace