Connecting two subnets with a multihomed Win2K box

[grooveman]

Hi all!

I'm feeling like a big schmuck... I've been trying to get this thing working for a few hours, but haven't quite had any luck yet.

The network looks like the following:


Cable modem---> wireless router----> Computer A
192.168.2.1 192.168.2.25 (default gateway 192.168.2.1)
|wired part| (wireless)
| and
XBox 192.168.3.1 ---------------->>Computer B
192.168.2.13 (wired to other subnet) 192.168.3.7 (default gw 192.168.3.1)
(Edit: Non munged diagram at: http://www-unix.oit.umass.edu/~asberg/temp2.txt


Both network segments work OK independently. That is, computer A can access the internet and the XBox without any trouble. (XBox can also access computer A without any trouble.) Computer B can access computer A.

Computers A and B are both running Win2K Pro... can't quite bridge the connections as easily as with WinXP. IP Routing is enabled with the registry key on computer A.

Route print on computer A brings up the following:

====================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 bf 21 00 51 ...... Realtek RTL8139/810x Family Fast Ethernet NIC

0x3 ...00 e0 98 be 31 ca ...... TNET1130
====================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.25 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.2.0 255.255.255.0 192.168.2.1 192.168.2.25 1 (Added by me.)
192.168.2.25 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.2.255 255.255.255.255 192.168.2.25 192.168.2.25 1
192.168.3.0 255.255.255.0 192.168.3.1 192.168.3.1 1
192.168.3.1 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.3.255 255.255.255.255 192.168.3.1 192.168.3.1 1
224.0.0.0 224.0.0.0 192.168.2.25 192.168.2.25 1
224.0.0.0 224.0.0.0 192.168.3.1 192.168.3.1 1
255.255.255.255 255.255.255.255 192.168.3.1 192.168.3.1 1
Default Gateway: 192.168.2.1
====================================================================
Persistent Routes:
None

An ipconfig /all on computer A gives:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : compa
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 802.11g Wireless PCI Card
Physical Address. . . . . . . . . : (snip)
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.25
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Wednesday, July 28, 2004 11:39:31 A

Lease Expires . . . . . . . . . . : Wednesday, August 11, 2004 11:39:31
AM

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
Physical Address. . . . . . . . . : (snip)
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.3.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

A traceroute from computer B to 192.168.2.13 gets stuck after hitting computer A (192.168.3.1).

Ideally, what I want to do is let the XBOX access an SMB share on computer B.

*Whew!* I've played around with route.exe but haven't gotten anywhere. I can add routes, but... :\

Any help anyone might be able to provide would be grand! I'm probably missing something so simple...

Thanks very kindly!

Andy

Edit: Oh no! My formatting! Fixing!

 

[Nothinman]

Personally, I would never try to use Windows as a router...

 

[Goosemaster]

WAY WAY WAY too many routes.

 

[Goosemaster]

Originally posted by: Nothinman
Personally, I would never try to use Windows as a router...

Windows is fine. It isn't spectacular by any means, and gets its ass handed to it by OS's that fit on a floppy disk, but it is still usuable.'

Even so, I would also recommend that you use another OS for the routing.

 

[spidey07]

I guess what the guys are sayings is there is a better way to accomplish what you're trying to do.

So can you list each device?

ideally you'd have a wireless router with some 10/100 ports - attach stuff to that and be all fine.

 

[grooveman]

Thanks for the replies, all!

I know this is a bit of a kludge... have a old Linux routing box around here somwhere that I was using as a firewall for a while, just is more of an attempt to see if I can get Win2k Pro routing working. (Would just make it so that I have one less box that has to be always on.) There are a hundred other better ways to do this... I've been fighting with this so long that I just sort of want it to work, I guess. *Grins sheepishly*

For the current routes, the only one I've added was for 192.168.2.0... the rest were created by Win2k... the only ones that can be deleted are the 224.0.0.0 ones... I'm not quite sure why they were created, but think they probably hopped on board after IP routing was enabled.

Anywho, thanks for the kind advice everyone!

Andy

Edit: There are three devices which I'm trying to get to see each other. XBox<-->Computer A<-->Computer B... Computer A is multihomed with one 802.11g connection, one 100 Mbit connection. Xbox and computer A get along fine, computer A and computer B get along fine. Computer B and the Xbox, alas, don't like each other so much.

 

[Goosemaster]

Basically, figure out what type of routing protocol your box is using. I honestly can;t tell because I am not that proficient at WORKSTATION-based routing protocols. I would assume that Windows uses RIP as a default protocol but chances are that I am wrong.

What matters most is that the right devices have the right routes.

I'll something in a sec....thinking...


EDIT:

Okay, I'm not going to write out your routes for you as you are a big boy now , but I will tell you how.

route format:

[foreign unadjacent destination] [subnet mask] [adjacent point of connection ot that network]




Gneral ex:

Router x(10.10.10.65/30)----(10.10.10.66/30)router y(10.10.10.69/30)------(10.10.10.70/30)router z

A route on router X to point to 10.10.10.70 would be

ip route 10.10.10.70 255.255.255.252 10.10.10.66

where :
10.10.10.70 is the unadjacent destination
255.255.255.252 is that destination's subnet mask
10.10.10.66 is the directly connected/adjacent interface you need to go through.

ex specific to your network:

wireless router (192.168.2.1)----(192.168.2.25)ComputerA(192.168.3.1)------(192.168.3.7)compB

A route on the wireless router to point to 192.168.3.7 would be

ip route 192.168.3.7 255.255.255.0 192.168.2.25

Or at least I think that's right ;confused;



Basically, you havea HELL of a lot of routes, but I do not see them pointing to anything but their own networks...worthless...


good luck

 

[Goosemaster]

a la Microsoft

The Windows 2000 IP routing table uses an IP address to identify an interface in the Interface field for the route. Therefore, the following process determines the next-hop address and interface:

? If the address in the Gateway field is an address that is assigned to an interface on the forwarding node:

The next-hop address is set to the destination IP address of the IP packet.

The next-hop interface is set to the interface to which the address in the Interface field is assigned.

? If the address in the Gateway field is not an address that is assigned to an interface on the forwarding node:

The next-hop address is set to the address in the Gateway field.

The next-hop interface is set to the interface to which the address

from technet.com

 

[grooveman]

Thanks, kindly Goosemaster!

Andy