Re: Network Hardware
- From: Chuck <none@xxxxxxxxxxx>
- Date: Wed, 01 Mar 2006 21:59:51 -0800
On Thu, 02 Mar 2006 04:55:21 GMT, "Troy" <Troy.Kranz@xxxxxxxxx> wrote:
Hi!
I wrote the story below before I read PChuck's article "File Sharing On A
LAN With Two Routers" and now wonder whether or not to send this message as
File Sharing and Remote Connection are two tasks I still want to be able to
do after separating LAN into subnets, as well as maybe Print Sharing.
I don't know if this is the correct forum for a question like this and
please redirect me if you can.
I have a network operating between two houses that are about 900 Metres
apart. The setup is this:
PCs are all XP Pro.
(House1) PCs <--> Switch <--> AP (Point to Point) <--> Roof Antenna
((((( )))) (House2) Roof Antenna <--> AP (Point to Point)<--> Switch <-->
PCs and Internet(Router/Modem Combo). Currently all devices are the one LAN
(all addresses in the 192.168.0.x 255.255.255.0 subnet).
I was thinking that to keep the traffic off the APs (why? Just because and
to learn stuff) I could create two subnets at each house and place a
Router/Switch (I have two spares Vigor 2104P and Dlink DI-524) between the
switch and the AP at each house. I was also hoping to use the DLink Router
to limit the times that the kids could access the internet as they would
have to go through the router to get to the internet on the other subnet.
In order to test this theory I have setup the following at my house:
PC1 <--> Router/Switch(DLink) <--> Router/Switch(Vigor) <--> Switch <-->
PC2-3 and Internet(Router/Modem Combo).
WAN Port on DLink Router connected to LAN Port1 on Vigor Router
PC1=192.168.3.2 255.255.255.0 gateway = 192.168.3.1
DLink Router LAN = 192.168.3.1 255.255.255.0 WAN = 192.168.0.137 (I just
picked this ip randomly on the 2nd Subnet)
WAN Port on Vigor Router not yet connected
Vigor Router LAN = 192.168.0.1 255.255.255.0 WAN = not yet setup
PC2 = 192.168.0.11 255.255.255.0 Gateway=192.168.0.138
PC3 = 192.168.0.12 255.255.255.0 Gateway=192.168.0.138
Internet Router/Modem = 192.168.0.138
With this setup I can ping the 192.168.0.0 subnet from 192.168.3.0 subnet
but I can't access the internet(Can ping 192.168.0.138). I am hoping this is
because I have not yet set up the return leg of that journey(ie WAN port on
vigor to Lan port on DLink).
I have searched on the internet for a lot of information on what I am trying
to do and what I have found tends to deal with routing a private Lan onto
the internet and not really about routing between private subnets. I may
have stumbled across sites that deal with what I am trying to do but maybe
it was at a level above my current understanding.
Anyway these are some of my question/s.
Q1. Am I on the right track with these ideas?
Q2. How do I connect the two routers together? eg. WAN to WAN port with
crossover or WAN to LAN on both Routers
Q3. Should these routers do the job?
Q4. When I move to the original setup will I have to configure Access Points
on their own subnet?
Q5. Could this be done with less equipment?
Q6. I have heard the phrase 192.168.x.x addresses are private and non
routable addresses. Does this mean that they should not be routed or that
they cannot be routed or is it another meaning all together?
Thanks in advance
Troy
Troy,
I see your problem, I think. On your main LAN, 192.168.0/24, the default
gateway is 192.168.0.138. On your DLink LAN, 192.168.3/24, the default gateway
is 192.168.3.1. Now, you need to define a default gateway for the DLink to use,
on its WAN connection, to connect to the Internet.
Without a default gateway assigned to the DLink WAN, any Internet traffic from
PC1 goes to its default gateway 192.168.3.1, and to the DLink WAN, and onto the
main LAN. And there it stays. The DLink WAN has to have a default gateway
defined, so the Internet traffic that it gets thru its LAN, 192.168.3.1, will go
thru 192.168.0.138. For the DLink, as for the computers on the main LAN, the
default gateway will be 192.168.0.138.
Q1 / Q2. The routers are connected properly. When you get this working, you'll
be moving all of your computers to the DLink LAN, and they will all be able to
share files. Just set the default gateway for the DLink to 192.168.0.138.
Q3. These routers should do the job.
Q4. Why do you wish to move to the original setup?
Q5. I'm not sure what you're accomplishing with the Vigor setup as a switch,
and connected to another switch. Are the Vigor and the switch located in the
same place, or are they separate?
Q6. The subnet 192.168.x.x is private (non-routable) so that it can be used on
any private (non-routed) LAN in the world, without fear of being duplicated by
any public LAN anywhere in the world. You can only use 192.168.x.x behind a NAT
router. A NAT router handles the entire 192.168.x.x subnet privately, and the
world sees only the WAN address. In your case, for instance, your main LAN sees
192.168.0.137, and that address is translated by the DLink into the 192.168.3.x
subnet.
Please let me know, at your earliest convenience, if these answers are
understandable. It would be hella easier to setup your network, then to explain
it.
--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.
- Follow-Ups:
- Re: Network Hardware
- From: Troy
- Re: Network Hardware
- References:
- Network Hardware
- From: Troy
- Network Hardware
- Prev by Date: Re: running out of letters for mapped drives?
- Next by Date: xp home workgroup/ xp pro domain network problems
- Previous by thread: Network Hardware
- Next by thread: Re: Network Hardware
- Index(es):
Relevant Pages
|
