ICS on Win2000 Pro

I have just installed ICS on my Win2k Pro machine.(put in another NIC. Made that one my local network. Shared the connection on the external network) Everything works fine on the host. I am having a problem with one of my clients.(actually my only client at this time) It is a Red Hat 7.3 Linux box. I have it set to use DHCP. That part seems to work fine. It receives an IP address, usually something like 192.168.0.93. But I can't seem to get it to connect to the internet though.

From the Win2k host, I can ping the Linux client just fine. From the Linux client, I can ping my host's real IP address(64.xxx.xxx.xxx), but not the local address of the host(192.168.0.1)

It also seems like DNS is working correctly. I can 'ping anydomain.com' from the client, and it resolves the name to an ip address, yet it does not actually recieve any packets back.(or actually send any for all I know) Traceroute, telnet, ftp, whois, etc. does not work either. But nslookup, host, and dig work just fine. That is why it seems like my dns stuff is working, but I am not sure. I cannot connect to any websites though. This is my big problem.

I have taken down my personal firewall on the Win2k host. I have taken down the firewall on my linux box as well.('ipchains -F') I cannot think of anything that would be blocking it.

I can't seem to figure out what I am doing wrong. Do I need to share certain applications from the host that the client will use, such as port 80, tcp and upd? I played around with these settings, but without much luck. Any help would be appreciated.

This should be working now. You can change the options for the NAT and add mapped ports etc. using the context menu.
Routing and RAS is not a proxy, thus it does not check the requests made by name or URL. However, you can define filters for each netowrk interface, including IP range and ports to be locked out (or to have exclusive access).
This will allow you to define simple rules depending on the IP or IP range. You could also block port 80 and use another proxy software to do more detailed filtering, while still allowing all other traffic to be handled by the NAT.
From: andyalder Date: 09/04/2001 05:32AM PST
The second screen of the RRAS connection wizard allows ICS or NAT, not both. Which did you pick???

If you picked ICS then disable the DHCP service as ICS provides it's own DHCP agent.

If picked NAT then ensure the DHCP service is running and had a router (03) option of your servers 192.168.0.1.
There's more to it than this but confirm whether ICS or NAT first.
From: Kong Date: 09/04/2001 06:26AM PST
Hi Andy, I chose NAT on the second screen...

Sorry about the confusion, on the first screen, I selected ICS and on the second screen, I selected
NAT...
From: andyalder Date: 09/04/2001 06:45AM PST
Under RRAS, ip routing NAT check that the 2 interfaces properties in case you have the inside interface
defined as the external interface (unlikely)

On DHCP manager set the router(03) and DNS server(06) to be your server 192.168.0.1

Under DNS manager, select the properties of the server and under the Forwarders tab enter your ISP's
DNS server as a forwarder. If the checkbox is grayed out then under forward lookup zones delete the
zonefile "." then action-refresh it will no longer be grayed out.

Also ensure no win2k workstation or win98SE has accidentally setup ICS or that might assign the DHCP
info to your clients. Easy to check with ipconfig.
From: andyalder Date: 09/04/2001 09:38AM PST
I'm not sure, I always use a firewall or setup the router to filter unwanted traffic. Probably the router
itself is performing NAT in which case no incoming ports would be forwarded to your server anyway, just
replies to it's own packets.
How to Configure Input Filters for Services That Run Behind Network Address Translation NAThttp://support.microsoft.com/support/kb/articles/Q254/0/18.ASP might be worth a read.

From: dcgames
Date: 07/11/2001 08:09AM PST
A) IP Forwarding cannot be enabled with a dialog box or button on Win2K PROFESSIONAL. You have to set a flag in the registry using REGEDT32.

B) To share an internet connection, just right click on it and open it's properties. There should be
a tab to do it. Just check "Share this connection". It works for dialup just fine.

- You have to have installed Internet COnnection Sharing (ICS) as a component when you installed Win
2K. Check in the Control Panel, Add/Remove Programs, Windows Components and make sure it's installed.

- When you "share the connection", you also need to specify that the connection is "dial-on-demand".

- You don't need to worry about enabling IP Forwarding if you are using the sharing the connection.
That's automatic.

- The lan NIC will be changed by ICS to IP address 192.168.0.1. It also installs a mini DHCP service.
Clients then use "dynamic IP" and are assigned 192.168.0.2, etc., with gateway 192.168.0.1. But you
can set the client's IP address statically if you prefer. Just remember it's 192.168.0.2 (or higher),
mask 255.255.255.0 and gateway 192.168.0.1.

the gateway does, in fact, look good... however the IP on the linux seems a bit problematic... 192.168.0.0 is a network address & cannot be used for a machine. change this to 192.168.0.2 and see how it goes