Re: way OT: route table

From: Phil S. (nospam-m-phil-NoSpam_at_123.net)
Date: 04/02/04 

Date: Fri, 2 Apr 2004 12:25:12 -0500

NIC:

Here is my $0.02:

first try
route -p add 32.76.0.0 mask 255.255.0.0 192.168.16.1
but don't forget you need the routing tables set up in your
access router also. Both ends. And both ways. This should
get ping to work. DNS, is another post.

You have your internal IP range of 192.168.16.0
your access router (CSU/DSU interface) has an interface on
your local network as 192.168.16.1 (I think this is what you
implied in your post.)

IP routing of the data packets happens in your access
router and the external address is probably 192.186.0.1

on the other side of the point-to-point is another access router with
an address pointing to you with something like 192.186.0.2 or something.
(what ever it is, it must be within the mask of the two access router
external IP address.)

Another IP routing of data packets takes place inside the remote access
router and the local interface of the remote access router will probably be
something like 32.76.0.1

You set up your local routing table to forward all 32.76.X.X to the local
interface on your access router.
The local access router should have its route table setup
to forward all 32.76.X.X to the remote access router.
the remote access router should know to pass all
32.76.X.X to the remote local interface.

If it is setup correctly, the remote site could have a different
IP Scheme at the local interface of the remote access router,
but as long as the routing tables along the way know to keep
passing 32.76.X.X along to the next router, your packet should
get to network 32.76.X.X.

I hope this is not too confusing. Just remember, the routing
tables must be set up to find your local IP Scheme also.

Phil S.

"nic" <anonymous@discussions.microsoft.com> wrote in message
news:1783b01c418d1$74bc3760$a401280a@phx.gbl...
> I'm not sure who to ask. If any of you know of a better
> newsgroup just let me know.
>
> OK, we are running SBS 2000 with an internal IP network of
> 192.168.16.0 (net mask 255.255.255.0, gateway
> 192.168.16.1). We have a need to add a frame-relay point
> to point connection with another company. This uses a
> completely different router and is on a seperate network
> of 192.168.0.0 (net mask 255.255.255.0, gateway
> 192.168.0.1) This will give us a private connection to
> their network. On their network I have to reach one of
> their servers (32.76.xx.xx). I was told I could add a
> static route in the route table to access the private
> network. (I have a server that needs to be on the main
> network but still access the private network)
>
> I tried adding a static route of
> >>route add 192.168.0.0 mask 255.255.255.0 192.168.0.1
>
> This fails saying the interface could not be found. If on
> that machine, I change my IP to go to the private network,
> I can successfully ping the gateway. But how can I remain
> on the 192.168.16.0 network but still access the
> 192.168.0.1 gateway? I'm hoping there is a networking
> guru out there. I'm pretty sure it will involve a static
> route but i'm having trouble.
>
> Thanks