SP2 problem with ICS client using DNS

  • Thread starter Thread starter John G. Ata
  • Start date Start date
J

John G. Ata

After installing SP2, my client ICS computer can no longer resolve names.
Communications works great on the host computer to the internet (public
network), the host computer to the client on the private network, and even
on the client ICS to the Internet as long as their is no name resolution
required. Interestingly enough, if a name has been resolved on the host
computer recently, the client will be able to resolve that name - it's as if
the client ICS can't send a DNS query out, but is able to use previous
successful queries from the host computer. Does anyone have any ideas?

Thanks,
John
 
"John G. Ata" said:
After installing SP2, my client ICS computer can no longer resolve names.
Communications works great on the host computer to the internet (public
network), the host computer to the client on the private network, and even
on the client ICS to the Internet as long as their is no name resolution
required. Interestingly enough, if a name has been resolved on the host
computer recently, the client will be able to resolve that name - it's as if
the client ICS can't send a DNS query out, but is able to use previous
successful queries from the host computer. Does anyone have any ideas?

Thanks,
John
Click to expand...

I don't know what caused the problem, John, but here are some possible
fixes. If one doesn't solve the problem, try the next one:

1. Un-install and re-install the network card on the client.

2. Download and install the latest network card driver on the client.

3. Disable and re-enable ICS on the host.

4. Configure TCP/IP manually on the client:

IP Address: 192.168.0.x (1<x<255)
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DNS Server = your ISP's DNS server
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
Hi Steve,

After much debugging, I have found a solution (although I'm not happy with
it). On the client, if I configure my ISP's DNS servers on the private
network then I have no problem. I don't like this because if my ISP changes
their servers, I won't know about it and am more prone to name resolution
failures. It is puzzling why the automatic configuration doesn't work (this
had my host computer's private network address 192.168.0.1 as the DNS
server). I guess I will run this way unless someone can point me to a
better solution.

Thanks for all your help, I appreciate it.

--John
 
I have this problem as well. However, from the client I can not even ping
the ip address of the NIC on the host that connects to the internet. Pinging
the ISP DNS server has the same result.
 
Back
Top