How can I use win2k routing to put a sub lan inside my lan?

[silverspecv]

I have 2 lans here and one win2k server with 2 nics that I want to use as a router between them. The 2 networks are 192.168.0.0/24 and 192.168.1.0/24. I installed rras on the router and I ran "route add 192.168.1.0 mask 255.255.255.0 192.168.0.54" on my workstation, but it won't forward packets. If I tracerte, I can see the packets get to the router, but the router isn't routing. What do I need to configure in rras? Also, will this "route add" be necessary on all machines? Is there a way to "publish" it or whatever? Also, will the routing appear seamless to all machines? I realize I may need to tweak dns, but suppose I use ip addresses, the whole thing should work just like one big lan right?

 

[vbrocks]

Make your server the default gateway in tcpip properties on the workstations (You can use dhcp to do this or do it by hand.

 

[silverspecv]

It is not the default gateway for the LAN, though. We got a new router this week, so the network schema has changed. Here is the new one:

The LAN is 10.1.1.0/24, and everything works fine with 10.1.1.1 as the default gateway to the internet. But we have this one multihomed server with 2 NIC's.. the main one is 10.1.1.3/24, and the second one is 192.168.1.1/24, which is plugged directly into another machine with the address 192.168.1.77/24. The multi-homed machine can see both networks just fine, but it won't route.

My workstation is 10.1.1.2, and I want to be able to ping 192.168.1.77.. I can traceroute and see the packet hit the multihomed machine, but it dies.

I found another thread in here with a similar problem, and the solution was to disable rras and re-enable it, so I did that, but it didn't work for me.

Here is my IP configuration for the multihomed machine:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : cf002
Primary DNS Suffix  . . . . . . . : specsol.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : specsol.com

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix  . : 
Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit Ethernet NIC
Physical Address. . . . . . . . . : 00-40-F4-B2-EC-90
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.1.1
DNS Servers . . . . . . . . . . . : 10.1.1.1

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix  . : 
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-D0-B7-BC-14-E4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.1.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.1.1
DHCP Server . . . . . . . . . . . : 10.1.1.1
DNS Servers . . . . . . . . . . . : 10.1.1.1
Lease Obtained. . . . . . . . . . : Thursday, December 09, 2004 10:18:45 AM
Lease Expires . . . . . . . . . . : Thursday, December 09, 2004 8:18:45 PM

And here is the routing table:

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000005 ...00 40 f4 b2 ec 90 ...... Realtek RTL8169/8110 Family Gigabit Ethernet NIC                                
0x1000006 ...00 d0 b7 bc 14 e4 ...... Intel(R) PRO Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0         10.1.1.1     192.168.1.1	  1
          0.0.0.0          0.0.0.0         10.1.1.1        10.1.1.3	  1
         10.1.1.0    255.255.255.0         10.1.1.3        10.1.1.3	  1
         10.1.1.3  255.255.255.255        127.0.0.1       127.0.0.1	  1
   10.255.255.255  255.255.255.255         10.1.1.3        10.1.1.3	  1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1	  1
      192.168.1.0    255.255.255.0      192.168.1.1     192.168.1.1	  1
      192.168.1.1  255.255.255.255        127.0.0.1       127.0.0.1	  1
     192.168.1.77  255.255.255.255      192.168.1.1     192.168.1.1	  1
    192.168.1.255  255.255.255.255      192.168.1.1     192.168.1.1	  1
        224.0.0.0        224.0.0.0         10.1.1.3        10.1.1.3	  1
        224.0.0.0        224.0.0.0      192.168.1.1     192.168.1.1	  1
  255.255.255.255  255.255.255.255      192.168.1.1     192.168.1.1	  1
Default Gateway:          10.1.1.1
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
      192.168.1.0    255.255.255.0      192.168.1.1       1

I have no idea where the 0.0.0.0 came from or the 224.0.0.0

 

[vbrocks]

What does it look like on workstation 10.1.1.2?
Do you have 10.1.1.3/24 listed as one of the gateways?
What does it look like on machine with the address 192.168.1.77/24? (It should have a default gateway of
192.168.1.1.)

 

[silverspecv]

Yes, I did a "route add" on the 10.1.1.2 (my workstation), to add 10.1.1.3 as the gateway to 192.168.1.*, and it seems to work.. traceroute shows 10.1.1.3 as the first hop, but it dies there

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : jmiller
Primary DNS Suffix  . . . . . . . : specsol.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : specsol.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix  . : 
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
Physical Address. . . . . . . . . : 00-D0-B7-B5-A8-44
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.1.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.1.1
DHCP Server . . . . . . . . . . . : 10.1.1.1
DNS Servers . . . . . . . . . . . : 10.1.1.1
Lease Obtained. . . . . . . . . . : Friday, December 10, 2004 7:15:23 AM
Lease Expires . . . . . . . . . . : Friday, December 10, 2004 5:15:23 PM

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000003 ...00 d0 b7 b5 a8 44 ...... Intel(R) PRO Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0         10.1.1.1        10.1.1.2	  1
         10.1.1.0    255.255.255.0         10.1.1.2        10.1.1.2	  1
         10.1.1.2  255.255.255.255        127.0.0.1       127.0.0.1	  1
   10.255.255.255  255.255.255.255         10.1.1.2        10.1.1.2	  1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1	  1
      192.168.1.0    255.255.255.0         10.1.1.3        10.1.1.2	  1
        224.0.0.0        224.0.0.0         10.1.1.2        10.1.1.2	  1
  255.255.255.255  255.255.255.255         10.1.1.2        10.1.1.2	  1
Default Gateway:          10.1.1.1
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
      192.168.1.0    255.255.255.0         10.1.1.3       1

 

[vbrocks]

Have you tried changing the tcp/ip properties to reflect the new default gateways on both workstations?

 

[silverspecv]

There is no new default gateway. There is only an alternate gateway for a particular subnet.

Is it possible that the win2k is acting like a firewall instead of a router? Like it's treating the LAN as if it were the internet, and the 192.168.1.* network as if it were the LAN, and thus blocking packets destined to it?