Win2000 routing can't be THIS hard???

[Shawn]

I need some advice here. I've Google'd my brains out the past
few days, and even had RRAS dreams last night, but STILL can't
seem to figure this one out...

I have three Windows 2000 Servers, a DSL connection, and some
workstation PC's all running Windows 2000/XP

ServerA: xxx.136.231.116 - Static IP
255.255.255.248 - Netmask
xxx.136.231.113 - Def.Gate (the DSL router)

ServerB: xxx.136.231.114 - Static IP (NIC1)
255.255.255.248 - Netmask
xxx.136.231.113 - Def.Gate

192.168.001.004 - Static IP (NIC2)
255.255.255.000 - Netmask
- No default gateway

ServerC: 192.168.001.003 - Static IP
255.255.255.000 - Netmask
192.168.001.004 - Def.Gate (NIC2 on ServerB)

The physical connections are, roughly:

+-------------+ +-----------+
| Switch A | | Switch B |
+-------------+ +-----------+
/ | \ / |
DSL ServerA ServerB.NIC1 / ServerC
(DNS) ServerB.NIC2
(RRAS installed)

ServerC has a DHCP server running that hands out addresses
in the 192.168.1.100 to 150 range to numerous Windows 2000
and XP workstations in the 192.168.1.0 network, all of which
are configured like ServerC with ServerB.NIC2 as the default
gateway and ServerA as their DNS server.

ServerB has RRAS installed and is set up with NAT, with NIC1
as external and NIC2 as internal. Internet is accessible from
the internal network, as are services on ServerA and ServerB.

I've added:
route add 192.168.1.0 mask 255.255.255.0 xx.136.231.114 metric 1
to ServerA

What I want to happen with this setup, though, is for me to
set at ServerA's console, and ping ServerC. ServerC registers
itself with the DNS server on ServerA fine, but when ServerA
tries to connect (ping, telnet, etc.) with ServerC, of course,
nothing happens. Nor can I ping 192.168.1.4 from ServerA.

My question seems simple enough to me, through in two days,
I've not found anything that works. How do I set up RRAS
on ServerB so that ServerC is accessible from ServerA???


Please help!

S-

 

[Danny Slye - [MSFT}]

You will never be able to ping 192.168.1.4 or 192.168.1.3 from Server A
because of NAT. NAT'ing is different from routing. One of the functions
of NAT is to obscure private IP address from the public Internet. You can
use the special ports tab of the public interface to map specific ports to
machines on the internal network. You could map 23 for telnet or 3389 for
terminal server, for example.
--------------------

I need some advice here. I've Google'd my brains out the past
few days, and even had RRAS dreams last night, but STILL can't
seem to figure this one out...

I have three Windows 2000 Servers, a DSL connection, and some
workstation PC's all running Windows 2000/XP

ServerA: xxx.136.231.116 - Static IP
255.255.255.248 - Netmask
xxx.136.231.113 - Def.Gate (the DSL router)

ServerB: xxx.136.231.114 - Static IP (NIC1)
255.255.255.248 - Netmask
xxx.136.231.113 - Def.Gate

192.168.001.004 - Static IP (NIC2)
255.255.255.000 - Netmask
- No default gateway

ServerC: 192.168.001.003 - Static IP
255.255.255.000 - Netmask
192.168.001.004 - Def.Gate (NIC2 on ServerB)

The physical connections are, roughly:

+-------------+ +-----------+
| Switch A | | Switch B |
+-------------+ +-----------+
/ | \ / |
DSL ServerA ServerB.NIC1 / ServerC
(DNS) ServerB.NIC2
(RRAS installed)

ServerC has a DHCP server running that hands out addresses
in the 192.168.1.100 to 150 range to numerous Windows 2000
and XP workstations in the 192.168.1.0 network, all of which
are configured like ServerC with ServerB.NIC2 as the default
gateway and ServerA as their DNS server.

ServerB has RRAS installed and is set up with NAT, with NIC1
as external and NIC2 as internal. Internet is accessible from
the internal network, as are services on ServerA and ServerB.

I've added:
route add 192.168.1.0 mask 255.255.255.0 xx.136.231.114 metric 1
to ServerA

What I want to happen with this setup, though, is for me to
set at ServerA's console, and ping ServerC. ServerC registers
itself with the DNS server on ServerA fine, but when ServerA
tries to connect (ping, telnet, etc.) with ServerC, of course,
nothing happens. Nor can I ping 192.168.1.4 from ServerA.

My question seems simple enough to me, through in two days,
I've not found anything that works. How do I set up RRAS
on ServerB so that ServerC is accessible from ServerA???


Please help!

S-

__
Danny Slye
Microsoft Support Professional
MCSE

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!

 

[Shawn]

Danny, thanks...

I removed NAT and everything worked fine. Now, I've got users
on the private network can't surf the web.

Any suggestions on how I can give 'em internet access without
having to re-enable NAT?

S-