Enabling ICS on the NIC connected to the
internet on a Win2K host always brings up
a warning that the card will be assigned the
address 192.168.0.1. If I have a LAN connected
to the host through a second NIC which has
been assigned the static IP gateway address
of 192.168.0.1, will this interfere with the proper
functioning of ICS?

Would I have to set the LAN connected NIC IP
address to say 192.168.0.2 to avoid this interference?

What if the internet connected NIC is assigned its
IP address through a DHCP server? How can a card
be assigned two separate addresses. Is this like
IP-Alias in Linux?

TIA

A card can only be assigned one address. If you get an IP address assigned through DHCP that is connected to the Internet that ends up being 192.168.0.1, there's something whrong somewhere. 192.168.x.x is a hobbyist address, and no router in the universe will believe that those packets are destined for the Internet.

Make sure your Win2k is set up right. I'd say if you're still in the setup stage of this server, install Linux and see if you can set up both NICs, so that one speaks to the Internet and one to your internal network. If you can get that to happen, the problem lies within Win2k. I have a NIC that won't work in Win98, but I'm running it and another NIC under Linux as a gateway to my LAN.

Okay, this is how ICS on Win2k works:

You enable sharing on the card connected to the internet, and this then sets your OTHER card to 192.168.0.1

It starts a DHCP server on your 2K box, and you have to set everything on the LAN to pick up a dynamic IP address. then all should be right with the world. except its not, cos your using M$ (i did exactly this for about 3 months cos i was too lazy to set up a linux firewall)

i assume that you are using a cable modem or other broadband connection? if you are, then i suggest getting some sort of firewall installed on your windows machine. eg zonealarm.

hope this helps

Slh

Yes I finally figured out that I would have to remove
the static IP settings from the card that interfaces
the LAN and enable it with DHCP so that ICS could
assign it the adress of 192.168.0.1.

Fortunately I did not have to set the Linux NIC to
DHCP to accept an assigned address from ICS.
I could leave the static assignment as is.

It works fine now.

It is terribly unclear that the LAN card on the host
machine is the one to set up for ICS DHCP.

BTW, Samba still works just fine and ZoneAlarm
doesn't seem to be a problem either.

It is Sooooo much easier to use a Linux server with
netfilter and SNAT/Masquerade. Maybe I should switch
things around and use the Linux box as the server.
Well, a guy's gotta experiment.


Thanks for the help.