Windows Forum

Ask something
Discussion Locked

Internet Access, Gateways and Routers

0 helpful
5 replies

by joe.oconnor

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

I have a client who has an NT server running Exchange v5.5. They have a remote office connected via an Ascend Pipeline 50 router (using a 56K point-to-point direct connection). The NT/Exchange server has a default gateway of the router LAN addressso that the remote office can access email via Exchange, print to network pinters, etc.

They also have a Netopia router (at the main location)with a Watchguard SOHO firewall unit. Local Workstations that have TCP/IP configured with DNS and the IP address of the firewall(as a gateway)can gain access to the Internet. The server cannot due to the existing default gateway for the 56K connection. It appears that you cannot have multiple gateways active at any time with NT.

Does anyone know how to configure the Ascend router (at the remote location) to "bounce-back" packets destined for the Internet? With the solution, Internet-destined packets will travel out the default gateway, hit the remote site and return to the main location to be routed out the firewall unit to the Internet destination. Does this involve configuring "static routes"??

Any help would be greatly appreciated!

5 replies

by jacq

i think the easiest solution is to make in the nt-server running the exchange the route to the remote office not the default route but just the route for the specific subnet.
the default route can be the soho router so there would be no -bouncing- of packets which would cost bandwith on that 56k connection.

the route can be added with a route command in a script configured to run once on startup
e.g. route add n.n.n.0 mask 255.255.255.0 g.g.g.g
where n.n.n.0 is the subnet and g.g.g.g is the gateway

i hope this helps.

by nettek

The first answer is correct. Make the Internet router the default gateway on the server, and use a route statement to tell the server where subnet on the other side of the 56k router is.

I would add one thing though. Make sure the command is:
route -p add
The -p makes the route persistent. Without it, the NT server will lose the route after rebooting.

This discussion is closed to new replies.