http://support.microsoft.com/default.aspx?scid=kb;en-us;Q230082

I've made the registry change as outlined in the MS knowledge base and rebooted.
 
According to MS, I should have an "Enable IP forwarding" on the advanved properties for the TCP/IP settings - but its not there :-(

Microsoft have since removed this option from the GUI on all versions of Windows since NT 4.0 (excluding the Server versions). That is why the registry hack is required (we had a recent topic on this on NTC but I can't, for the life of me, find the exact one :x).
 

Quote: I've made the registry change as outlined in the MS knowledge base and rebooted.  
Then your machine should now be acting as a router. You haven't made it clear whether you're still having problems; are you able to ping from a machine on one subnet to a machine on the other subnet?

Sorry for the confusion.
 
I can't ping across subnets.
 
I can only ping the two subnets on the Win2K machine.
 
Regards.

Not to worry.
 
Originally posted by masterlodi:

Quote:I can't ping across subnets.
 
I may be jumping the gun, but are you using more than one machine to perform routing duties, ie;
 

Quote:Machine 1 NIC 1: 192.168.0.1
NIC 2: 192.168.1.1
 
Machine 2
NIC 1: 192.168.1.2
NIC 2: 192.168.2.1

 
Hopefully not (it gets way more complicated), can you outline your network structure for me - to make sure I'm not going down the wrong route.

Hi Ross, thanks for your help thus far!
 
I've got a Win2K machine with two network cards. First network (10.10..*) is tied to one card. Second network (192.168..*) is tied to the other card.
 
The 192.168.1.* is connected to a switch and XP Pro clients.
 
The 10.10.10.* is connected to another switch.
 
So, the Win2K machine can route to either network but now I need to build a route (with RIPV2) so that any client on the 192.168..* network to access the 10.10..* network.
 
Hope that makes some sense
 
Cheers

Hi masterlodi,
 
Gotcha. At first glance the Win2K machine *should* be routing (after simply applying the registry hack). But I'm probably missing something (if someone notices, please shout ).
 
From the Win2K machine, can you provide here a dump of the 'ROUTE PRINT' results from a command prompt? Also, I'm sure you have already done this, but check to make sure that the default gateways of the clients are set to their respective NIC's address in the Win2K box.
 
Also, if you can dump out the results from a TRACERT from one of your XP clients (when pinging across the subnets) would be a great help.
 

Hi Ross,
 
I've already checked the route but I'm obviously missing something
 
So here goes
 
 
route print
 
================================================================
Active Routes:
Network Dest Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.55 1
10.10.10.0 255.255.255.0 10.10.10.2 10.10.10.2 1
10.10.10.2 255.255.255.255 127.0.0.1 127.0.0.1 1
10.10.10.2 255.255.255.255 192.168.1.57 192.168.1.55 1
10.255.255.255 255.255.255.255 10.10.10.2 10.10.10.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 192.168.1.55 192.168.1.55 1
192.168.1.55 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.1.255 255.255.255.255 192.168.1.55 192.168.1.55 1
224.0.0.0 224.0.0.0 10.10.10.2 10.10.10.2 1
224.0.0.0 224.0.0.0 192.168.1.55 192.168.1.55 1
255.255.255.255 255.255.255.255 192.168.1.55 192.168.1.55 1
Default Gateway: 192.168.1.1
================================================================
 
 
tracert
 
================================================================
Tracing route to 10.10.10.2 over a maximum of 30 hops
1 1 ms 1 ms <1 ms officeportal.gateway.2wire.net [192.168.1.1]
2 34 ms 35 ms 35 ms btdhg546-hg3.ealing.broadband.bt.net [217.32.84.
74]
3 32 ms 35 ms 35 ms 217.32.84.33
4 33 ms 35 ms 35 ms 217.32.84.106
5 * * * Request timed out.
================================================================
 
Cheers!
 

Hi Ross,
 
I've added
 
route -p add 10.10.10.2 MASK 255.255.255.255 192.168.1.55
 
I can now ping 10.10.10.2 (IP address of the NIC) but I need to access the entire network.
 
What am I doing wrong?!
 
Also, the NIC for 10.10.. does not have a default gateway.
 
 
Cheers!

Hello,
 
I think we're getting there. This is correct (and would have been configured by making your Win2K machine an 'IP forwarder'.
 

Quote:================================================================Active Routes:
Network Dest Netmask Gateway Interface Metric
10.10.10.0 255.255.255.0 10.10.10.2 10.10.10.2 1
10.10.10.2 255.255.255.255 127.0.0.1 127.0.0.1 1
10.10.10.2 255.255.255.255 192.168.1.57 192.168.1.55 1
10.255.255.255 255.255.255.255 10.10.10.2 10.10.10.2 1
 
Your Win2K machine is correctly forwarding the packets from one subnet to the other, what I think isn't happening properly is that packets from client machines to opposite subnets are being routed out over the internet first through your broadband connection (as seen in the TRACERT). How is your internet connection integrated into your network in relation to the Win2K machine?
 

Quote:Also, the NIC for 10.10.. does not have a default gateway 
That's fine (for the moment).
 
BTW - You only need to add persistent routes when you need to specify where the next hop is [for any given subnet] for when you have more than 2 subnets. Eg, this will tell one router what is the next router (hop) to forward packets to a third subnet.
 
 
 
 

Hi there,
 
The switch that the Win2K and WinXP clients connect to serves the internet connection. It's IP address is 191.168.1.1 (if that helps).
 
Cheers

Am I right in saying that your switch (192.168.1.1) is actually an ADSL Modem/Router (also providing domain name resolution)? If so, what I think is happening is that the router (192.168.1.1) doesn't know anything about subnet 10.10.10.x and is thus going to the internet to find it.
 
I am not entirely familar with combined Modem/Routers, but there must be a way to configure it (as long as it not beyond the modem/router's capability) so that it knows to hop to the Win2K machine (NIC 192.168.1.55) to get to the 10.10.10.x subnet (through the machine's second NIC,10.10.10.2). Sort of like adding a persistent route but to the Modem/Router.
 
A couple of things to make sure of though;
 
- The 10.10.10.2 NIC in the Win2K router has NO gateway set and NO DNS set
 
- The 192.168.1.55 NIC in the Win2K router has it's gateway set to 192.168.1.1 and it's DNS set to 192.168.1.1
 
- The clients on the 10.10.10.x subnet have their gateway set to 10.10.10.2 and their DNS set to 192.168.1.1.
 
- The clients on the 192.168.1.x subnet have their gateway set to 192.168.1.1 and their DNS set to 192.168.1.1
 
Even before making any changes, you should [currently] be able to ping from the 10.10.10.x subnet to a client on the 192.168.1.x one but not visa versa.
 
Hopefully I'm on the right track .

Originally posted by ross_aveling:

Quote:Even before making any changes, you should [currently] be able to ping from the 10.10.10.x subnet to a client on the 192.168.1.x one but not visa versa. 
As long as the switch on the 10.10.10.x subnet is acting just as a switch. If not, you'll have to tell this one about the hop to subnet 192.168.1.x and set the clients gateway's accordingly.
 

Yeah the switch is a 2wire IG1800 but is not a Router per se (as far as I'm aware). It can't see the 10.x network and never has.
 
But I've followed your list and all of them are correct!
 

Originally posted by masterlodi:

Quote:It can't see the 10.x network and never has. 
That's because it doesn't know that subnet 10.10.10.x exists. If there is no way to add a new static route (ie, "to get to 10.10.10.x, go through 192.168.1.55" ) into it's routing table then we've come to a dead end I'm afraid. If someone knows different with this model of 2wire switch they may be able to lend a hand, otherwise one choice would be to get hold of a more advanced ADSL switch.
 
Also, have found this page where someone wishes to use a 2wire 1800 switch with two subnets. Looks like there are some limitations with the hardware.
 
Sorry I couldn't help you further though .

Ahhhhhhh!!!!!
 
Light dawns!!
 
That link was very helpful.
 
It shows how to add a static route to the IG1800!
 
Thing is, what is the correct route now to access the 10.10.10.x network (I know my IP addressing skills need brushing up)!

Excellent, perhaps we'll get there after all .
 
It's going to be something like (it's difficult to say without actually looking at the configuration page and it's options);
 
Network address: 10.10.10.0
Netmask: 255.255.255.0
Gateway address: 192.168.1.55
 
Good luck!

I added the suggested static route below and despite our efforts, it's still not playing.
 
There progress though, as the tracert output from an XP machine gives:
 
Tracing route to 10.10.10.1 over a maximum of 30 hops
 
1 <1 ms <1 ms <1 ms bcm2k [192.168.1.55]
2 * * * Request timed out.
 
Hope this helps!
 
Cheers Ross

OK, we'll get there in the end.
 
Try adding another static route (as before), but;
 
Network address: 10.10.10.255
Netmask: 255.255.255.255
Gateway address: 192.168.1.55
 
See if that works.

(sigh) Its still not working, Ross.
 
Here are the routes as they appear on the IG1800
 

Quote: Subnet IP Subnet Mask Gateway Interface
127.0.0.1 255.255.255.255 127.0.0.1 lo0
192.168.1.1 255.255.255.255 192.168.1.1 vlan0
192.168.2.1 255.255.255.255 192.168.2.1 vlan0:3
81.136.246.195 255.255.255.255 81.136.246.195 ppp0
10.10.10.0 255.255.255.0 192.168.1.55 vlan0
10.10.10.2 255.255.255.255 192.168.1.55 vlan0
10.10.10.255 255.255.255.255 192.168.1.55 vlan0
10.255.255.255 255.255.255.255 192.168.1.55 vlan0
217.47.137.74 255.255.255.255 81.136.246.195 ppp0
81.136.246.192 255.255.255.248 192.168.1.1 vlan0
192.168.1.0 255.255.255.0 192.168.1.1 vlan0
192.168.2.0 255.255.255.0 192.168.2.1 vlan0:3
127.0.0.0 255.0.0.0 127.0.0.1 lo0
0.0.0.0 0.0.0.0 217.47.137.74 ppp0

 
Cheers!