Tricky routing problem

Ultimate Windows 7 ultimate
February 18, 2010 at 09:19:24
Specs: Windows Vista
G'day everyone

My house now has two internet connections.
I've been trying to set it up so that there are
two isolated networks each with their own
internet connection, but so the halves can talk
via my server.

My server has two NICs, each configured to
the subnet of each network. Each network has
a router/modem (connects to the internet),
which is set as the default gateway of hosts
on each side of the server by DHCP. The aim
is to have the router/modems route traffic
destined for the other networks via the server. I
tried to set up static routes, but they have only
partially worked.

For instance, the router at 192.168.1.1 has a
static route for 192.168.0.0/255.255.0.0, and
directs this to 192.168.1.2, the IP of the
server's appropriate NIC. I am then able to ping
192.168.2.2, the server's other NIC which is
connected to the other network. However I
cannot ping any hosts on the other network,
which is my problem.

The server is running windows server 2003,
and has RRaS installed. I simply went "enable
RRaS" and ticked the LAN routing box. I'm not
sure if it requires further configuration or not.

The server can access everything just fine.


If anyone can help me, please help! :D

By the way, the motivation for the splitting of
the network was because it is a requirement
that hosts automatically configure themselves
with DHCP and use the appropriate internet
gateway depending on where they are
connected.

Thank you for reading ^_^


See More: Tricky routing problem

Report •


#1
February 18, 2010 at 09:35:45
You have conflicting requirements

"The aim is to have the router/modems route traffic
destined for the other networks via the server."

Not going to happen since this is handled by the gateway entry on the host

"the motivation for the splitting of
the network was because it is a requirement
that hosts automatically configure themselves
with DHCP and use the appropriate internet
gateway"

Given the requirement no server is required. Each links router can do that for you seemlessly.

RRAS is for routing between the interfaces. In your case its only purpose is to provide routes between the two lans.

Usually only one interface has a gateway entry. Two gateways/added routes maybe confusing the situation if you can't ping between subnets via the server


Report •

#2
February 18, 2010 at 09:40:58
can you suggest a simpler way for me to have the two
physical networks able to communicate with each other whilst
each using their own internet connections and all configuring
themselves with DHCP? I couldn't think of a simpler way to do
it because if i don't split the networks with a router, the DHCP
packets cannot be segmented to the appropriate networks.

please suggest any simple solution

thank you very much for replying


Report •

#3
February 18, 2010 at 09:42:14
a very simple way for me to explain my basic need is this

two local networks with their own internet connections that use
DHCP that can also communicate with each other


Report •

Related Solutions

#4
February 18, 2010 at 10:20:06
Yes simple

Put a router inbetween the two lans and do not enable dhcp passthru.

Dhcp will stay on each lans subnet and not crossover but all other traffic will.


Report •

#5
February 18, 2010 at 22:20:03
that's what i have done, but routing is not working. as i said, i am
unable to access the computers on each side of the router in the
middle. i'm sorry if i'm not giving some kind of specific
information that is relevant, but i'm not really sure what could be
wrong.

thanks for replying.


Report •

#6
February 18, 2010 at 22:53:37
I enabled RIP on the routers and the central server (which is
the router between the networks), and i get these results.
192.168.2.1 is the router of the other network, 192.168.2.2 is
the server's NIC on the other network and 192.168.2.4 is a
host on the other network. As you can see, I can access
everything perfectly except the host on the other network.
This is why I am very confused. The routing table of the server
in RRaS shows a route to 192.168.2.0/255.255.255.0 with the
NIC on that network set as the interface, and 192.168.2.2 as
the gateway. This sounds right, so i'm at a loss to explain
why I can't ping the host on the other network. The server in
the middle can ping it perfectly.

C:\Windows\system32>tracert 192.168.2.1

Tracing route to 192.168.2.1 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 1 ms 1 ms <1 ms GOD [192.168.1.2]
3 2 ms 2 ms 2 ms 192.168.2.1

Trace complete.

C:\Windows\system32>tracert 192.168.2.2

Tracing route to GOD [192.168.2.2]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 192.168.1.1
2 1 ms 1 ms 1 ms GOD [192.168.2.2]

Trace complete.

C:\Windows\system32>tracert 192.168.2.4

Tracing route to 192.168.2.4 over a maximum of 30 hops

1 2 ms 2 ms 1 ms 192.168.1.1
2 1 ms 1 ms <1 ms GOD [192.168.1.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.

Thanks for any help or suggestions!


Report •

#7
February 18, 2010 at 22:55:40
And yes, the server only has a default gateway set on one of its
NICs for its own internet access. The other NICs don't have one
set. I'm very confused.

Report •

#8
February 19, 2010 at 00:03:08
I've discovered that my routing was working perfectly and that
windows firewall is COMPLETELY blocking everything from the
other subnet. If anyone knows how to make it trust a subnet,
please reply.

Thanks for everyone's help.


Report •

#9
February 19, 2010 at 05:30:23
Why not just disable it? This is within a LAN environment is it not?

Report •


Ask Question