Help with Routing and Remote Access

Hi,

I have a server running Windows Server 2003 Enterprise x64.

It has an Intel Gigabit Dual Port NIC.

Local Area Connection is the internal network.
Local Area Connection 2 is connected directly to the Internet.

In Routing and Remote Access under IP Routing and NAT/Basic Firewall, I have
these settings for each connection:

Local Area Connection:
- Private interface connected to private network

Local Area Connection 2:
- Public interface connected to the Internet
Enable NAT on this interface (checked)
Enable a basic firewall on this interface (checked)
and under Services and Ports:
HTTPS is checked and forwarded by IP address to a separate internal web
server.
HTTP is checked and forwarded by IP Address to a separate internal web server.

The problem is that from inside the network, no one can access our website.
The website is accessible from outside of the network.

For example, www.mydomain.com has an ip address. That ip address is assigned
to Local Area Connection 2. Routing and Remote Access forwards all HTTPS and
HTTP requests to www.mydomain.com to our internal web server.

If someone inside the network goes to www.mydomain.com, we get a page can
not be displayed error. Any attempt to telnet to port 80 and 443 finds no
response. It is like Routing and Remote Access isn't forwarding requests from
inside the network back to the internal web server - instead, its just
deadending..

Any idea what is going on?

This is exactly what is happening:

When going to http://www.mydomain.com, it is hitting IIS running on that
actual machine, rather than getting port forwarded to the internal web server
ip address.

Any ideas about how to get this working correctly?

Justin

"Justin" wrote:

> Hi,
>
> I have a server running Windows Server 2003 Enterprise x64.
>
> It has an Intel Gigabit Dual Port NIC.
>
> Local Area Connection is the internal network.
> Local Area Connection 2 is connected directly to the Internet.
>
> In Routing and Remote Access under IP Routing and NAT/Basic Firewall, I have
> these settings for each connection:
>
> Local Area Connection:
> - Private interface connected to private network
>
> Local Area Connection 2:
> - Public interface connected to the Internet
> Enable NAT on this interface (checked)
> Enable a basic firewall on this interface (checked)
> and under Services and Ports:
> HTTPS is checked and forwarded by IP address to a separate internal web
> server.
> HTTP is checked and forwarded by IP Address to a separate internal web server.
>
> The problem is that from inside the network, no one can access our website.
> The website is accessible from outside of the network.
>
> For example, www.mydomain.com has an ip address. That ip address is assigned
> to Local Area Connection 2. Routing and Remote Access forwards all HTTPS and
> HTTP requests to www.mydomain.com to our internal web server.
>
> If someone inside the network goes to www.mydomain.com, we get a page can
> not be displayed error. Any attempt to telnet to port 80 and 443 finds no
> response. It is like Routing and Remote Access isn't forwarding requests from
> inside the network back to the internal web server - instead, its just
> deadending..
>
> Any idea what is going on?

"Justin" <(E-Mail Removed)> wrote:
> Hi,
> The problem is that from inside the network, no one can access our
> website.
> The website is accessible from outside of the network.
>
> For example, www.mydomain.com has an ip address. That ip address is
> assigned
> to Local Area Connection 2. Routing and Remote Access forwards all HTTPS
> and
> HTTP requests to www.mydomain.com to our internal web server.
>

Add a record in your **INTERNAL** DNS server to map www.mydomain.com to the
**LAN** IP address of your web server.

ThePro