f



Windows "routing" server separating two subnets - one subnet can reach the Internet and the other can't....computers also can't ping each other between subnets

Gurus,

I have a small lab with a bunch of servers setup on two different subnets, 
192.168.1.1 is the gateway for one and 172.16.1.1 is the gateway for the 
other.  Installed on my Router (Windows Server with three NICs - I know, 
please don't comment on this, it's is for learning purposes, not 
production), the third NIC is the gateway to the Internet.

What works:  The Router server can reach the Internet as well as the 
computers in the 192.168.1.0/24 subnet (the first subnet built).

What's broken:  The computers on the 172.16.1.0/16 subnet cannot get to the 
Internet AND no computer in either subnet can ping any computer in the other 
subnet.  What am I doing wrong?  I think I need a static route on the Router 
server but am unsure of how to configure that static route, I believe it 
needs to be configured against the 172.16.x.y NIC.  To clarify again, all 
computers on the 172.16.1.0/16 subnet have a default gateway of 172.16.1.1 - 
that is one of the interface addresses of the Windows router. All computers 
on the 172.16.1.0/16 subnet can successfully ping the gateway address of 
172.16.1.1 but not beyond it - indicating to me a problem with how I 
configured my static route on the gateway machine.

So my question would be, how exactly to configure a static route(s) on the 
gateway machine such that it will forward packets between subnets? In doing 
that, for that static route, what would be my:

Destination?
Network mask?
Gateway?

Additional details:

192.168.1.0/24 subnet computer XP1:

        Host Name . . . . . . . . . . . . : XP1
        Primary Dns Suffix  . . . . . . . : alpha.local
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : alpha.local
                                            alpha.local

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : alpha.local
        Description . . . . . . . . . . . : VMware Accelerated AMD PCNet
Adapter #2
        Physical Address. . . . . . . . . : 00-0C-29-4C-D8-52
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.200
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . : 192.168.1.10
        DNS Servers . . . . . . . . . . . : 192.168.1.10
        Lease Obtained. . . . . . . . . . : Thursday, September 18, 2008
9:31:05 PM
        Lease Expires . . . . . . . . . . : Friday, September 26, 2008
9:31:05 PM

------------------------------------------------------

172.16.1.0/16 subnet computer XP2:

        Host Name . . . . . . . . . . . . : XP2
        Primary Dns Suffix  . . . . . . . : alpha.local
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : alpha.local

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : VMware Accelerated AMD PCNet
Adapter

        Physical Address. . . . . . . . . : 00-0C-29-E1-E7-07
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 172.16.1.2
        Subnet Mask . . . . . . . . . . . : 255.255.0.0
        Default Gateway . . . . . . . . . : 171.16.1.1
        DNS Servers . . . . . . . . . . . : 192.168.1.10

--
Spin 

0
Spin
9/19/2008 9:48:59 PM
comp.windows.networking.tcp-ip 1889 articles. 0 followers. Post Follow

2 Replies
984 Views

Similar Articles

[PageSpeed] 17

On Fri, 19 Sep 2008 17:48:59 -0400, "Spin" <Spin@invalid.com> wrote:

>So my question would be, how exactly to configure a static route(s) on the 
>gateway machine such that it will forward packets between subnets? In doing 
>that, for that static route, what would be my:
>

You don't need a static route to do this, you need to enable routing
on the multi-homed pc acting as a router.

I couldn't say how to do that for server versions of windows, but for
various workstation versions it's a registry hack as follows

For win9x 

System Key:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP]
Value Name: EnableRouting
Data Type: (string value)
Value Data: (0 = disabled, 1 = enabled)

For winxp/2k/NT
 
System Key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
Value Name: IPEnableRouter
Data Type: REG_DWORD (DWORD Value)
Value Data: (0 = disabled, 1 = enabled) 


Jim.

0
James
9/21/2008 7:04:59 AM
 If you're running a server OS you'll need to configure a routing and
remote access server.



On Sep 19, 10:48=A0pm, "Spin" <S...@invalid.com> wrote:
> Gurus,
>
> I have a small lab with a bunch of servers setup on two different subnets=
,
> 192.168.1.1 is the gateway for one and 172.16.1.1 is the gateway for the
> other. =A0Installed on my Router (Windows Server with three NICs - I know=
,
> please don't comment on this, it's is for learning purposes, not
> production), the third NIC is the gateway to the Internet.
>
> What works: =A0The Router server can reach the Internet as well as the
> computers in the 192.168.1.0/24 subnet (the first subnet built).
>
> What's broken: =A0The computers on the 172.16.1.0/16 subnet cannot get to=
 the
> Internet AND no computer in either subnet can ping any computer in the ot=
her
> subnet. =A0What am I doing wrong? =A0I think I need a static route on the=
 Router
> server but am unsure of how to configure that static route, I believe it
> needs to be configured against the 172.16.x.y NIC. =A0To clarify again, a=
ll
> computers on the 172.16.1.0/16 subnet have a default gateway of 172.16.1.=
1 -
> that is one of the interface addresses of the Windows router. All compute=
rs
> on the 172.16.1.0/16 subnet can successfully ping the gateway address of
> 172.16.1.1 but not beyond it - indicating to me a problem with how I
> configured my static route on the gateway machine.
>
> So my question would be, how exactly to configure a static route(s) on th=
e
> gateway machine such that it will forward packets between subnets? In doi=
ng
> that, for that static route, what would be my:
>
> Destination?
> Network mask?
> Gateway?
>
> Additional details:
>
> 192.168.1.0/24 subnet computer XP1:
>
> =A0 =A0 =A0 =A0 Host Name . . . . . . . . . . . . : XP1
> =A0 =A0 =A0 =A0 Primary Dns Suffix =A0. . . . . . . : alpha.local
> =A0 =A0 =A0 =A0 Node Type . . . . . . . . . . . . : Unknown
> =A0 =A0 =A0 =A0 IP Routing Enabled. . . . . . . . : No
> =A0 =A0 =A0 =A0 WINS Proxy Enabled. . . . . . . . : No
> =A0 =A0 =A0 =A0 DNS Suffix Search List. . . . . . : alpha.local
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 alpha.local
>
> Ethernet adapter Local Area Connection:
>
> =A0 =A0 =A0 =A0 Connection-specific DNS Suffix =A0. : alpha.local
> =A0 =A0 =A0 =A0 Description . . . . . . . . . . . : VMware Accelerated AM=
D PCNet
> Adapter #2
> =A0 =A0 =A0 =A0 Physical Address. . . . . . . . . : 00-0C-29-4C-D8-52
> =A0 =A0 =A0 =A0 Dhcp Enabled. . . . . . . . . . . : Yes
> =A0 =A0 =A0 =A0 Autoconfiguration Enabled . . . . : Yes
> =A0 =A0 =A0 =A0 IP Address. . . . . . . . . . . . : 192.168.1.200
> =A0 =A0 =A0 =A0 Subnet Mask . . . . . . . . . . . : 255.255.255.0
> =A0 =A0 =A0 =A0 Default Gateway . . . . . . . . . : 192.168.1.1
> =A0 =A0 =A0 =A0 DHCP Server . . . . . . . . . . . : 192.168.1.10
> =A0 =A0 =A0 =A0 DNS Servers . . . . . . . . . . . : 192.168.1.10
> =A0 =A0 =A0 =A0 Lease Obtained. . . . . . . . . . : Thursday, September 1=
8, 2008
> 9:31:05 PM
> =A0 =A0 =A0 =A0 Lease Expires . . . . . . . . . . : Friday, September 26,=
 2008
> 9:31:05 PM
>
> ------------------------------------------------------
>
> 172.16.1.0/16 subnet computer XP2:
>
> =A0 =A0 =A0 =A0 Host Name . . . . . . . . . . . . : XP2
> =A0 =A0 =A0 =A0 Primary Dns Suffix =A0. . . . . . . : alpha.local
> =A0 =A0 =A0 =A0 Node Type . . . . . . . . . . . . : Unknown
> =A0 =A0 =A0 =A0 IP Routing Enabled. . . . . . . . : No
> =A0 =A0 =A0 =A0 WINS Proxy Enabled. . . . . . . . : No
> =A0 =A0 =A0 =A0 DNS Suffix Search List. . . . . . : alpha.local
>
> Ethernet adapter Local Area Connection:
>
> =A0 =A0 =A0 =A0 Connection-specific DNS Suffix =A0. :
> =A0 =A0 =A0 =A0 Description . . . . . . . . . . . : VMware Accelerated AM=
D PCNet
> Adapter
>
> =A0 =A0 =A0 =A0 Physical Address. . . . . . . . . : 00-0C-29-E1-E7-07
> =A0 =A0 =A0 =A0 Dhcp Enabled. . . . . . . . . . . : No
> =A0 =A0 =A0 =A0 IP Address. . . . . . . . . . . . : 172.16.1.2
> =A0 =A0 =A0 =A0 Subnet Mask . . . . . . . . . . . : 255.255.0.0
> =A0 =A0 =A0 =A0 Default Gateway . . . . . . . . . : 171.16.1.1
> =A0 =A0 =A0 =A0 DNS Servers . . . . . . . . . . . : 192.168.1.10
>
> --
> Spin

0
jamesparkercullen
9/23/2008 1:55:39 PM
Reply: