Linking two networks with internet connections

Hi

I have two networks at home, each with their own internet connection.
I'd like to link the two networks up so that I can share files between
computers on either network, but for the computers to only use the
internet connection via the router they are connected to--not to use
the connection on the other network.

Is this possible? The routers for each network are:

1. Linksys Wireless-G ADSL Home Gateway
2. Belkin (Model Number: F5D7632-4)

Any help would be much appreciated. Thank you.

(E-Mail Removed) declared for all the world to hear...
> Hi
>
> I have two networks at home, each with their own internet connection.
> I'd like to link the two networks up so that I can share files between
> computers on either network, but for the computers to only use the
> internet connection via the router they are connected to--not to use
> the connection on the other network.
>
> Is this possible? The routers for each network are:
>
> 1. Linksys Wireless-G ADSL Home Gateway
> 2. Belkin (Model Number: F5D7632-4)
>
> Any help would be much appreciated. Thank you.

On all of your PCs, specify manual IP addresses, and whilst doing so
specify the the IP of the router you want it to go out to the internet
as the GATEWAY IP in the tcp/ip properties. They will then all be able
to talk to each other, but anything external will go out via the router
you specify.
--
Regards
Jon

"David" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> I have two networks at home, each with their own internet connection.
> I'd like to link the two networks up so that I can share files between
> computers on either network, but for the computers to only use the
> internet connection via the router they are connected to--not to use
> the connection on the other network.
>
> Is this possible? The routers for each network are:
>
> 1. Linksys Wireless-G ADSL Home Gateway
> 2. Belkin (Model Number: F5D7632-4)

Yes, it is possible to do what you want, but you will almost certainly have
to use static IP configuration for at least some computers. I think it is
worth pointing out that it is probably impossible to prevent computers that
should use router 1 from using router 2 and vice-versa.

In terms of the physical network, all you need to do is connect the two
routers together via their LAN ports. This can be either directly, with a
single cable (a crossover cable may be needed, but a straight one will
probably work), or via a hub or switch(es).

Both routers need their LAN-side interfaces configured with unique addresses
in the same range. At least one router must have its DHCP server disabled.
Then all PCs need to be configured with addresses in the same range, and
their default gateway set to the appropriate router. For example:

Router 1 LAN-side interface IP address/mask: 192.168.0.1/255.255.255.0
Router 1 DHCP server: enabled, pool 192.168.0.10-192.168.0.127
Router 2 LAN-side interface IP address/mask: 192.168.0.2/255.255.255.0
Router 2 DHCP server: disabled
PCs to use router 1: use DHCP (automatically assign IP address & DNS server)
PCs to use router 2: manual IP address 192.168.0.128-192.168.0.254, subnet
mask 255.255.255.0, DNS server 192.168.0.2 (or those of the ISP router 2
connects to).

Alex

On Tue, 14 Aug 2007 17:34:28 +0100, "Alex Fraser" <(E-Mail Removed)>
mused:

>"David" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed) oups.com...
>> I have two networks at home, each with their own internet connection.
>> I'd like to link the two networks up so that I can share files between
>> computers on either network, but for the computers to only use the
>> internet connection via the router they are connected to--not to use
>> the connection on the other network.
>>
>> Is this possible? The routers for each network are:
>>
>> 1. Linksys Wireless-G ADSL Home Gateway
>> 2. Belkin (Model Number: F5D7632-4)
>
>Yes, it is possible to do what you want, but you will almost certainly have
>to use static IP configuration for at least some computers. I think it is
>worth pointing out that it is probably impossible to prevent computers that
>should use router 1 from using router 2 and vice-versa.
>
Could you not stick something in the hosts file as well to route
external traffic to the router? Saves the `fiddlers` altering the
settings at least.
--
Regards,
Stuart.

In article <(E-Mail Removed) >, Alex
Fraser says...
> "David" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ups.com...
> > I have two networks at home, each with their own internet connection.
> > I'd like to link the two networks up so that I can share files between
> > computers on either network, but for the computers to only use the
> > internet connection via the router they are connected to--not to use
> > the connection on the other network.
> >
> > Is this possible? The routers for each network are:
> >
> > 1. Linksys Wireless-G ADSL Home Gateway
> > 2. Belkin (Model Number: F5D7632-4)
>
> Yes, it is possible to do what you want, but you will almost certainly have
> to use static IP configuration for at least some computers.

You don't need to use static IP addresses - merely enter the default
gateway.

Another option is to use a non routable protocol such as NetBEUI for
File and Printer sharing and disassociate TCP/IP from Client for
Microsoft Networksa.


--
Conor

The United States, increasing quality by lowering standards since 1776.

"Conor" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) t...
> In article <(E-Mail Removed) >, Alex
> Fraser says...
>> "David" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed) ups.com...
>> > I have two networks at home, each with their own internet connection.
>> > I'd like to link the two networks up so that I can share files between
>> > computers on either network, but for the computers to only use the
>> > internet connection via the router they are connected to--not to use
>> > the connection on the other network.
[snip]
>> Yes, it is possible to do what you want, but you will almost certainly
>> have to use static IP configuration for at least some computers.
>
> You don't need to use static IP addresses - merely enter the default
> gateway.

On Windows, as far as I can tell, using DHCP means a route for the default
gateway will be added if one is provided in the DHCP response. It seems that
the OP wants the computer to only use the entered route and never the one
discovered via DHCP, but it appears impossible to guarantee this.

> Another option is to use a non routable protocol such as NetBEUI for
> File and Printer sharing and disassociate TCP/IP from Client for
> Microsoft Networksa.

I can't see the advantage. Can you elaborate?

Alex

"Lurch" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Tue, 14 Aug 2007 17:34:28 +0100, "Alex Fraser" <(E-Mail Removed)>
> mused:
>>"David" <(E-Mail Removed)> wrote in message
>>news:(E-Mail Removed) roups.com...
>>> I have two networks at home, each with their own internet connection.
>>> I'd like to link the two networks up so that I can share files between
>>> computers on either network, but for the computers to only use the
>>> internet connection via the router they are connected to--not to use
>>> the connection on the other network.
[snip]
>>Yes, it is possible to do what you want, but you will almost certainly
>>have to use static IP configuration for at least some computers. I think
>>it is worth pointing out that it is probably impossible to prevent
>>computers that should use router 1 from using router 2 and vice-versa.
>
> Could you not stick something in the hosts file as well to route
> external traffic to the router? Saves the `fiddlers` altering the
> settings at least.

The hosts file has nothing to do with routing, so not that way. You can stop
"fiddling" to some extent with Windows 2k and later, if the users don't have
administrative rights.

Alex

On Tue, 14 Aug 2007 19:07:43 +0100, "Alex Fraser" <(E-Mail Removed)>
mused:

>"Lurch" <(E-Mail Removed)> wrote in message
>news:(E-Mail Removed).. .
>> On Tue, 14 Aug 2007 17:34:28 +0100, "Alex Fraser" <(E-Mail Removed)>
>> mused:
>>>"David" <(E-Mail Removed)> wrote in message
>>>news:(E-Mail Removed) groups.com...
>>>> I have two networks at home, each with their own internet connection.
>>>> I'd like to link the two networks up so that I can share files between
>>>> computers on either network, but for the computers to only use the
>>>> internet connection via the router they are connected to--not to use
>>>> the connection on the other network.
>[snip]
>>>Yes, it is possible to do what you want, but you will almost certainly
>>>have to use static IP configuration for at least some computers. I think
>>>it is worth pointing out that it is probably impossible to prevent
>>>computers that should use router 1 from using router 2 and vice-versa.
>>
>> Could you not stick something in the hosts file as well to route
>> external traffic to the router? Saves the `fiddlers` altering the
>> settings at least.
>
>The hosts file has nothing to do with routing, so not that way.

Maybe I'm thinking of somethign else, there is something that defines
routing and gateways in some sort of fashion, if only I could remember
what it was.

>You can stop
>"fiddling" to some extent with Windows 2k and later, if the users don't have
>administrative rights.
>
Probably the easiest way if it's possible.
--
Regards,
Stuart.

On 14 Aug, 20:54, Lurch <myrealn...@sjwelectrical.co.uk> wrote:
> On Tue, 14 Aug 2007 19:07:43 +0100, "Alex Fraser" <m...@privacy.net>
> mused:
>
>
>
> >"Lurch" <myrealn...@sjwelectrical.co.uk> wrote in message
> >news:(E-Mail Removed).. .
> >> On Tue, 14 Aug 2007 17:34:28 +0100, "Alex Fraser" <m...@privacy.net>
> >> mused:
> >>>"David" <i.davidwin...@googlemail.com> wrote in message
> >>>news:(E-Mail Removed) groups.com...
> >>>> I have two networks at home, each with their own internet connection.
> >>>> I'd like to link the two networks up so that I can share files between
> >>>> computers on either network, but for the computers to only use the
> >>>> internet connection via the router they are connected to--not to use
> >>>> the connection on the other network.
> >[snip]
> >>>Yes, it is possible to do what you want, but you will almost certainly
> >>>have to use static IP configuration for at least some computers. I think
> >>>it is worth pointing out that it is probably impossible to prevent
> >>>computers that should use router 1 from using router 2 and vice-versa.
>
> >> Could you not stick something in the hosts file as well to route
> >> external traffic to the router? Saves the `fiddlers` altering the
> >> settings at least.
>
> >The hosts file has nothing to do with routing, so not that way.
>
> Maybe I'm thinking of somethign else, there is something that defines
> routing and gateways in some sort of fashion, if only I could remember
> what it was.
>
> >You can stop
> >"fiddling" to some extent with Windows 2k and later, if the users don't have
> >administrative rights.
>
> Probably the easiest way if it's possible.
> --
> Regards,
> Stuart.

You are probably thinking of the ROUTE ADD command from a command box.
That enables you to apply a static route for a specific destination
that is different to that offered by DHCP or TCP/IP configuration. the
only drawback with this is it has a habit of only living for as long
as the PC isn't rebooted. So to ensure it stays in existence you
probably need a command (.cmd) file run on startup from within the
registry as it would be too late to leave it to a user startup.

Neil

On Thu, 06 Sep 2007 10:32:27 -0700, (E-Mail Removed) wrote:


>You are probably thinking of the ROUTE ADD command from a command box.
>That enables you to apply a static route for a specific destination
>that is different to that offered by DHCP or TCP/IP configuration. the
>only drawback with this is it has a habit of only living for as long
>as the PC isn't rebooted. So to ensure it stays in existence you
>probably need a command (.cmd) file run on startup from within the
>registry as it would be too late to leave it to a user startup.

/p on the end of the route add command will cause the route to be
persistant. Persistant routes will be restored on reboot, and are
listed separately when route print is run.