Re: Can XP bridge 2 private networks?
From: Ron Lowe (ron-msng_at_{d.e.l.e.t.e.}lowe-family.me.uk)
Date: 06/29/04
- Next message: Lanwench [MVP - Exchange]: "Re: Dameware and PING to Windows XP workstations does not work"
- Previous message: Bryan Linton: "Add'l Info: Can't Copy Local Profile"
- In reply to: Jim S. Greathouse: "Can XP bridge 2 private networks?"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Can XP bridge 2 private networks?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 29 Jun 2004 16:55:12 +0100
"Jim S. Greathouse" <jim_greathouse@hotmail.com> wrote in message
news:a7a6545b.0406290624.6dab2460@posting.google.com...
> Hi,
>
> We have an XP box that is connected to 2 seperate private networks
> (each has a 48 port switch) -- the first is using 10.20.30.xx
> addresses while the second is using 192.168.100.xx addresses.
>
> I would like to bridge these connections so that machines on the
> 192.168.100.xx network can see the 10.20.30.xx machines.
>
> Bridging the two connections by selecting both networks and then
> telling XP to bridge breaks both networks. The XP box cannot
> communicate with any address in the 10.20.30.xx or 192.168.100.xx
> space. Reverting to an earlier restore point restores the
> connectivity.
>
> Can XP bridging be used to connect these two private networks?
>
> Thanks,
>
> Jim
Bridging is not what you need to join 2 different IP subnets.
You need a router.
To span 2 different subnets, you need to enable IP forwarding.
The XP box will need 2 LAN cards, one connected to each switch.
Give each NIC an IP address in the appropriate subnet.
( Let's say 192.168.100.254 and 10.20.30.254. )
Then enable IP forwarding between the interfaces:
http://support.microsoft.com/?kbid=315236
This turns the XP box into a router.
Now, all the machines need to be told about the router...
On all the machines on the 192.168.100 network, you need to
set up a static route which points to the 10.20.30 network via the XP
box at 192.168.100.254:
route -p add 10.20.30.0 mask 255.255.255.0 192.168.0.254
Do a route print, and check for the persistent route.
Then, on all the machines on the 10.20.30 network, you need to
set up a static route which points to the 192.168.100 network via the XP
box at 10.20.30.254:
route -p add 192.168.100.0 mask 255.255.255.0 10.20.30.254
Do a route print, and check for the persistent route.
You should now be able to ping by IP address between the subnets.
You will now need to fix up cross-subnet name resolution.
Assuming you don't have a WINS server or DNS servers,
then you will need to use static name resolution.
To enable NetBIOS name resolution between the machines, you will
need to create an LMHOSTS file.
To enable DNS resolution, you need to create a HOSTS file.
You should then be able to ping by name, and map drives by name.
You will not be able to browse across the subnets, since browsing relies
on NetBIOS broadcasts which don't cross the router.
To make cross-subnet browsing work, you need a Domain, which will set
up a Domain Master Browser which can collate the individual subnet
Segment Browse Lists, and concatenate them into a domain-wide browse list.
That is beyond the topic of this post :-)
-- Best Regards, Ron Lowe MS-MVP Windows Networking
- Next message: Lanwench [MVP - Exchange]: "Re: Dameware and PING to Windows XP workstations does not work"
- Previous message: Bryan Linton: "Add'l Info: Can't Copy Local Profile"
- In reply to: Jim S. Greathouse: "Can XP bridge 2 private networks?"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Can XP bridge 2 private networks?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
