RRAS and IIS, need help!

I have a Win2003 Std. box with 2 NICs. One NIC is connected to the internal
network and the other, external one is connected to a PPPoE modem (via RRAS
dialin interface). On the external interface NAT and basic firewall is
enabled. My internal clients can all connect to the internet no problem. I
have a seperate Win2003 box on the same network (internal) running IIS, that
one is able to connect to the internet too no problem... The problem is I
cannot access the IIS server from the internet, or telnet into it from
externally either. I've already opened port 80 on the basic firewall (in RRAS
on the dialin interface) but that didnt work.. any ideas?

From the Internet, you cannot directly access a machine which is behind
a NAT router. You will need to forward tcp port 80 from the NAT machine to
the private IP of the IIS server. You should them be able to see the web
site from the Internet using the server's public IP.


Scott S. wrote:
> I have a Win2003 Std. box with 2 NICs. One NIC is connected to the
> internal network and the other, external one is connected to a PPPoE
> modem (via RRAS dialin interface). On the external interface NAT and
> basic firewall is enabled. My internal clients can all connect to the
> internet no problem. I have a seperate Win2003 box on the same
> network (internal) running IIS, that one is able to connect to the
> internet too no problem... The problem is I cannot access the IIS
> server from the internet, or telnet into it from externally either.
> I've already opened port 80 on the basic firewall (in RRAS on the
> dialin interface) but that didnt work.. any ideas?

Hello Bill thanks for the response. I am not sure how to do port forwarding
in RRAS...on the dialin interface (the one connected to my PPPoE modem) I
went into the Services and Ports tab, checked off Port 80 and put in the
internal IP of my IIS box (192.168.0.10).....that did not work. Any ideas?

"Bill Grant" wrote:

> From the Internet, you cannot directly access a machine which is behind
> a NAT router. You will need to forward tcp port 80 from the NAT machine to
> the private IP of the IIS server. You should them be able to see the web
> site from the Internet using the server's public IP.
>
>
> Scott S. wrote:
> > I have a Win2003 Std. box with 2 NICs. One NIC is connected to the
> > internal network and the other, external one is connected to a PPPoE
> > modem (via RRAS dialin interface). On the external interface NAT and
> > basic firewall is enabled. My internal clients can all connect to the
> > internet no problem. I have a seperate Win2003 box on the same
> > network (internal) running IIS, that one is able to connect to the
> > internet too no problem... The problem is I cannot access the IIS
> > server from the internet, or telnet into it from externally either.
> > I've already opened port 80 on the basic firewall (in RRAS on the
> > dialin interface) but that didnt work.. any ideas?
>
>
>

If it helps, heres an ipconfig /all:

Windows IP Configuration

Host Name . . . . . . . . . . . . : gateway
Primary Dns Suffix . . . . . . . : ENTERPRISE.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : ENTERPRISE.local

Ethernet adapter Internal:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet
NIC
Physical Address. . . . . . . . . : 00-50-BF-91-B8-CA
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.20
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.0.10

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.59
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

Ethernet adapter External:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet
NIC #2
Physical Address. . . . . . . . . : 00-40-05-01-EF-E2
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.0.0.1
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

PPP adapter Remote Router:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : x.x.x.x
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : x.x.x.x
DNS Servers . . . . . . . . . . . : x.x.x.x
x.x.x.x
NetBIOS over Tcpip. . . . . . . . : Disabled

ISP info omitted.

"Scott S." <(E-Mail Removed)> wrote in message
news:61C02A18-EF9D-44DE-A686-(E-Mail Removed)...
> Hello Bill thanks for the response. I am not sure how to do port
forwarding
> in RRAS...on the dialin interface (the one connected to my PPPoE modem) I
> went into the Services and Ports tab, checked off Port 80 and put in the
> internal IP of my IIS box (192.168.0.10).....that did not work. Any ideas?

It isn't "port forwarding",..it is Static NAT. In some devices it is called
Server Publishing,...I don't remember exactly what RRAS calls it and I don't
have any machines setup like that around here to check. You'll need to
investigate that, but by your post you may have already done that. You need
to make sure that IIS isn't already installed and running on the RRAS box
because it will take control of port 80 and RRAS won't be able to use it to
perform the Static NAT.

Just as an FYI...
There is no true term "port forwarding" or "forwarding a port" although it
gets thrown all over the place due to the way the SOHO market has thrown the
industry's terminology into disarray. There is Port Address Translation
(PAT) but it isn't used as stand-alone and is always used in combination
with Static NAT where the published server is listening on a different port
than the one being listen for on the external side of the NAT Device.
There is a term "IP Forwarding", but that is just normal every-day Layer3
Routing (as seen in NT4, Linux, Unix). Although it gets mistakenly used to
mean Static NAT all the time.


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------