Need help with ICS

[Mr.Goodbytes]

Before I start, I have read and attempted what was suggested in the links provided in: http://sysopt.earthweb.com/forum/Forum6/HTML/001804.html

I've used tools like wingate and sygate, or the linksys router/switch before, but I don't have them in this situation. What I have is one Win98 SE box with 2 NIC's in it. One is connected to a cable modem, the other is connected to a 10/100 switch. Box #2 has Win 98 and one NIC in it of course connected to the switch. ICS appears to be set up properly on the first machine. I have put static IP's on each one, 192.168.1.101 and 192.168.1.102. Host, domain, and proper DNS server entries are set up on Box #2. Computers are on same workgroup. I've tried multiple entries for the gateway on Box #2 to no avail.

I can however ping each local IP from either box. Box #1 can access the net and use ICQ and AIM just fine. Box #2 has no net access whatsoever. And yes, all protocals are installed on each machine (TCP/IP, IPX/SPX, and NetBEUI). Have I given enough information to solve this one? Do I have some setting wrong on Box #2?

Thanks in advance.

[DVNT1]

Remove your client PC's LAN static IPs and related gateway/DNS settings set them for DHCP.

On the ICS host PC, I think you need the static 192.168.0.1/255.255.255.0 address if ICS is already installed (it normally does it during install).

[Mr.Goodbytes]

Tried that, didn't work though. The client is given the proper IP 192.168.0.2, but it still cannot access the net. It can still ping the IP of the host PC and that which is given to it by @home. Any other suggestions?

[Mr.Goodbytes]

I have also noticed that I can ping the DNS servers that the host computer uses. I can also ping yahoo, but only if I type in the IP. But I can't get to the website by typing in the IP. So I guess DNS isn't working, right? I'm really quite confused by this one.

[Ollie46]

Do you have ip forwarding enabled? Also, have you configured the hosts file so that box #2 knows that box #1 is a gateway and not just another machine.

Ollie

[Mr.Goodbytes]

The client knows that the host is a gateway. I have just tried enabling DNS on the host, and the result just let my client pc know the DNS addresses. Still no net accessHow do you enable IP forwarding?

[kirk6677]

looks like you and me are having the same problem! however I am using windows 2000 advanced server and windows me. Don't ya hate it when this happens?

[DVNT1]

IP forwarding does not sound like the problem in this case. It does sound like DNS problems. With static IPs on the client, you must set the DNS IP address (on the clients) to be the ICS HOST computer's LAN IP address.


I suggested DHCP for the client because the other DNS and Gateway settings would be correct. In doing that, the LAN NIC in the HOST must be set to 192.168.0.1 address or it won't work either.

If you want static IP addresses on the client that are out of the defualt 192.168.0.1,192.168.0.2, etc.. range then you may need to edit the registy. See http://support.microsoft.com/support/kb/articles/Q230/1/48.ASP?LN=EN-US&SD=gn&FR=0&qry=ICS&rnk=30&src=DHCS_MSPSS_gn_SRCH&SPR=WINME . Then set your client static IP addresses, DNS IP to be the LAN NIC address on the HOST, same for Gateway.

[This message has been edited by DVNT1 (edited 01-07-2001).]

[DVNT1]

Are you saying that I need to make that the DNS as well on the client?

Not if it is being assigned by the HOST. Which is usually done by default.

To check, run WINIPCFG on the client, then choose more info...it (192.168.0.1) should show up there correctly.

Should I keep DNS enabled on the host? I just entered on it the settings that are automatically give to it by @home's DHCP server.

I don't know about @Home's settings, but if your HOST accesses the Internet correctly then it shouldn't be a problem for the client either way.


Relating to kirk6677's problem/fix....it may be easier to remove your TCP/IP protocol (from clients too) and ICS. Reboot, then add the TCP/IP protocol but do not enter any additional settings.

Install ICS on the HOST, reboot, Then startup the client.

[Ollie46]

Ok, heres the deal. I just realized what you are doing. Anyway, it is a documented problem that ICS will not work with some cable connections. http://www.speedguide.net has a patches section that containts the patch that is needed for ICS to work on these systems. I have not used it so I can not gaurantee that it will solve your problem. Also, DVNT1, i had a similar problem on my Linux box and the only thing that kept it from not working was the fact that IPforwarding was not enabled, that's why I applied that to this situation.

Ollie

[Mr.Goodbytes]

I do have the client set up for DHCP, and the host gave it the IP address 192.168.0.2. Now the host's LAN IP is 192.168.0.1 and that is automatically chosen as the gateway. Are you saying that I need to make that the DNS as well on the client? Should I keep DNS enabled on the host? I just entered on it the settings that are automatically give to it by @home's DHCP server.

[DVNT1]

Ollie46, because his client PC could ping Internet IP addresses, I would have to assume the IP forwarding part is okay. If it was not able to ping those, then the IP forwading would be a concern.
Regarding the known problem with some cable connections, are you referring to unidirectional connections? If not, do you have any links to the other known problems so that I can understand them as well?

You mentioned speedguide.net, which patch seems to fix an ICS problem? I only noticed speed related patches (except a Win95 patch for TCP/IP)?

[Mr.Goodbytes]

I tried removing all protocols and starting from scratch. I end up in the same situation with the host getting access to the net and the client only able to ping locations on the LAN and on the net. ICS still says just one computer using internet connection. I'm thinking of trying the NAT 32 that Genocide referred to in the link on my first post. Anybody have some thoughts on that utility?

[DVNT1]

I *think* there would only be one client since the HOST computer doesn't use ICS to get to the Internet, only the client.

If you can ping the Internet from the client and the HOST can use the Internet, it would seem that DNS still isn't right on the client.

Since your reinstallment of protocols, what does the WINIPCFG (on the client) show as the DNS server?

[Mr.Goodbytes]

It shows (and this is probably because I have DNS enabled on the host) 24.10.210.47 as primary DNS and 24.10.210.49 as the secondary. These are the DNS addresses that the host uses as assigned by @home's servers.

That's the way it should be, right? I mean, the client should only see the host's LAN IP as a gateway, and the DNS should still be derived from the ISP. If I'm wrong, then maybe that's why this is screwing up. Anyone else have thoughts on what ICS means when it says, "1 computer is using the internet connection?" Does that mean 1 total or one other than the host?



[This message has been edited by Mr.Goodbytes (edited 01-08-2001).]

[DVNT1]

Yes, the DNS seems to be configured correctly then.

You stated you can ping Internet addresses...does this mean only by IP or also by HOST name, like www.yahoo.com (http://www.yahoo.com) ?
If pingin host name works then the web browser may be a problem.

Additionally, these links talk about settings if using manually set IP ranges... http://support.microsoft.com/support/kb/articles/Q230/1/51.ASP