ICS Problems

Alright. I'm having some issues here. Both of my boxes are running Windows 2000 Pro. The host machine has 2 NIC's installed ... one for the cable modem, one connected to the NIC in my workstation. Without ICS enabled the network functions properly. When I enable ICS, and reconfigure the NIC's, the network functions proplery at the LAN level ... but as soon as I try to access an outside source from my client machine, the host locks up solid and requires a reboot. I don't see what I've done wrong, but maybe somebody here knows.

These are the steps I take to enable ICS:

1. On the host machine, I right click on the connection for the cable modem, enable sharing, and choose the LAN connection from the *for local network* pulldown menu. Bang, ICS enabled.

2. On the client machine, I change the TCP/IP properties of the NIC to the following;
IP address = 192.168.0.69
Subnet Mask = 255.255.255.0
Default Gateway = 192.168.0.1

3. I change the LAN settings of the web browser on the client machine so that *automatically detect settings* is unchecked.

4. Back on the host machine, I set the firewall to act as an ICS gateway, and add the client machine IP address to the local zone list.

With all this having been done, both computers can see eachother across the network, I can freely access drives on one from the other, and they both get ping replies from eachother. However, like I noted earlier, when I try to fire up the web browser on the client machine, or try to ping an internet address from the client, the host locks up and requires a reboot. I'm stumped. Any help would be greatly appreciated. Thanks in advance.

Regards,
Christopher

 

Sounds like you know what you're doing. Interesting problem. Maybe some setting you've overlooked? Is Client's DNS server and gateway set to 192.168.0.1? Did you previously have a proxy server installed? Sometimes a proxy server's residual registry settings, even after it's been uninstalled, will foul things up (one time I had to reinstall w2k because of this). That the server hangs, rather than merely fails to connect, suggests possibility of conlict between ICS and a NIC. Maybe changing NIC or updating w2k with SR2 or SR3 might help if it's this. As a last resort, you could dump ICS and use NAT32, which I think is better anyway.