At 02/08/2006, Pete Holsberg wrote:
...That sounds like a DNS problem, right?
You could try flushing the DNS cache on her computer -- "ipconfig
/flushdns" from the command line. The longer the system is on, the
more addresses it caches, but I'm not sure what the limit for that
is. Anyway, it sounds like it may just be a slow response from the
DNS server and XP isn't waiting long enough for it. XP treats a
non-response from the server the same as a bad address and logs it in
the cache as such. Then when the address is used again, rather than
asking the DNS server to resolve it, the cache is used. So, the
address can again come up as bad. The cache is supposed to speed
things up by not having to go to the DNS server every time, but it
can have its drawbacks.
There's a registry tweak to prevent negative responses from the DNS
server from being cached. That forces requests that didn't work to
go back to the DNS server to resolve them rather than using the local cahce.
You can find the tweak for that
here: <http://cable-dsl.home.att.net/#dns_cache>
Oh, and it doesn't matter if she is using a dialup, cable-modem, or
whatever connection. That cache still works the same way. I used to
have a lot of problem with that type of DNS error when I still used
dialup with XP, until I added that tweak to the registry. Since I've
gotten a cable-modem, it's rarely a problem, though.
HTH.
--
Tony Lowe, The HapMaster
What if the hokey-pokey really is what it's all about?
--
----------------------------------------
WIN-HOME Archives: http://PEACH.EASE.LSOFT.COM/archives/WIN-HOME.html
Contact the List Owner about anything: [EMAIL PROTECTED]
Official Win-Home List Members Profiles Page
http://www.besteffort.com/winhome/Profiles.html
