Re: "Unable to find server" timeout.
- From: The Pearles <thisgroup@usenet>
- Date: Thu, 08 Sep 2005 00:27:26 +0100
On Tue, 6 Sep 2005 01:55:50 -0400, "Robert Aldwinckle"
<robald@xxxxxxxxxxxxx> wrote:
>"The Pearles" <thisgroup@usenet> wrote in message
>news:d0cph1172cnv8r3gqv548j1m8b4utombeb@xxxxxxx
>...
>> Both machines are set to use HTTP 1.1 both with and without proxies.
>
>
>That's good. That means that you can use caching better
>--once you are connected.
>
>
>>
>> I haven't given up, yet though. I did find a difference in the
>> registry between the two machines. The key
>> HKCU\Software\Microsoft\Windows\Current
>> Version\InternetSettings\Connections has an entry for each of the DUN
>> connections (plus a couple more) and, on the "good" (W98) machine
>> there is a "LAN" entry, which contains the IP address of the gateway.
>> I have to way of knowing what added this, so I manually added the same
>> values to the "faulty" (WinME) machine. No effect at all.
>>
>> These settings also appear in HKEY_USERS\DEFAULT\Software... etc.
>>
>> I also discovered that if I enable DNS via Control
>> Panel\Network\TCPIP\Properties (it doesn't seem to matter whether I
>> enter my ISP DNS addresses or the gateway address) the timeout
>> increases from 15 seconds or so to around 30 seconds. Still not quite
>> long enough for the gateway to dial my ISP and get connected, but a
>> move in the right direction, so maybe this timeout is set
>> automatically depending on other settings, like DNS, proxies, which
>> might alter the time needed for a server to respond.
>>
>> There are a good many MSKB articles about DNS problems of various
>> kinds, and one of them, 181050, tells me that the default timeout for
>> IE6 is 60 minutes (!). I'd be happy with 60 seconds.
>> I am not seeing anything like that timeout on either machine, so I am
>> now thinking that something (winsock related?) within WinME is
>> overriding IE6, so maybe it's ME not IE6 that's the problem, but I am
>> into uncharted (for me) waters here. MSKB 259818 covers a situation
>> where ICS must override this timeout.
>
>
>If it really is a DNS timeout neither article applies.
I'm not as sure of this now as I was when I first asked the question.
The
>KB181050 is about a timeout for the request once the connection
>is established which would be after a DNS timeout would be applicable.
>KB259818 refers to a timeout for establishing the link which would be
>before a DNS timeout would be applicable.
>
>Does KB259818 describe your hardware setup?
No, it doesn't - I'm not using ICS at all.
> E.g. ICS connection
>from WinME machine to host Win98 machine which does the dial?
>If the Win98 machine is already connected and you then try to connect
>with the WinME machine is there any problem? If not, it looks to me
>that the WinME machine thinks it is connected to a LAN and oblivious
>of any delays in establishing a dial-up link.
Well, since all the machines access the "internet sharing device"
which is set up as a gateway on the LAN - you may be right. - but
where do I go from here?
> Then changing that should be
>the focus of your research and testing. And in that case this newsgroup
>probably is not the best place to be looking for help with that issue.
>
>
>In fact, the only time that I have seen the possibility of changing DNS
>timeout values was posted long ago in a reply by Kent W. England [MVP]. Here is a link to his post which I used to reference
>occasionally along with
>the search which enabled me to find it:
>
>http://groups.google.com/group/microsoft.public.windows.inetexplorer.ie6.browser/msg/ddbc009fe9819375?as_umsgid=u832VJRpBHA.1088@tkmsftngp02
>
This is very close to my set up, I am not using a router, but not the
exact problem. although I'm sure it's on the right lines.
The problem is not a delay in initial connection, but that IE never
connects first time (i.e. if IE has to wait for the sharing device to
dial out) I always get "Unable to find server or DNS error". Hitting
"refresh" always brings up the page OK. Subsequent DNS searches work
perfectly.. There are three machines using the "internet sharing
device" (D-Link DP-602). They run WFWG (using IE5 and NS3) W98 and
WinME (both using IE6 SP1), only the WinME box has the problem.
-snip-
>
>I suspect that you could probably use this information as a way to
>deal with your symptom but I also suspect that it would probably not
>be the best way to do it.
This prompts two questions.
First, where do I set the DNS timeout, since I don't have the key:-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\......
Do I simply add a TCPIP\parameters "layer" to :-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services ?
or does it go somewhere else in W98?
Second, Why might this not be the best way to cure the problem, and
what would?
And very many thanks for a very informative response -
jp.
.
- Follow-Ups:
- Re: "Unable to find server" timeout.
- From: Robert Aldwinckle
- Re: "Unable to find server" timeout.
- References:
- Re: "Unable to find server" timeout.
- From: Robert Aldwinckle
- Re: "Unable to find server" timeout.
- From: The Pearles
- Re: "Unable to find server" timeout.
- From: Robert Aldwinckle
- Re: "Unable to find server" timeout.
- Prev by Date: Re: IE7
- Next by Date: Re: IE won't play embedded video (and goes to 100%)
- Previous by thread: Re: "Unable to find server" timeout.
- Next by thread: Re: "Unable to find server" timeout.
- Index(es):
Relevant Pages
|
