Connecting to two networks

  • Thread starter Thread starter Mike Hyndman
  • Start date Start date
M

Mike Hyndman

Is it possible to connect to two networks at the same time, one
connecting to a peer to peer network via LAN card; the other connection
via wireless to an NT domain/ XP Pro workgroup? Both networks use static
IP addresses.
The offices at my school have a small peer to peer network (3 PC's),
whilst the rest of the school has a domain/workgroup wired installation
(<30 PC's) with some wireless access points. I have a laptop which has a
built in wireless card as well as a LAN card which I would like to
connect to both if possible.
TIA
Mike H
remove -bats- to reply
 
Is it possible to connect to two networks at the same time, one
connecting to a peer to peer network via LAN card; the other connection
via wireless to an NT domain/ XP Pro workgroup? Both networks use static
IP addresses.
The offices at my school have a small peer to peer network (3 PC's),
whilst the rest of the school has a domain/workgroup wired installation
(<30 PC's) with some wireless access points. I have a laptop which has a
built in wireless card as well as a LAN card which I would like to
connect to both if possible.
Click to expand...


PP and Workgroup are the same thing.

No, either you are Domain or WG, but not both at the same time, unless
u use something like Virtual PC. Two OS in the same box and running
concurrently.
 
Mike said:
Is it possible to connect to two networks at the same time, one
connecting to a peer to peer network via LAN card; the other connection
via wireless to an NT domain/ XP Pro workgroup? Both networks use static
IP addresses.
The offices at my school have a small peer to peer network (3 PC's),
whilst the rest of the school has a domain/workgroup wired installation
(<30 PC's) with some wireless access points. I have a laptop which has a
built in wireless card as well as a LAN card which I would like to
connect to both if possible.
TIA
Mike H
remove -bats- to reply
Click to expand...

to what end?

you ought to be able to move files around with, e.g., ftp, regardless of
whether Windows is willing to play nice with both subnets at once
 
Yes. You'll need to log into the domain in order to access domain resources,
but you can still browse and connect to the workgroup resources on the other
LAN. The only requirement is that the two be on different subnets. Set your
domain side network card up (TCP/IP Properties) with the full compliment of
settings (IP address, Mask, Gateway, DNS, WINs if required), on the
workgroup side, just fill out the IP address and subnet mask. No default
gateway or other settings. In your browser (My Network Places), you'll have
to drill down through "Entire Network -> Microsoft Windows Network" to see
computers in the workgroup. If this fails, you'll need to connect using IP
addresses. You can make shortcuts to workgroup shares by right-clicking on
your desktop or in a folder, selecting "New -> Shortcut", and typing the UNC
path to a workgroup computer, i.e. \\192.168.10.5. Then you can name the
shortcut according to the computer name it refers to, i.e. "Workgroup
Server". This is also a good place to utilize "Poor Man's DFS". Create a
share on a Workgroup computer, Put shortcuts to all other workgroup
resources in the shared folder (file share, printers, etc), and a shortcut
to the folder containing the other shortcuts on each workgroup computer's
desktop. Then any time you add a shortcut to the shared folder, everyone
immediately has access to it via their desktop shortcut. Note that the
shortcuts must ALL refer to UNC paths.

....kurt
 
Yes. You'll need to log into the domain in order to access domain resources,
but you can still browse and connect to the workgroup resources on the other
LAN. The only requirement is that the two be on different subnets. Set your
domain side network card up (TCP/IP Properties) with the full compliment of
settings (IP address, Mask, Gateway, DNS, WINs if required), on the
workgroup side, just fill out the IP address and subnet mask. No default
gateway or other settings. In your browser (My Network Places), you'll have
to drill down through "Entire Network -> Microsoft Windows Network" to see
computers in the workgroup. If this fails, you'll need to connect using IP
addresses. You can make shortcuts to workgroup shares by right-clicking on
your desktop or in a folder, selecting "New -> Shortcut", and typing the UNC
path to a workgroup computer, i.e. \\192.168.10.5. Then you can name the
shortcut according to the computer name it refers to, i.e. "Workgroup
Server". This is also a good place to utilize "Poor Man's DFS". Create a
share on a Workgroup computer, Put shortcuts to all other workgroup
resources in the shared folder (file share, printers, etc), and a shortcut
to the folder containing the other shortcuts on each workgroup computer's
desktop. Then any time you add a shortcut to the shared folder, everyone
immediately has access to it via their desktop shortcut. Note that the
shortcuts must ALL refer to UNC paths.

...kurt
Click to expand...
Many thanks to all for your replies, something to think about. The PP
network (LAN) has the address range 10.74.101.* 255.0.0.0 subnet and the
domain NW has the address range 10.74.27.* subnet 255.255.255.0
(Wireless) The XPPro PC's on this network do not log on to the domain,
they just use a shortcut to it to access the folders/files they need to
use.
remove -bats- to reply
 
The PP network (LAN) has the address
range 10.74.101.* 255.0.0.0 subnet
Click to expand...

A subnet mask of 255.0.0.0 is the entire Class A 10.0.0.0 network, there are
no divisions into subnets. If you only need access to the 10.74.101.x
network, you can shorten up the subnet mask to 255.255.255.0, which would
put the other LAN on the 10.74.27.0 network on a different subnet. But it
sounds like both networks are already connected? If both LANs are connected,
there's no need for two network cards or anything else. You just need an IP
address within the range of the 10.27.74.0 network and you will be able to
access both on the same NIC (barring access-lists, VLANs, etc.).

....kurt
 
A subnet mask of 255.0.0.0 is the entire Class A 10.0.0.0 network, there are
no divisions into subnets. If you only need access to the 10.74.101.x
network, you can shorten up the subnet mask to 255.255.255.0, which would
put the other LAN on the 10.74.27.0 network on a different subnet. But it
sounds like both networks are already connected? If both LANs are connected,
there's no need for two network cards or anything else. You just need an IP
address within the range of the 10.27.74.0 network and you will be able to
access both on the same NIC (barring access-lists, VLANs, etc.).
Click to expand...
Many thanks Kurt,

I'm almost positive that the PP mask is as stated, but will check on
Monday. I'm assured that the two networks are totally independant, the
only place I thought they may share was the gateway to the proxy server,
but the differing IP's ruled that out.
again many thanks.
Mike H
remove -bats- to reply
 
Mike Hyndman skrev:
Many thanks Kurt,

I'm almost positive that the PP mask is as stated, but will check on
Monday. I'm assured that the two networks are totally independant, the
only place I thought they may share was the gateway to the proxy server,
but the differing IP's ruled that out.
again many thanks.
Mike H
remove -bats- to reply
Click to expand...

hi

i use two ip right now! connected to a router with two wan ports.
linksys rv042, made for small networks. can be used as gateway or router!

http://www.linksys.com/products/product.asp?grid=34&scid=29&prid=639

tia coco
 
Mike Hyndman skrev:
Yo CoCo,

Thanks for the info, looks interesting.
Many Thank.
Mike H
remove -bats- to reply
Click to expand...

hi a small varning about this router! if you have a lot of ports active this thing will
limit your speed!!
 
Back
Top