[Virtualacorn-list] Loosing internet connection with XP

[ralph_valmai at ntlworld.com]

In message <mpro.l193s500qupkd01nw at wingsandbeaks.org.uk.invalid>
          Jeremy Nicoll - ml virtualacorn 
<jn.ml.vac.83 at wingsandbeaks.org.uk> wrote:

> ralph_valmai at ntlworld.com wrote:

<Snip>

>> Windows. "Windows cannot make a connection" or some such words. It
>> tells me a few obvious things to try and then asks me if I want it to
>> attempt a repair. This takes a little time but always gets me back on
>> line.

> But is it Windows after you've tried to do something that you think needs an
> internet connection, or does it tell you this out of the blue?

It isn't out of the blue, but occurs when I ask to view a web page.

> Do you have a software firewall that would (in its logs) show what internet
> activity was ongoing?

I'm a bit pressed for time here, having been away for a few days with 
urgent things to do on my return, but I will try to set aside time to 
look at this tomorrow. However, I am using the firewall that is part 
of (or comes with) XP.

<snip>

> Ages ago I found that (with my VM cable connection) executing almost any
> command at all (not internet related stuff) took forever unless my firewall
> has been told that the DNS servers I'm connected to are 'trusted'.  Whenever
> (though it is rare) I go to a new network (eg if visiting a friend) I hit
> the problem again.  It was clear (at the time) that there was a timeout
> being waited for in each case.  With no internet connection there was an
> immediate failure of whatever-it-was to communicate with the outside world,
> and with a 'trusted' DNS server whatever-it-was worked ok... but otherwise
> it took 1-2 /minutes/ to decide that it should just do the command anyway.

This seems somewhat similar, except that I have to go through a 
dialogue that (quickly) leads to the suggestion that the system could 
attempt to repair the connection if required. It also takes a couple 
of minutes once the process is started.


> I have no idea what's causing it.  Nor do I know if the problem still
> exists.  But it does suggest that there may on my machine (and perhaps yours
> too) be something that makes very frequent DNS lookups.

Well, it is to soon to be certain. Since my return the problem hasn't 
manifested itself yet.

Ralph



-- 

Ralph & Valmai Stevens
In leafy Epping