|
Home > Archive > alt.certification.network-plus > June 2002 > Gateway and routing question...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Gateway and routing question...
|
|
| Jon A. Schmuland 2002-06-24, 6:44 pm |
| Hi all. This problem seems a little convoluted, but it's really quite
straight forward. With the exception of the simple solution.
Here's the setup: (all machines are win98 peer to peer)
One main computer w/ two NIC's. One nic is private LAN (192.168.0.1)
connected to another machine via crossover cable.
The other NIC in the main computer is DSL into a switch. Connected to the
switch is another machine (192.168.0.150). That machine has one NIC w/ two
IP's (one static and one dynamic for DSL, also).
You follow?
left computer (192.168.0.150)--normcable--{main ( DSL
/192.168.0.1)}--xovercable--right computer(192.168.0.101)
The main machine can see all three computers in Network Neighborhood.
The right machine (192.168.0.150) can see itself and the main.
The left machine (192.168.0.101) can see itself and the main.
But what I wanna do is be at 192.168.0.150 and access 192.168.0.101.
Now, I KNOW there is an easier way to do it and I could use different
protocols and all that. I'm trying to practically create what I read about
in a networking book. If the "gateway" is the main computer, I should be
able to access all three machines from any location.
Sadly, I can't. Sorry this is so long winded, but I want to figure out this
problem.
Any takers on this one?
Cheers.
--
Jon
| |
| Andy Barkl 2002-06-24, 6:44 pm |
| "Jon A. Schmuland" <jschmuland@hotmail.com> wrote in message
news:l3sO8.18074$mh.722717@news1.telusplanet.net...
> Hi all. This problem seems a little convoluted, but it's really quite
> straight forward. With the exception of the simple solution.
>
> Here's the setup: (all machines are win98 peer to peer)
>
> One main computer w/ two NIC's. One nic is private LAN (192.168.0.1)
> connected to another machine via crossover cable.
>
> The other NIC in the main computer is DSL into a switch. Connected to the
> switch is another machine (192.168.0.150). That machine has one NIC w/
two
> IP's (one static and one dynamic for DSL, also).
>
> You follow?
> left computer (192.168.0.150)--normcable--{main ( DSL
> /192.168.0.1)}--xovercable--right computer(192.168.0.101)
>
> The main machine can see all three computers in Network Neighborhood.
>
> The right machine (192.168.0.150) can see itself and the main.
> The left machine (192.168.0.101) can see itself and the main.
>
> But what I wanna do is be at 192.168.0.150 and access 192.168.0.101.
>
> Now, I KNOW there is an easier way to do it and I could use different
> protocols and all that. I'm trying to practically create what I read
about
> in a networking book. If the "gateway" is the main computer, I should be
> able to access all three machines from any location.
>
> Sadly, I can't. Sorry this is so long winded, but I want to figure out
this
> problem.
>
> Any takers on this one?
>
> Cheers.
> --
> Jon
Since the main machine is not designated as a router you could change the
subnet of either the left or right machine to something like 192.168.1.x and
then add a static route command to both that machine and the main machine,
with the route add command at the command line.
| |
| Jon A. Schmuland 2002-06-24, 6:44 pm |
| I follow *some* of what you're talking about. Can you give me an example,
or do you have a link to a good "step by step" kinda resource?
Are you suggesting instead of a 255.255.255.0 subnet on the left and right
machines, I put the main machine's IP?
"Andy Barkl" <abarkl@NOSPAM.wetrainit.com> wrote in message
news:hrsO8.21944$3R2.663240@news1.west.cox.net...
> "Jon A. Schmuland" <jschmuland@hotmail.com> wrote in message
> news:l3sO8.18074$mh.722717@news1.telusplanet.net...
> > Hi all. This problem seems a little convoluted, but it's really quite
> > straight forward. With the exception of the simple solution.
> >
> > Here's the setup: (all machines are win98 peer to peer)
> >
> > One main computer w/ two NIC's. One nic is private LAN (192.168.0.1)
> > connected to another machine via crossover cable.
> >
> > The other NIC in the main computer is DSL into a switch. Connected to
the
> > switch is another machine (192.168.0.150). That machine has one NIC w/
> two
> > IP's (one static and one dynamic for DSL, also).
> >
> > You follow?
> > left computer (192.168.0.150)--normcable--{main ( DSL
> > /192.168.0.1)}--xovercable--right computer(192.168.0.101)
> >
> > The main machine can see all three computers in Network Neighborhood.
> >
> > The right machine (192.168.0.150) can see itself and the main.
> > The left machine (192.168.0.101) can see itself and the main.
> >
> > But what I wanna do is be at 192.168.0.150 and access 192.168.0.101.
> >
> > Now, I KNOW there is an easier way to do it and I could use different
> > protocols and all that. I'm trying to practically create what I read
> about
> > in a networking book. If the "gateway" is the main computer, I should
be
> > able to access all three machines from any location.
> >
> > Sadly, I can't. Sorry this is so long winded, but I want to figure out
> this
> > problem.
> >
> > Any takers on this one?
> >
> > Cheers.
> > --
> > Jon
>
> Since the main machine is not designated as a router you could change the
> subnet of either the left or right machine to something like 192.168.1.x
and
> then add a static route command to both that machine and the main machine,
> with the route add command at the command line.
>
>
| |
| Andy Barkl 2002-06-24, 6:44 pm |
| "Jon A. Schmuland" <jschmuland@hotmail.com> wrote in message
news:AltO8.23230$vo2.749096@news2.telusplanet.net...
> I follow *some* of what you're talking about. Can you give me an example,
> or do you have a link to a good "step by step" kinda resource?
>
> Are you suggesting instead of a 255.255.255.0 subnet on the left and right
> machines, I put the main machine's IP?
Don't change anything on each machine except for the subnet number (if you
are using 192.168.0.x with a mask of 255.255.255.0, and you change the range
to 192.168.1.x, it's a different subnet), set the left machine to
192.168.1.x and the main machine's card which is connected to that machine
to 192.168.1.x with the same mask of 255.255.255.0.
Then add the static route at both the main machine and the left machine for
the 192.168.0.x network. Also there is no need for gateway values on any
machine.
|
|
|
|
|