Windows 2000 networking question

[Brian]

Hi all:

Here's my problem. I have a Windows 2000 machine that has a NIC in it
and the machine runs an inter-office application through a Netgear hub.
A W95 computer is the client and the W2K machine is the server running
the application. What I want to do is add a wireless USB device to the
W2K machine and then bridge the WLAN connection (USB) to the NIC on the
W2K computer and set up ICS using the already wired connection through
the hub so the W95 computer can get online.

I set this all up but I can't get both connections to run at the same
time. One has to be disabled for the other to work. Independently, they
work fine. What am I missing here?

Plus, once I get both connections to run simultaneously, I'll need to
bridge them and then set up ICS. Is this viable? Then, how do I run ICS
since the WAP's IP address is already 192.168.0.1 since I think that ICS
needs to assign that IP to the W2K machine? Any suggestions would be
greatly appreciated.


Brian

 

[Phillip Windell]

You're getting your "lingo" twisted. Bridging has no role in this. They
never even had this bridging featue before XP,...so how would Win98, NT, an
Win200 have used the internet this way in the past?

This is done with Netowrk Address Translation (NAT) and that is what ICS
does. ICS also has a built in DHCP serice that you are forced to use and you
are forced to use the addres range it provides.

The USB Nic would be setup to connect to the Intenet as if it was the only
NIC in the machine. The LAN nic is setup to work on the LAN as if it was
also the only NIC in the machine. There is no direct relationship between
these Nics and neither will know (or care) that the other one exists.

The USB Nic would probably have the Default Gateway and the rest of the IP
Addressing setup by the ISP's DHCP. The LAN Nic would have 192.168.0.1 (if
memory serves) for the ICS to work and it will force the address it wants.
This LAN nic will *not* have a Default gateway. All other machines on the
LAN will have their addresses set to "automatic" and will get their address
settings from the built-in DHCP that ICS has.

 

[Brian]

You're getting your "lingo" twisted. Bridging has no role in this. They
never even had this bridging featue before XP,...so how would Win98, NT, an
Win200 have used the internet this way in the past?

Thanks for the explanation. Knowing what to ask is much easier if you
use the right terminology.

This is done with Netowrk Address Translation (NAT) and that is what ICS
does. ICS also has a built in DHCP serice that you are forced to use and you
are forced to use the addres range it provides.

The USB Nic would be setup to connect to the Intenet as if it was the only
NIC in the machine. The LAN nic is setup to work on the LAN as if it was
also the only NIC in the machine. There is no direct relationship between
these Nics and neither will know (or care) that the other one exists.

Since the USB adapter and NIC are already installed, what do I need to
do to acheive this - making them think they are the lone network interface?

The USB Nic would probably have the Default Gateway and the rest of the IP
Addressing setup by the ISP's DHCP. The LAN Nic would have 192.168.0.1 (if
memory serves) for the ICS to work and it will force the address it wants.
This LAN nic will *not* have a Default gateway. All other machines on the
LAN will have their addresses set to "automatic" and will get their address
settings from the built-in DHCP that ICS has.

The WAP/Router is already assigned an IP of 192.168.0.1. If the USB
device is set as the gateway with the IP of same wouldn't there be a
conflict? I read that to overcome this simply unplug the WAP, set up
NAT, then plug your WAP in again. Is this correct?


Brian

 

[Phillip Windell]

Since the USB adapter and NIC are already installed, what do I need to
do to acheive this - making them think they are the lone network

interface?

Do nothing. I stated it that way so you would not go out of your way to
make them otherwise (like the bridging stuff).

The WAP/Router is already assigned an IP of 192.168.0.1. If the USB
device is set as the gateway with the IP of same wouldn't there be a
conflict? I read that to overcome this simply unplug the WAP, set up
NAT, then plug your WAP in again. Is this correct?

WAP? Sorry, I don't even remember what the acronym means.... What Router?
If you already have some kind of broadband Router handling the Internet
connection then forget the whole thing, forget ICS, forget the USB nic and
remove it. Run the machine with only the normal LAN Nic.

 

[Brian]

interface?

Do nothing. I stated it that way so you would not go out of your way to
make them otherwise (like the bridging stuff).




WAP? Sorry, I don't even remember what the acronym means.... What Router?
If you already have some kind of broadband Router handling the Internet
connection then forget the whole thing, forget ICS, forget the USB nic and
remove it. Run the machine with only the normal LAN Nic.

Sorry. Wireless Access Point - we have a Netgear wireless access
point/router. The goal is to get a W95 machine online using the existing
infrastructure of the internal LAN. The W2K machine powers an
inter-office application that runs through that LAN; connected through a
hub. So, the W2K machine will act as a router itself - connecting to the
outside via the USB wireless and then passing (routing) it through the
LAN NIC to the W95 machine.



Brian

 

[Phillip Windell]

Sorry. Wireless Access Point - we have a Netgear wireless access

Ah! Sorry, I should have known that . I guess I'm just getting tired of all
the constant acronyms.

point/router. The goal is to get a W95 machine online using the existing
infrastructure of the internal LAN. The W2K machine powers an
inter-office application that runs through that LAN; connected through a
hub. So, the W2K machine will act as a router itself - connecting to the
outside via the USB wireless and then passing (routing) it through the
LAN NIC to the W95 machine.

Anyway, yes, if the WAP is properly connecting to the Internet on the Win2k
box, then enable ICS on this box and let is "share" the Internet Connection.
As you noticed, you have an address conflict. The WAP's address *must* use a
different subnet. If you can't do that, then you will have to replace it
with something else that is more configurable (and not USB). ICS is
hardcoded to use the address set it uses,...I think it can be altered in the
registry but I don't remember for sure (I don't use ICS, probably never
will).

 

[Brian]

Anyway, yes, if the WAP is properly connecting to the Internet on the Win2k
box, then enable ICS on this box and let is "share" the Internet Connection.
As you noticed, you have an address conflict. The WAP's address *must* use a
different subnet. If you can't do that, then you will have to replace it
with something else that is more configurable (and not USB). ICS is
hardcoded to use the address set it uses,...I think it can be altered in the
registry but I don't remember for sure (I don't use ICS, probably never
will).

To avoid the conflict I changed the WAP IP to 192.168.2.1 and then let
ICS do its thing and assign the LAN NIC an IP of 192.168.0.1. The W95
machine gets the web ok now. Easy enough. Thanks for your help.


Brian

 

[Phillip Windell]

Thumbs up!