Windows Forum

Ask something
Discussion Locked

LAN Routing

0 helpful
3 replies

by stormrage

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

Would really appreciate assistance with routing between three lan segments. This has me knakkered...

Lan A = 192.168.0.0/28 with RIP1 routers on segment
Lan B = 192.168.1.0/28 with RIP1 routers on segment
ADSL Router 10.0.0.1/28 with NAT and firewalling and Wireless

Lan A has a Windows 2000 Server setup with RRAS doing lan routing between 192.168.0.0/28 and 10.0.0.0/28
IP=192.168.0.4/28 and IP=10.0.0.4/28

Lan B has a Windows 2003 Server setup with RRAS doing lan routing between 192.168.1.0/28 and 10.0.0.0/28
IP=192.168.1.4/28 and 10.0.0.7/28

Lan A can ping right into Lan B with good responses.

Lan B can't ping into Lan B (Yet ONLY the server can ping some devices. NOT ALL)

With pathping, traceroute or ping from behind the LAN B server, all ICMP replies simply terminate at the LAN A server.

RIP and OSPF is used on both servers.

When RRAS is enabled on LAN A all machines and sub branches can communicate right through to the I-Net and in between.

Yet, the moment LAN B's RRAS server is enabled, RIP kankkers up... (Equally if this action is reversed between the Lan's)

For some unknown reason to me, either of the servers create a 4.0.0.0/255.0.0.0 or 18.0.0.0/255.0.0.0 route entry on their near site adapters and RIP replicated this entry to all the other routers.

Any advice on how to sort this irritating issue will be greatly appreciated.

Thanks

StormRage
Thanks

3 replies

by robo_dev

Couple of random thoughts:

1) Do you have only one default gateway set in each server? Windows will allow you to have one on each interface, and this hoses things up. Even if you start setting interface metrics, dead-gateway detection will kill one of the default gateways at regular intervals.

2) You may need to define a persistent static route in the workstations on lan B to get to lan A, and vice-versa since there is a single default gateway with two adapters.

3) The Windows 2003 firewall can mess you up.

4) There are lots of oddities in the Windows 2003 IP stack such as dead-gateway detection that can really wreak havoc...

by stormrage

1) At each server ONLY one gateway was set; specifically the 10.0.0.1/28 ADSL interface on each server's WAN (LanA=10.0.0.4/28 or LanB=10.0.0.7/28) interface. This worked fine for LanA, which replicated the default route from the ADSL router (0.0.0.0 <- 10.0.0.1) to all the subnets. LanB however did not replicate the 0.0.0.0 route, causing this whole network not to be able to reach the I-Net.

I actually removed the default gateway from the LanA router (specifying none), yet RIP worked great and replicated the default route from the ADSL router to all involved machines on LanA.

The same action in LanB causes LanB to replicate NO default route to all involved machines. Therefore no machine can get to the I-Net and NO default route (0.0.0.0) exists. LanB server does create an 4.0.0.0/255.0.0.0 - default route ?????

2) If believe I stated this incorrectly:-

Workstations from LanB can reach all the subnets and machines on LanA. It is specifically the Windows 2003 Server acting as router, that can not reach LanA subnets ... or machines... And this machine is configured for monitoring....

It is as if the Windows 2000 server ONLY rejects the Windows 2003 server's packets

3) RRAS requires that Windows Firewall/ICS be DISABLED. Therefore Firewall/ICS has been disabled on both Windows Servers

4) Can you please elaborate on the dead-gateway detection?

.......

What really $%&$* me off, is the route 4.0.0.0/255.0.0.0 that just appears from #^$%&$* nowhere. Any idea to it's origins?

I am adding the routing tables below, sorry for all the space it is taking up:-

Windows 2000 Routing Server:-

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.4 1
4.0.0.0 255.0.0.0 10.0.0.7 10.0.0.4 15
4.0.2.0 255.255.254.0 10.0.0.7 10.0.0.4 3
10.0.0.0 255.255.255.0 10.0.0.4 10.0.0.4 1
10.0.0.4 255.255.255.255 127.0.0.1 127.0.0.1 1
10.255.255.255 255.255.255.255 10.0.0.4 10.0.0.4 1
20.0.0.0 255.0.0.0 192.168.0.254 192.168.0.4 2
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.4 192.168.0.4 1
192.168.0.4 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.0.255 255.255.255.255 192.168.0.4 192.168.0.4 1
192.168.1.0 255.255.255.0 192.168.0.253 192.168.0.4 3
192.168.2.0 255.255.255.0 192.168.0.254 192.168.0.4 3
192.168.3.0 255.255.255.0 192.168.0.250 192.168.0.4 3
192.168.5.0 255.255.255.0 10.0.0.7 10.0.0.4 4
224.0.0.0 224.0.0.0 10.0.0.4 10.0.0.4 1
224.0.0.0 224.0.0.0 192.168.0.4 192.168.0.4 1
255.255.255.255 255.255.255.255 10.0.0.4 10.0.0.4 1
Default Gateway: 10.0.0.1
===========================================================================
Persistent Routes:
None

Windows 2003 Routing Server:-

Active Routes:
Network Destination Netmask Gateway Interface Metric
4.0.0.0 255.0.0.0 10.0.0.4 10.0.0.7 12
10.0.0.0 255.255.255.0 10.0.0.7 10.0.0.7 20
10.0.0.7 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.0.0.7 10.0.0.7 20
20.0.0.0 255.0.0.0 10.0.0.4 10.0.0.7 3
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 10.0.0.4 10.0.0.7 4
192.168.1.0 255.255.255.0 10.0.0.4 10.0.0.7 4
192.168.2.0 255.255.255.0 10.0.0.4 10.0.0.7 4
192.168.3.0 255.255.255.0 10.0.0.4 10.0.0.7 4
192.168.5.0 255.255.255.0 192.168.5.4 192.168.5.4 10
192.168.5.4 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.5.255 255.255.255.255 192.168.5.4 192.168.5.4 10
224.0.0.0 240.0.0.0 10.0.0.7 10.0.0.7 20
224.0.0.0 240.0.0.0 192.168.5.4 192.168.5.4 10
255.255.255.255 255.255.255.255 10.0.0.7 10.0.0.7 1
255.255.255.255 255.255.255.255 192.168.5.4 192.168.5.4 1
===========================================================================
Persistent Routes:
None

A workstation behind LanA:-

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.4 192.168.0.20 20
4.0.0.0 255.0.0.0 192.168.0.4 192.168.0.20 16
10.0.0.0 255.0.0.0 192.168.0.4 192.168.0.20 3
10.0.0.0 255.0.0.0 192.168.0.250 192.168.0.20 2
20.0.0.0 255.0.0.0 192.168.0.254 192.168.0.20 2
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.20 192.168.0.20 20
192.168.0.20 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.20 192.168.0.20 20
192.168.1.0 255.255.255.0 192.168.0.253 192.168.0.20 3
192.168.2.0 255.255.255.0 192.168.0.254 192.168.0.20 3
192.168.3.0 255.255.255.0 192.168.0.250 192.168.0.20 3
192.168.3.250 255.255.255.255 192.168.0.250 192.168.0.20 1
192.168.5.0 255.255.255.0 192.168.0.4 192.168.0.20 3
224.0.0.0 240.0.0.0 192.168.0.20 192.168.0.20 20
255.255.255.255 255.255.255.255 192.168.0.20 192.168.0.20 1
255.255.255.255 255.255.255.255 192.168.0.20 3 1
Default Gateway: 192.168.0.4
===========================================================================
Persistent Routes:
None

A machine on one of the LanA subnets:-

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.3.250 192.168.3.4 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.3.0 255.255.255.0 192.168.3.4 192.168.3.4 1
192.168.3.4 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.3.255 255.255.255.255 192.168.3.4 192.168.3.4 1
224.0.0.0 224.0.0.0 192.168.3.4 192.168.3.4 1
255.255.255.255 255.255.255.255 192.168.3.4 192.168.3.4 1
Default Gateway: 192.168.3.250
===========================================================================
Persistent Routes:
None

A workstation behind LanB:-

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.5.4 192.168.5.20 10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.5.0 255.255.255.0 192.168.5.20 192.168.5.20 10
192.168.5.20 255.255.255.255 127.0.0.1 127.0.0.1 10
192.168.5.255 255.255.255.255 192.168.5.20 192.168.5.20 10
224.0.0.0 240.0.0.0 192.168.5.20 192.168.5.20 10
255.255.255.255 255.255.255.255 192.168.5.20 192.168.5.20 1
255.255.255.255 255.255.255.255 192.168.5.20 3 1
Default Gateway: 192.168.5.4
===========================================================================
Persistent Routes:
None

Notes:-

ADSL Router - NetGear DG834GT - RIP V2M
SubNet Routers - 3Net Monet - RIP V1B
Win 2K & 2K3 WAN Interfaces - RIP V2M
Win 2K LAN Interface - RIP V1B
Win 2K3 LAN Interface - RIP V2M

Thanks

by cg it

meaning remote access routing over a WAN link. if you haven't created rules that allow LAN A to communicate with LAN B and specified why type of authentication method, All traffic from A to B through the Miniports will be rejected. Further, if you didn't create a pool of addresses for the miniports, for DHCP relay, you won't get traffic. though RRAS isn't a firewall, connections to the server require some form of authentication be it MS CHAP, Window Intergrated, IPSec, and the user logging on must also have permission to log on as a remote user.

You mention using RIP but where is RIP enabled? in RRAS? or on a perimeter router?

This discussion is closed to new replies.