Discussion Locked

Help with Gateways

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

I would like to anticipate that I am no expert in this field
I have the following task to accomplish:

I have a network with static IP's assigned (Win2000 Server and Win98 clients) - 192.168.2.x is the network.
The clients link to an AS-400 PC for administrative purposes which is located to another geographical location through a peer to peer cable hooked to a router carrying IP 192.168.2.1 on the LAN.
For this reason, the client's gateway (In windows 98 LAN settings) was set to the Router's IP;
When the clients send packet requests for the AS-400 PC (192.168.200.3), which is different than the IP of the local LAN, the client is handling them through the gateway (which is the router).
Now I need to do Internet Connection Sharing, and for this reason, have to let the client's through a different gateway (the server, and not the router anymore).
By doing so, I get ICS up and running without any problems, but then obviously the clients loose connection to the AS-400.

I need to tell RRAS that all packets requestes to 192.168.200.3 (the remote ip) be forwarded to through the other gateway (router) instead that the Internet.
I am stuck !!

Anyone can help ?

14 replies

by sgt_shultz

the clients need a static route set up for the as-400. that is all i can suggest, i only did it once and i can't remember how. get a command prompt and type route /? to see how it works.

by fashionlight

Hello,

though I thank you very much for your help, this was not enough to help me solve the problem. If you were a bit more precise on how to build that static route, then it would have helped me. Thank you anyways

by cg it

I would like some clarification on the internetwork topology.

How I interpret your description is that you have 1 LAN #1 in which clients on that LAN link to the another LAN #2 that the AS-400PC is on. This is accomplished via peer to peer connection.

You've determined that clients on LAN 1 need a internet connection and plan to accomplish this via ICS on a server in LAN 1. If you do this then clients can no longer link to the AS-400PC on LAN 2. You wish to use RRAS to filter packets destined for a specific IP [the AS-400PC] to use a specified route.

Your perimeter access router on LAN 1 [if it has 4 interfaces like Cisco Access Routers] should be able to route packets to solve your problem. Another suggestion would be to use a proxy server in lieu of ICS for internet connection sharing [something like ISA server 2004. Note: ISA 2000 does not have this capability but 2004 does].

your problem stems from having to change default gateway out addressing for the LAN to accomplish ICS. This method may cause more headaches that seting up a perimeter router to route packets.

by fashionlight

I unfortunately have no access to the perimeter router :-( That is my main issue otherwise I would have solved things differently like also stated by you. I didn't think about adding a proxy on the server, which is an excellent idea, so I can leave the gateway of the clients unmodified instead of changing it to the server's IP for Internet sharing; before adding a proxy server though I would like to make sure that there is no other solution to this through the RRAS server.

I tried to add a static route on the server so that all traffic to the remote network be addressed to the router instead of the internet but it didn't work...

The string I used was:
route add 192.168.200.0 mask 255.255.255.0 192.168.2.1 metric 1

Does anyone know what I am doing wrong? If there is no solution, I will accept your answer CG IT, so please post here again !!

by cg it

there are "ways" in which to make a connection over different "paths" for programs. Unfortunately, using only 1 NIC [one path] the methods aren't "automatic" paths but require user intervention. Without a "router" which would simplfy this, I'm afraid trying to configure RRAS to "route" traffic over a different path when only 1 is present isnna gonna work well [probably not at all] unless you can route at the application layer [e.g. by port]. if you can route at the application layer then your problem is solved in connecting over the internet to your remote AS-400PC as well as providing ICS but that would require you to disable the peer to peer hookup and strickly use the internet.

only other way is to multihome everthing so that there are 2 paths.

by cg it

when I say multihome everything, clients need to be multihomed. One path for ICS and one path for the peer to peer connection.

by cg it

NICs don't provide multiple gateway selection. Routers do which is why it would be easier to go that route [and RRAS though a quasi router isn't setup to handle with multiple path routing with only 1 connection line]. Multihome solves the problem but can cause more problems in that traffic over the LAN can get congested and data loss can get excessive [not to mention that Windows client O/Ss generally don't like a multihomed environment.

by cg it

thats why Cisco, 3Com, etc commercial routers have multiple ethernet ports, PPP serial ports, Frame Relay ports, etc so that multiple paths can be configured just for the senario you describe. ISA server 2004 [$1500 USD] can also do this using multiple NICS [3 or more] [ISA 2000 can not].

This discussion is closed to new replies.