T
Timothy Barbeisch
Hello:
I'm trying to solve a really weird set of problems with the DNS client
service in Windows XP Pro. I have a Gateway DS 450E laptop with
onboard wired and wireless Ethernet cards. I have reinstalled XP Pro
from scratch to no avail attempting to solve this problem.
Currently there is _no_ extra software installed on this unit other
then the operating system -- which is Windows XP Professional w/SP2.
The problem that I'm having is really weird. The DNS client stops
working even though the system can contact the DNS server on my local
network (ping's work just fine). I can't resolve any hostnames with
_any_ software. Going to "www.cnn.com" fails -- as does "ping
www.cnn.com" (unable to resolve host).
If I stop and restart the DNS client service low and behold all of the
hostnames start to resolve just fine. For awhile anyway -- eventually
it stops working again. It's not a network issue when ping's still
work -- it's not even sending packets to my DNS server to attempt to
resolve the hostnames -- it just quits working.
I had assumed this was being caused by Cyberpatrol -- which is why I
wound up reinstalling XP fresh. It's happening on a brand new install.
What the heck could be going on? This has me at wits end -- I've
never seen anything remotely like this before.
I'm trying to solve a really weird set of problems with the DNS client
service in Windows XP Pro. I have a Gateway DS 450E laptop with
onboard wired and wireless Ethernet cards. I have reinstalled XP Pro
from scratch to no avail attempting to solve this problem.
Currently there is _no_ extra software installed on this unit other
then the operating system -- which is Windows XP Professional w/SP2.
The problem that I'm having is really weird. The DNS client stops
working even though the system can contact the DNS server on my local
network (ping's work just fine). I can't resolve any hostnames with
_any_ software. Going to "www.cnn.com" fails -- as does "ping
www.cnn.com" (unable to resolve host).
If I stop and restart the DNS client service low and behold all of the
hostnames start to resolve just fine. For awhile anyway -- eventually
it stops working again. It's not a network issue when ping's still
work -- it's not even sending packets to my DNS server to attempt to
resolve the hostnames -- it just quits working.
I had assumed this was being caused by Cyberpatrol -- which is why I
wound up reinstalling XP fresh. It's happening on a brand new install.
What the heck could be going on? This has me at wits end -- I've
never seen anything remotely like this before.