Which LAN gets priority?

Char Jackson wrote:
> Keep in mind that you don't necessarily need multiple NICs to join
> multiple networks. You can assign multiple IP addresses to a single
> NIC and the OS will automatically use the correct source IP for the
> network you're attempting to access. That comes in handy when you want
> to be able to access more networks (I mean access directly, not via a
> router) than the number of NICs that are available.

Interesting, thanks for that. I dug around in TCP/IP properties, and found
a place to enter more IP addresses in the "Advanced" tab.

Jon

On Sat, 3 Dec 2011 11:55:37 -0800, "Jon Danniken"
<(E-Mail Removed)> wrote:

>Char Jackson wrote:
>> Generally, an IP address can only be assigned to one adapter in a
>> given network. If two adapters are given the same address, a conflict
>> occurs. It's sort of like giving your house the same number as the
>> guy's house down the street and the mail carrier doesn't know where to
>> deliver the mail. Every address needs to be unique.
>>
>> In the case above, the router's LAN IP is 192.168.75.1 (and the
>> Netmask is assumed to be 255.255.255.0), so the other valid IP's on
>> that network are 192.168.75.2 thru 192.168.75.254. Generally, every
>> network also has two reserved addresses, which in this case are
>> 192.168.75.0 (which refers to the network itself) and 192.168.75.255
>> (which is the broadcast address for that network).
>>
>> So if you have a device with an address of 192.168.75.1, it makes
>> sense that you can't assign that same address to a second device on
>> that network and expect it to work. In your example above,
>> 192.168.75.100 is a valid IP address for that network and it will
>> enable you to talk to the router, but any address between 192.168.75.2
>> thru 192.168.75.254 will work just as well because they all lie within
>> the Netmask.
>
>Thanks Char, that makes sense now. Just for fun I changed the static IP of
>the NIC from 192.168.75.100 to 192.168.7550, and it still worked, which was
>a good confirmation of the concept.

That's obviously 192.168.75.50. I knew what you meant.

>>> Thanks again for your help,
>>
>> No problem, I'm glad you made serious progress.
>
>Indeed I did, and I also learned a lot more in the process, which will come
>in handy when I actually hook the router up to the modem.

It's fun, right? There are tons of great tutorials online. I like
to point people to www.practicallynetworked.com as a good place to
start.

Char Jackson wrote:
>
> It's fun, right? There are tons of great tutorials online. I like
> to point people to www.practicallynetworked.com as a good place to
> start.

Aye, it is indeed a fun puzzle to figure out. Can be frustrating at times
when you don't have another computer in the house, and botching up your only
network connection leaves you high and dry, though, but that's part of the
excitement.

I have found some tutorials online, but I still like usenet for some reason.
I'll probably make another post here pretty soon to confirm what I think is
the right way too hook everything up.

Jon