Re: please advise - problem with routing
From: Dana Brash (dbrash_at_Phongsaly.com)
Date: 10/18/04
- Next message: Andy: "NLB Load balancing with sessions"
- Previous message: Dana Brash: "Re: PDC Server Not Appearing Network Neighbourhood <-- Heavy Duty Help Required !"
- In reply to: andrew: "Re: please advise - problem with routing"
- Next in thread: andrew: "Re: please advise - problem with routing"
- Reply: andrew: "Re: please advise - problem with routing"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 18 Oct 2004 19:21:20 +0800
Hi Andrew,
>>I have 2 network 192.168.1.1 and 192.168.26.1 connected together by
>> router.
Actually, these are HOST addresses, not NETWORK addresses.
But working with the concept that we've got two subnets 192.168.1.x/24 and
192.168.26.x/24, you could accomplish this a couple different ways. The
first diagram below shows a literal interpretation of this statement. The
second diagram shows a different way that you could accomplish this. These
are by no means the only ways to do it....
If your config is different, please point out where.
>> > On first server 192.168.1.1 I have additional NIC 192.168.2.1 which is
>> used
>> > by some
>> > device.
What is that device? a printer? Wireless AP? Another comptuer? What is it's
purpose?
Not terribly important, but may be helpful to know...
>> >From 192.168.1.1 I can access that device since I checked IP
>> routing
>> > on that sever
Again, I will assume that this means from the 192.168.1.x/24 subnet you can
access the 192.168.2.x/24 subnet
How have you enabled routing on this device? Are you using RRAS? Static
Routes?
>> > and use 192.168.1.1 as a gateway,
As far as I can tell, this HOST IP address should be the private side of
your Internet Router, and not related to routing between the two internal
subnets
>> >but I cannot access that device from
> the
>> > second 192.168.26.1 network.
Right, you need to add the routes.
Below are some example setups, but again, I'm not too sure how you've got
your topology configured.
Again, there are many ways to accomplish what you're trying to do. Please
help us understand what you've actually done. Feel free to modify the
diagrams to draw us a picture.
HTH,
=d=
--
Dana Brash
MCSE, MCDBA, MCSA
dbrash@gmail.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In this diagram for packets from 192.168.26.x to reach 192.168.2.x, the
router needs to have a route entry that directs traffic to the
192.168.2.x/24 network via the 192.168.1.11 Gateway using ETH0
("/24" = "24 bit" = "255.255.255.0" subnet mask)
********************************************************
_____________
| Some Device |
|____________|
|
192.168.2.??/24
|
|
NIC2
192.168.2.x/24
_|_
| |
| | first server (Actually a router also)
|__|
|
NIC1
192.168.1.11/24
|
|
192.168.1.1/24 (let's say ETH0)
____|______
| ROUTER |----/\/\/---(ETH2)---/\/\/---->> INTERNET
|__________|
192.168.26.1/24 (let's say ETH1)
|
|
192.168.26.x/24
********************************************************
In this diagram for packets from 192.168.26.x to reach 192.168.2.x, ROUTER-2
will have a Route from 192.168.26.x/24 -> 192.168.2.x/24 via 192.168.1.11
Gateway using Interface 192.168.1.12 (RT2_ETH0).
There will also be a default route on Router2 that uses ROUTER1 ETH0 as the
default gateway.
===========================================================================
ON ROUTER2:
Network Destination Netmask Gateway Interface
Metric
. .
192.168.2.0 255.255.255.0 192.168.1.11 192.168.1.12
??
. .
Default Gateway: 192.168.1.1
===========================================================================
********************************************************
_____________
| Some Device |
|____________|
|
192.168.2.??/24
|
|
Server_NIC2
192.168.2.x/24
_|_
| |
| | first server (Actually a router also)
|__|
|
Server_NIC1
192.168.1.11/24
|
|
____\/____ __________
| Switch |--(RT1_ETH0)-->| ROUTER1 | --(RT1_ETH1)----->> INTERNET
|________| 192.168.1.1/24 |__________| PUBLIC IP
^
|
|
192.168.1.12/24(let's say RT2_ETH0)
|
____\/______
| ROUTER 2 |
|__________|
|
192.168.26.1/24 (let's say RT2_ETH1)
|
|
192.168.26.x/24
********************************************************
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
Dana Brash
MCSE, MCDBA, MCSA
dbrash@gmail.com
"andrew" <kc2ine@yahoo.com> wrote in message
news:%233SjBPLtEHA.2808@TK2MSFTNGP14.phx.gbl...
> Hi Mike,
> I use gateway 255.255.255.0 in both. The 192.168.26.1 is not on the
> server,
> this is separated remote network with router( GW 192.168.26.1) The
> problem
> is what gateway use to get to 192.168.2.1 network. I use 192.168.26.1 GW
> to
> get to 192.168.1.1 and this work.
> The NIC 192.168.2.1 is on the server 192.168.1.1 (second NIC)
> thanks, Andrew
>
> "Miha Pihler" <mihap-news@atlantis.si> wrote in message
> news:uh6LV8BtEHA.2660@TK2MSFTNGP12.phx.gbl...
>> Hi Andrew,
>>
>> You haven't told us the subnet mask that you use (in this case, this
>> would
>> be very important information).
>>
>> If you decided to use default subnet mask for 192.168.x.x network that
> would
>> be 255.255.255.0 (or 24 bit subnet mask). If we look at an example one
>> subnet would be:
>> 192.168.1.1 - 192.168.1.255 with 24 bit subnet mask. Second subnet would
> in
>> this case be
>> 192.168.2.1 - 192.168.2.255 with 24 bit subnet mask Third subnet would in
>> this case be
>> 192.168.3.1 - 192.168.3.255 with 24 bit subnet mask ....
>> .
>> .
>> .
>> 192.168.26.1 - 192.168.26.255 with 24 bit subnet mask
>> .
>> .
>> .
>> 192.168.255.1 - 192.168.255.255 with 24 bit subnet mask.
>>
>> In this case computers and devices in 192.168.1.x network will need a
>> gateway on 192.168.1.x subnet. Computers and devices in 192.168.2.x
> network
>> will need their gateway on 192.168.2.x subnet or will not be able to
> connect
>> to 192.168.1.x network (or anything outside 192.168.2.x network). And
>> computers and devices in 192.168.26.x network will need their gateway on
>> 192.168.26.x subnet...
>>
>> Gateway _must_ always be on same subnet as computers/devices are...
>>
>> If you have a server with 3 NIC with IPs 192.168.1.1 and 192.168.2.1 and
>> 192.168.26.1 this server will be able to connect to all three networks
> (but
>> only this server/device). It will use information from the NIC to build a
>> routing table.
>>
>> Such servers (and Windows computer) can have only one default gateway.
> This
>> would be the NIC that leads e.g. to the internet. E.g. if your NIC
>> 192.168.1.1 would be connected to the router that lead to the internet
> this
>> NIC would have a gateway.
>>
>> Mike
>>
>> "andrew" <kc2ine@yahoo.com> wrote in message
>> news:OsVm8RBtEHA.3052@tk2msftngp13.phx.gbl...
>> > hi,
>> > I have 2 network 192.168.1.1 and 192.168.26.1 connected together by
>> router.
>> > On first server 192.168.1.1 I have additional NIC 192.168.2.1 which is
>> used
>> > by some
>> > device. From 192.168.1.1 I can access that device since I checked IP
>> routing
>> > on that sever
>> > and use 192.168.1.1 as a gateway, but I cannot access that device from
> the
>> > second 192.168.26.1 network. Can somebody help? I cannot use the same
>> > gateway since this is different network.
>> >
>> >
>>
>>
>
>
- Next message: Andy: "NLB Load balancing with sessions"
- Previous message: Dana Brash: "Re: PDC Server Not Appearing Network Neighbourhood <-- Heavy Duty Help Required !"
- In reply to: andrew: "Re: please advise - problem with routing"
- Next in thread: andrew: "Re: please advise - problem with routing"
- Reply: andrew: "Re: please advise - problem with routing"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
