Problem with XP caching failed DNS lookups

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a problem with a windows XP box I have recently acquired

I connect this box to the net through a proxy machine with a modem. On
attempting to connect the proxy dials on demand and connects and
everything is automatic from then on - usually.

What happens with the XP client is that I will attempt to go to a web
page ( google.com for example ), the proxy dials up and connects. By
this time XP has decided it would get no response and returned an
error. Now on every other box I have used as a client I could then
reload and the page would come up, ie it is only a spurious error
because the dial up connection is slower than the application's
timeout. But with XP it appears to have cached the name server
information so that subsequent connection attempts will also fail,
albeit that they fail immediately, but connections to a new address (
e.g. google.co.uk ) work correctly.

The only way to connect to the original page appears to be to reboot
XP. How can I persuade XP that it really doesn't know as much as it
thinks it does and make this box connect?

TIA
 
(No_spam_please) wrote in
What happens with the XP client is that I will attempt to go to a web
page ( google.com for example ), the proxy dials up and connects. By
this time XP has decided it would get no response and returned an
error. Now on every other box I have used as a client I could then
reload and the page would come up, ie it is only a spurious error
because the dial up connection is slower than the application's
timeout. But with XP it appears to have cached the name server
information so that subsequent connection attempts will also fail,
albeit that they fail immediately, but connections to a new address (
e.g. google.co.uk ) work correctly.
Click to expand...

See if this helps:

http://www.jsiinc.com/subn/tip6500/rh6540.htm
 
Back
Top