This is a step by step setup of how you get Windows 2000 Server (or Professional) to use Internet Connection Sharing or ICS.
Introducing OpManager, an enterprise-ready network & datacenter infrastructure monitoring software. Trusted by over a million IT admins worldwide, OpManager monitors Routers, Switches, Firewalls, Physical/Virtual Servers, LAN/WAN traffic, Configuration changes, Apps such as Oracle, SAP, Websphere, etc & other IT devices from a single console. It is easy-to-deploy & use. Try it for FreeDownload FREE 30-Day Trial of ManageEngine OpManager
These instructions assume that when you have a Cable Modem connection or an ADSL connection (frankly, it can also be a simple Dial-Up modem connection, but that won't get you anywhere, would it?).
Let's say you have the following LAN configuration:
Internet | | | | 220.127.116.11 (Real IP from ISP) SRV1 (This will be the ICS computer) 192.168.0.1 (Bogus IP - Configured by ICS) | | | | Switching Hub---------PRO2 | 192.168.0.2 (Bogus IP - Configured by ICS) | | | | 192.168.0.3 (Bogus IP - Configured by ICS) PRO3
Instead of a hub you could use a crossover cable to the other computer but then you will only be able to connect 2 computers, and if you'd want more you'd need more NICs.
Step 1: Configure Internet Connection Sharing
Right click "My Network Places" and select "Properties".
In this window you should see an icon for "Local Area Connection" and "Local Area Connection 2" for both of your NIC's.
Right click on the Network Area Connection icon that connects to your Cable or ADSL modem, and select "Properties" from the drop down window.
If you're using a modem to connect to the Internet you must right click the icon that represents the connection to the Internet.
Click on the Sharing tab.
Check the box next to "Enable Internet Connection Sharing for this connection" and press "OK" to share your connection through this NIC.
You will receive a warning window saying that your NIC will automatically receive an IP address of 192.168.0.1, and that if you have other computers on your LAN that have static IP addresses - you should configure them to obtain it automatically - otherwise you will probably break the connection with them.
Acknowledge this warning.
Back at the "My Network Places" Window, right click on your "Local Area Connection 2" icon and select Properties from the drop down menu.
Check the TCP/IP settings by double clicking on the "Internet Protocol (TCP/IP)" line, or highlight it and then click the "Properties" button beneath it.
You should make sure that your TCP/IP properties looks exactly like this:
These settings were auto configured by the ICS service.
Step 2: Configure network computers to use ICS
To get your Client computers up and working you must configure them to obtain an IP address automatically. To do so you must go to their Local Area Connection icons (like you did in step 1) and select the properties for the TCP/IP protocol. You must then select "Obtain IP address automatically" and press Ok.
To see if the computer has successfully received an IP address from the ICS service, go to a command prompt and type "ipconfig /all" (without the quotes you moron!). Notice that it should say "DHCP Enabled = Yes", and that the IP address should be in the 192.168.0.0 range (probably 192.168.0.2, 3, 4 and so on). If it's not showing yet, you can force a renewal of the IP address by typing "ipconfig /renew" and waiting a few seconds.
If you're using Win9X go to Start/Run and type "winipcfg" and do a renew from the window.
ICS is a practical feature for people that do not know how to configure their Internet Connection Sharing through NAT. But one thing should be clear as crystal:
ICS is CRAP!!! ICS is a no-no on operational networks!
ICS might ruin your network! If you have computers that are configured with static IP addresses you must now configure them to get their IP addresses automatically, and if you do not do so, they might not be able to communicate with you anymore (or create IP address conflicts).
ICS will cause your computer to behave as a DHCP server, and by doing so it will stop the regular DHCP service (if you ever had one running)!
ICS will act as a DNS proxy, and will render your existing DNS infrastructure useless (if you ever had one)!!!
ICS will ruin your Active Directory (no DNS? No AD!) unless it's run on the Domain Controller itself, but that's something you don't want to do, do you?
ICS will not let you choose what IP address range to lease to it's clients. It will only lease the 192.168.0.0 network range, and you cannot change that.
ICS has very limited port mapping functionality and low performance compared to the regular NAT service.
ICS is only good for 2-5 computer networks that do NOT have running DNS, AD, DHCP, Web or E-Mail services, and if that's not the case - consider NAT.
With that said, carefully consider your situation and act accordingly.