Making Two Lans?

  • Thread starter Thread starter W. Watson
  • Start date Start date
W

W. Watson

I have a typical LAN of three computere A,B, and C. A and B each have one
ethernet card. C has two. On the second of these, I somehow made LAN2. It
has a special ethernet device (10.0.0.1) that I needed connected to C. How I
made LAN2 a few months ago has escaped me. By going to the Control Panel
Network/Dial-up icon, I see a Make LAN icon, which wants a zip code and
phone #. This cannot be how I made LAN2. I suspect the presence of the
second ethernet card produced it. Is this right? If not, how does one do
this sort of thing?

Wayne T. Watson (Nevada City, CA)
 
W. Watson said:
I have a typical LAN of three computere A,B, and C. A and B each have
one ethernet card. C has two. On the second of these, I somehow made
LAN2. It has a special ethernet device (10.0.0.1) that I needed
connected to C. How I made LAN2 a few months ago has escaped me. By
going to the Control Panel Network/Dial-up icon, I see a Make LAN icon,
which wants a zip code and phone #. This cannot be how I made LAN2. I
suspect the presence of the second ethernet card produced it. Is this
right? If not, how does one do this sort of thing?

Wayne T. Watson (Nevada City, CA)
Click to expand...


right-click My network places, select properties. Your network
connections should be in there.

....kurt
 
I don't see how this helps me make a second LAN entry (icon) for the single
device that is not connected to the PC LAN.
 
You don't need to do that.
There is always an equal number of "LAN Connections" to the number of
Interfaces.
What "single device"?

Please explain clearly what you are doing and why. We can not help if we have to
play "Name that Mystery Function".

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed (as annoying as they are, and as stupid as they sound), are
my own and not those of my employer, or Microsoft, or anyone else associated
with me, including my cats.
-----------------------------------------------------
 
It's a video device. It has its own unique address that is apart from the PC
network. The PC with the device shows two LAN network icons. One shows its
properties on the PC network and the other shows the properties that have
the device address. Did that help? How did the second LAN icon get created?
I did this months ago and have no idea. It works fine.
 
W. Watson said:
It's a video device. It has its own unique address that is apart from the PC
network. The PC with the device shows two LAN network icons. One shows its
properties on the PC network and the other shows the properties that have the
device address. Did that help?
Click to expand...

Sorry, a little, but not enough. What Video Device? What exactly is it? What
does it do? How does it do it? Why does it have to have an IP# in the first
place? Is it an internal or external piece of hardware? Does it have it's own
RJ45 Female Connector? Is it "networkable" in the sense that other
machines/devices communicate with it?
How did the second LAN icon get created? I did this months ago and have no
idea. It works fine.
Click to expand...

Those get added when an additional Network Adapter gets added to the machine.
For example, adding a Firewaire Card creates a new network called "1394
Connection". It happens automatically,..you don't "do" anything. If you were to
delete the "connection" you'd probably have to uninstall and reinstall the
device.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed (as annoying as they are, and as stupid as they sound), are
my own and not those of my employer, or Microsoft, or anyone else associated
with me, including my cats.
-----------------------------------------------------
 
Of course it's networkable. Why would I have it there? How is knowing the
video device going to help? It has a fixed IP address, and it works. It's an
ethernet cable running from the device to the ethernet connector in the back
of the computer, as I said in the first post. I'm talking about a fully
functional network of three computers and a device that works on one of the
computers via an ethernet connection. It all works.

How would you go about in W2K connecting an ethernet device of any sort with
a fixed ethernet address to a network of LANed PCs that already working? You
only want to connect it to one of the PCs. As I said, in the first post,
it's connected to C.
 
Let me simplify matters. Suppose you have a single computer and you want to
add a device that has a fixed ethernet address, it is not a computer, and is
completely networkable. Further it has no dial-up or communications ability
other than to record data and send it back to the PC it is attached to. How
would you go about making a connection via the networking or other
facilities of W2K?
 
W. Watson said:
Let me simplify matters. Suppose you have a single computer and you want
to add a device that has a fixed ethernet address, it is not a computer,
and is completely networkable. Further it has no dial-up or
communications ability other than to record data and send it back to the
PC it is attached to. How would you go about making a connection via the
networking or other facilities of W2K?
Click to expand...

I think you're confusing the physical device with the logical network
connection (you certainly are confusing me). So lets go back to the
beginning.

1) You have a computer with one NIC. You need to connect to a device on
another network, and you want to use a second NIC to do that. OK so far?

2) You install a second NIC by plugging one into a PCI slot. When that
happens, Windows will most likely recognize the thing and create an
entry in the device manager list for the new NIC. If Windows doesn't
know the card, you may have to install a driver.

3) If you now go the network settings page (there are several ways to
get there, I prefer the method in my 1st reply), you should magically
find a new network connection (named "Local Area Connection 2" by
default). From this page and its sub-pages, you can assign the new
network interface an IP address and other TCP/IP settings, add and
remove or enable and disable various clients, protocols, etc.


If this is not what you mean, I'm lost and so it appears are others.

For the record, you don't need a second NIC to talk to devices
configured on different subnets, you can just assign a second IP address
to the existing NIC. A second NIC will, of course, guarantee bandwidth
exclusively for the subnet that it's configured for.

....kurt
 
Thank you. You are not confused. You understood it all perfectly. I posed
this possibility in my first post.

"I suspect the presence of the second ethernet card produced it. Is this
right?" It being LAN2.
 
W. Watson said:
Let me simplify matters. Suppose you have a single computer and you want to
add a device that has a fixed ethernet address, it is not a computer, and is
completely networkable.
Click to expand...

You don't,..it is that simple,...continued below.

An ethernet address is a Layer2 MAC address and is not "completely networkable"
because it only functions at Layer2. I am pretty sure that you are
misdescribing the situation which makes it impossible to either understand what
you really have or suggest anything to do about it.
Further it has no dial-up or communications ability other than to record data
and send it back to the PC it is attached to. How would you go about making a
connection via the networking or other facilities of W2K?
Click to expand...

You don't.
It won't happen,...at least not according to how you are describing everything.
That is why I am asking the questions that I asked. The questions I ask are
specific and are for a reason.

A machine cannot have two functioning "interfaces" on the same subnet that are
active at the same time without unpredictable behavor (at best). The
"interfaces" would have to be Teamed or have one left disabled. On the other
hand if the interfaces are in different subnets then other hosts on the one
subnet can *never* access the machine by the interface of the opposite subnet
unless that PC is configured to operate as a router (which pretty much isn't
going to happen).

So if you think about these things for a bit you will see why I have so
difficult of a time understanding the situation and how it was ever supposed to
operate in the first place.
Terminology is extremely important,...as one of my heros always says, "...words
mean things".

So what *is* this device? Are we talking about a Firewire based device (a "1394
Device").

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed (as annoying as they are, and as stupid as they sound), are
my own and not those of my employer, or Microsoft, or anyone else associated
with me, including my cats.
-----------------------------------------------------
 
I believe Kurt provided enough info for me. Plug it into the second PCI, and
follow the yellow brick road. I recall that when I did this about 3 months
ago, it was almost ridiculously simple. The device is a video box with a
fixed ethernet address. It's an interface to a camera that takes pictures of
the sky. It works fine. No, I don't work for any govt. secret agencies. :-)
It's been working quite well since I installed it.

You seem to be having a hard time accepting the fact that this device has no
conventional connection to the computer. No firewire, no USB, no printer
port, zippo. Ethernet--that's it. I hope you don't want a circuit diagram.
:-) It works on Linux, Win and Apple under Python. There you have it ...
 
Are you working on a special project for the US army? Whatever the
"device" is it seems to be a national secret! It must be a VPM...

John
 
W. Watson said:
I believe Kurt provided enough info for me. Plug it into the second PCI, and
follow the yellow brick road. I recall that when I did this about 3 months ago,
it was almost ridiculously simple. The device is a video box with a fixed
ethernet address. It's an interface to a camera that takes pictures of the sky.
It works fine. No, I don't work for any govt. secret agencies. :-) It's been
working quite well since I installed it.
Click to expand...

Ok. Good luck with it.
You seem to be having a hard time accepting the fact that this device has no
conventional connection to the computer. No firewire, no USB, no printer port,
zippo. Ethernet--that's it. I hope you don't want a circuit diagram. :-) It
works on Linux, Win and Apple under Python. There you have it ...
Click to expand...

No I just have a hard time understanding how it actually works. Remember that we
are completely "blind" from our end,...all we have is what you describe. I work
at a TV station,...a whole building full of weird gadets,...much of which could
be called a "video device",...I've learned to not take anything for granted.

We also have a Camera up on a tower,...about 400 feet up,...I forget what "name"
they have for it this week.
http://www.wandtv.com/page941.cfm


--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed (as annoying as they are, and as stupid as they sound), are
my own and not those of my employer, or Microsoft, or anyone else associated
with me, including my cats.
-----------------------------------------------------
 
Back
Top