Re: Free brain teaser - Networking ?

Rescue wrote:
I have 3 pc's in front of me...
3 monitors

it all flows from left to right.

On my far left is os XP
in the middle is Y2K
on the right is Y2K (my very very cool server..has 4 processors and 5
HD)

The far left pc has 2 ethernet cards.
The middle pc has 2 ethernet cards.
The last pc, has one ethernet card

The left pc has ICS turned on, I DO get internet on the middle
machine...
so that's two machines on the internet...

I have tried all evening to get the 3rd pc on the internet...

I am not allowed to use ICS on the middle machine because it creates an
IP conflict with the first machine.. 192.168.1.1

How can I jump the 3rd machine onto the internet..

another very cool thing...All 3 machines are in the same workgroup, all
3 machines can see each other...(in case that is of signifigance)

I don't have a hub or router...(I know this is ideal and I am going to
get one soon)
but can't I just assign and IP for the 3rd machine

looks like

PC 1 = Internet Source
PC 1 = ICS enabled

PC 2 = Does get on the internet just fine
PC 2 = Will not let me share second card here...IP conflict with first
machine

PC3 = Is on the network, but not on the internet (yet)

Thanks


The second machine would have to be setup as a router so it can route between 1 and 2. That's Routing and Remote Access on the Win2k server (assuming that's what you mean by "Y2K").

The IP conflict on the second machine's second NIC is because you apparently haven't set it to a different subnet, which you would have to do for it to be a router. I.E. your 192.168.1.0 range should be subnetted with, say, a 192 mask that could give you 4 subnets:
192.168.1.0 - 192.168.1.63
192.168.1.64 - 192.168.1.127
192.168.1.128 - 192.168.1.191
192.168.1.192 - 192.168.1.256

First and last of each unusable (broadcast address and such) and 1 address for the router port, which is traditionally the first one like the 192.168.1.1 default assigned by XP for the ICS 'router' address. So, for a 192 mask, the subnet router ports are usually assigned as
192.168.1.1
192.168.1.65
192.168.1.129
192.168.1.193

Your first subnet would be the one you have now between machines 1 and 2, except change the subnet mask to 192 limiting it's range to 192.168.1.0 - 192.168.1.63. Assign the second NIC on machine 2 to 192.168.1.65 for the second subnet. Make machine 3's NIC anything in the second subnet range, say 192.168.1.66 with it's default gateway the adjoining router's address, I.E. 192.168.1.65. You then have to setup the routing in Routing and Remote Access on machine 2.

It works this way. When a machine wants something 'on the subnet' (which it knows by the NIC IP and mask assignment) it simply sends it out and the target machine on that subnet will see it and respond. If, however, the target is NOT 'on the subnet' it must be routed, and that's what the default gateway does. I.E. Machine wants something NOT 'on the local subnet' (it knows because the IP it wants to talk to is not in the subnet range) so it sends the request (addressed) to the 'gateway', rather than raw over the subnet, and the gateway (who sees 'this is addressed to me to do something with') knows what the next step in the routing is. In machine 2's case it will know, if you setup the routes properly, to send it on to machine 1 (it's default gateway on that NIC).

The reason you have to subnet with what you've currently got is because machine 2 has two NICs and, so, must be what's called a 'multi-homed' machine. The IPs for the two NICs can't be in the same subnet because they're physically different NICs and, so, physically different nets.

The reason machine 3 can't get to the internet, as it stands the way you have it, is because machine 2 doesn't know you want it to route between 3 and 1, plus you probably didn't set it as the gateway in machine 3 anyway, so machine 3's internet requests just wander around the local subnet like the Geico Gecko's lonely 'fact' looking for a place to call home in someone's ear. I.E. Nothing past machine 3 knows they're supposed to 'do something' with them so they're ignored (not my job, man).

Of course, it's all simpler with an external router and them all on the same subnet (only 1 NIC used per machine).

The second most simple would be a hub/switch that connects both machine 2 and 3 to the machine 1 ICS NIC. The down side there is machine 1 always needs to be on to do the ICS.

The worst is the subnetting because both 1 and 2 must be on for 3 to get to the internet.

.

Relevant Pages

  • Re: New User on Wireless Setup (continued)
    ... with the gateway on the second pointing to the first so the cable internet works on both..... ... easy to do the two wap/routers to isolate the subnets, trick was the gateway so the second subnet users could use the internet, but not see anything shared on the other subnet ... wap router 1 ssid PPinUSA DHPC server on, cable modem, starting ip ...
    (alt.internet.wireless)
  • Re: IP Config with 2 NICs Wizard dont work, Static dont work!
    ... Leave the Subnet MASK alone and change the 3rd octet in the ... IP address of either the internal NIC or (external NIC & router). ... Properties | Internet Protocol | Properties ... >>> you have both NICs in the same subnet, ...
    (microsoft.public.windows.server.sbs)
  • Re: IP Config with 2 NICs Wizard dont work, Static dont work!
    ... want to beat a dead horse here but the internal and external NICs CANNOT ... Internet and Email on Left Panel and set the Address to 192.168.16.2 Leave ... If you want to understand IP subnetting and subnet masks please get a book ... Or should I move the static IP routers over to ...
    (microsoft.public.windows.server.sbs)
  • Default Gateway Reverts to Old Setting
    ... Having a problem with the default gateway setting on a WinSvr2003 Std box at ... This server is on the only IP subnet at the client's main office. ... The server has two identical 10/100/1000 NICs, ...
    (microsoft.public.windows.server.networking)
  • Re: 2 NIC SBS2003R2 LAN/WAN Firewall Router Connection Failure
    ... Please contact your router vendor to check the settings in the router, ... may be there are some rule deny the access from some IP addresses or subnet. ... How to configure Internet access in Windows Small Business Server 2003 ... |> Two Nics, a static IP address, ISA, router ...
    (microsoft.public.windows.server.sbs)