Business network: 2 Gateways

[EKKC]

we recently merged with a smaller company. their people are now in our office. we have a second network linked up to a business DSL line we opened for guests. now its the new company's network

they have a router that connects to a dedicated line to france, we brought that over too along with the private mpls line. the internet is through the business dsl which is verizon and there's a linksys router to it. now for all servers and clients, they need to access both the internet and the french-intranet. but putting the gateway for linksys, they lose access to france. using the private-line router as gateway, they lose the internet. we do not have a proxy in place.

so i modified the routing table like so on my pc. i had the default gateway as the linksys and then did this at command prompt

route add -p 10.0.0.0 mask 255.0.0.0 (private-line router IP) metric 2

that worked for me and i have access to both the verizon-internet and the french-intranet hosted within the 10.0.0.0 range. but is there a way to make this work for multiple clients without going into each one of them and without setting up a proxy server?

thanks

 

[nweaver]

not sure what DHCP server you use, but I know you can define routes as scope options on 2k3 server.

 

[EKKC]

DHCP is on one of the 2000 servers. can i define routes on 2k adv svr?

 

[nweaver]

not sure. It would be a scope option (I saw it today on my 2k3 server).

 

[imported_netman]

Did you colapse the both of these internal networks into one? So that you can route to either gateway from a single NIC, thus not requiring a NIC on each separate network?

If the linksys allows you to place static routes on it then you could just put the 10.0.0.0/8 route on the linksys redirecting traffic to the verizon gateway.

 

[EKKC]

linksys = verizon dsl router
cisco = mpls private line router

i think i see what you're saying... but the dhcp is being handled by a server within the network, and not by the linksys, would that still work???

 

[Variable D]

You need to put the route statements in the router like EKKC said. You could 10 net the new folks and keep your old network 192 or the other way around, or your could give them each their own DHCP scope and use that range in your routers route statement. You just need to segment the two networks, either by a scope or separate private networks and then use a route statement for that scope or network. Either way will work.

 

[nweaver]

I think Netman is saying to get one default gateway, and put the static route on it, so all traffic hits the router, and then your router does it's job (routes traffic to the appropriate network)

 

[EKKC]

i am EKKC. ROFL

there isnt really new and old people network. we are keeping the two networks separate until we go ahead with a third new network that will be the permanent network of the post-merger company. the new people each gets 2 lines and 2 computers - one old computer on the old network and our computer on the actual comapny network. The guest DSL line is now our "network" for the new people, who needs internet on the verizon dsl - linksys router and the french intranet through the cisco router.

if i already have that route statement set up as persistent on the DHCP (an actual server on the network handling the DHCP - not the linksys) server's route table (so now the 10 net traffic goes to french-intranet router and everything else meaning internet goes through verizon dsl linksys router), would the same setting be delegated to the DHCP clients? i probably think it wont but if it does it will save me a lot of headache.

 

[EatSpam]

Leave the default gateway/route in DHCP as Linksys router. Make a static route entry in the Linksys router for your French network - put the local address of the French router in as the gateway for the French network.

What you want to happen: A client on your network needs to talk to the machine in France. It forwards packets to the Linksys Router (default route). The Linksys router looks in the static route table and forwards the packets to your router to France, which in turn forwards the packets to their destination.

Don't mess with static routes in DHCP or anything like that. The proper way is to leave routing to the routers.

 

[nweaver]

All the DHCP static route is going to do is push that out to all DHCP clients. It's an easy way to do this if you don't want to mess with the routers. It's a scope option, and easy to eliminate when you change. Adding this as a scope option to DHCP doesn't cause the DHCP server to route, it's still "Leaving routing to the routers".

This is just easier then typing the route add statment on every PC.

 

[EKKC]

i added a routing entry to the linksys router so all 10 net traffic gets redirected to the cisco router to france. this worked flawlessly. i take away the routing entries on my desktops/servers and they see both networks (internet and france intranet). even my dhcp clients now see both networks without adding the manual route entry. :thumbsup: to everyone who helped!

linksys routing table: (10.25.128.254 is the cisco router that goes to france intranet)
Destination LAN IP / Subnet Mask / Default Gateway / Hop Count / Interface
0.0.0.0 / 0.0.0.0 / 70.107.240.1 / 1 / Internet
10.25.128.0 / 255.255.255.0 / 0.0.0.0 / 1 / Local
10.0.0.0 / 255.0.0.0 / 10.25.128.254 / 1 / Local
70.107.240.0 / 255.255.255.0 / 0.0.0.0 / 1 / Internet

i love you guys!!!