- also known as “Spiny swallows his networking pride”.
Background: I’m involved in a network project in my copious free time, and we’ve run into a snag: We need to have two exit points from a LAN - one exit point is the server/proxy, a Microsoft SBS (Small Business Server) box with two NICs, one for the Internet connection and one for the LAN. The other exit point is a Cisco 2621 router that connects to a satellite office (via VPN).
I need to install some sort of route on the server, so that traffic destined for the satellite office can be handed off to the router.
Now, while I can configure Cisco routers to arc-weld underwater, I can hardly keep my own Windows PC running. Microsoft-savvy I’m not. And so I turn to the Teeming Millions…
Further details: For historical reasons, the client PCs have the server as their default gateway. Changing this would not make anyone happy. The server knows exactly two networks: The local one and the Internet. And it knows that non-local traffic should be handed to the Internet, so there is some capability to make a routing decision there.
In my salad days, I would sometimes install a route in a server like this: route -p add 131.107.3.0 mask 255.255.255.0 131.107.3.1 (these are not live IP addresses) - has this fallen by the wayside ?
My partner in crime on this job is a really good guy with Microsoft, but not that hot on networking.
Anyhow, any and all comments , hints, help, offers to drive out and fix it etc. etc. would be most welcome.
I shall sing the praises of whoever comes up with a solution.