You are on the right track, Steven. ICS isn't really compatible with AD.
The ICS "server" works as a DNS proxy, so the client needs to use
192.168.0.1 as the DNS setting. This fails for AD, as the client needs to
use the AD DNS server.
With NAT you can get around it by using DNS forwarding on the AD DNS
server. Not sure if this will work for ICS though.
"Steven L Umbach" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Could be a dns problem. Try using nslookup to see what it reports as your
> dns server and then use it to try and resolve an internet name such as
> Yahoo.com. Since your using a domain, I assume you mean an Active
> Directory domain, your internal dns server - a domain controller would
> need to be able to resolve internet names via the use of a forwarder or
> using root hints. See the link below on dns in an AD domain to see if it
> can help you out. Also if you have the XP SP2 firewall enabled, disable it
> temporarily to see if that makes a difference. In general ICS and domain
> computers will not work well because I believe that ICS requires the ICS
> computer to be an DHCP "allocator" which can cause problems on a network
> with domain computers that are DHCP clients. Using NAT on a server could
> be a better solution, though I have never used such with a dial up
> connection. --- Steve
>
>
> "Tim Marsden" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi,
>>
>> I have a domain, one client pc has a modem and connection sharing turned
>> on.
>> From the other pc I can ping my isp and automatic updates find the net
>> ok.
>> But I can not use Internet explorer? Page not found.
>> I am using XP sp2.
>>
>> Any suggestions
>>
>> Tim
>>
>
>
|