Networking Forums

Networking Forums > Computer Networking > Broadband > ADSL timeout problem ? - webpage not found....

Reply
Thread Tools Display Modes

ADSL timeout problem ? - webpage not found....

 
 
Adrian Brentnall
Guest
Posts: n/a

 
      06-02-2006, 09:37 AM
Hi All

A minor niggle (compared to the complete loss of Broadband thatks to
PlusNet's tinkering last week..)

To get the connection back I had to default the Safecom router back to
factory settings. Since then, applications that access the web
(firefox, ie, Agent, mailwasher) tend to return an error message
indicating that they can't find the web - maybe 2 or 3 times out of
ten.

The error message comes back as soon as 'return' is hit on the browser
- but clicking 'try again' in Firefox usually brings up the missing
page. Almost as if the browser's not giving the Router long enough to
get a response...

Wonder if there's a setting for this somewhere in the bowels of WinXP
Home ? - or maybe it's a router thing. Nervous to fiddle with too much
in case I upset the delicate balance that is PlusNet ADSL !

Thanks
Adrian
======return email munged=================
take out the papers and the trash to reply
 
Reply With Quote
 
 
 
 
Eros
Guest
Posts: n/a

 
      06-02-2006, 09:41 AM
"Adrian Brentnall" <adrian-the papers and the (E-Mail Removed)> wrote
in message news:(E-Mail Removed)...
> Hi All
>
> A minor niggle (compared to the complete loss of Broadband thatks to
> PlusNet's tinkering last week..)
>
> To get the connection back I had to default the Safecom router back to
> factory settings. Since then, applications that access the web
> (firefox, ie, Agent, mailwasher) tend to return an error message
> indicating that they can't find the web - maybe 2 or 3 times out of
> ten.
>
> The error message comes back as soon as 'return' is hit on the browser
> - but clicking 'try again' in Firefox usually brings up the missing
> page. Almost as if the browser's not giving the Router long enough to
> get a response...
>
> Wonder if there's a setting for this somewhere in the bowels of WinXP
> Home ? - or maybe it's a router thing. Nervous to fiddle with too much
> in case I upset the delicate balance that is PlusNet ADSL !


Best thing to try first is do a Windows Update and get all the updates in...
http://update.microsoft.com/microsof...ult.aspx?ln=en
or http://tinyurl.com/7mnnt


 
Reply With Quote
 
Adrian Brentnall
Guest
Posts: n/a

 
      06-02-2006, 09:56 AM
Hi Eros

On Fri, 2 Jun 2006 10:41:17 +0100, "Eros" <(E-Mail Removed)>
wrote:

>"Adrian Brentnall" <adrian-the papers and the (E-Mail Removed)> wrote
>in message news:(E-Mail Removed)...
>> Hi All
>>
>> A minor niggle (compared to the complete loss of Broadband thatks to
>> PlusNet's tinkering last week..)
>>
>> To get the connection back I had to default the Safecom router back to
>> factory settings. Since then, applications that access the web
>> (firefox, ie, Agent, mailwasher) tend to return an error message
>> indicating that they can't find the web - maybe 2 or 3 times out of
>> ten.
>>
>> The error message comes back as soon as 'return' is hit on the browser
>> - but clicking 'try again' in Firefox usually brings up the missing
>> page. Almost as if the browser's not giving the Router long enough to
>> get a response...
>>
>> Wonder if there's a setting for this somewhere in the bowels of WinXP
>> Home ? - or maybe it's a router thing. Nervous to fiddle with too much
>> in case I upset the delicate balance that is PlusNet ADSL !

>
>Best thing to try first is do a Windows Update and get all the updates in...
>http://update.microsoft.com/microsof...ult.aspx?ln=en
>or http://tinyurl.com/7mnnt
>


Thanks for the suggestion.
Did a quick check and MS thinks that we're fully up-to-date...

What's next ? <g>

Thanks
Adrian
======return email munged=================
take out the papers and the trash to reply
 
Reply With Quote
 
Alan J. Flavell
Guest
Posts: n/a

 
      06-02-2006, 10:29 AM
On Fri, 2 Jun 2006, Adrian Brentnall wrote:

> To get the connection back I had to default the Safecom router back
> to factory settings. Since then, applications that access the web
> (firefox, ie, Agent, mailwasher) tend to return an error message
> indicating that they can't find the web - maybe 2 or 3 times out of
> ten.


*Possibly* your DNS settings are sub-optimal, and it can't look up the
name in time. By the time you try again, the DNS lookup has been done
and you get immediate success. Seen that many a time.

Check your provider's recommendations for DNS servers, and either
configure them in your PC directly, or in your router's DHCP server,
whichever is more appropriate for you.

This is only a hunch - it might well be something else. But I'd say
it's worth a try.

> Wonder if there's a setting for this somewhere in the bowels of
> WinXP Home ?


Depends whether you set up the IP configuration explicitly, or told it
to use DHCP (get the IP and DNS settings automatically, I mean).

> - or maybe it's a router thing. Nervous to fiddle with too much
> in case I upset the delicate balance that is PlusNet ADSL !


The ADSL is presumably BT's. Plusnet only gets involved after you've
got that part working.

Things get easier as you develop a better mental picture of which part
does what, so that you don't waste time trying to fix parts that
aren't broken.
 
Reply With Quote
 
Adrian Brentnall
Guest
Posts: n/a

 
      06-02-2006, 05:29 PM
HI Both

On Fri, 2 Jun 2006 20:17:35 +0100, jannerboy
<(E-Mail Removed)> wrote:

>
>Alan J. Flavell Wrote:
>> On Fri, 2 Jun 2006, Adrian Brentnall wrote
>>
>> *Possibly* your DNS settings are sub-optimal, and it can't look up the
>>
>> name in time. By the time you try again, the DNS lookup has been done
>>
>> and you get immediate success. Seen that many a time.

>
>yes, i agree
>most ISPs have 2 DNS servers (a & b)
>each request elicits a response from either a) or b) on a random basis
>if one of the servers is flakey, then 50% of the requests will fail.
>this could be the cause of the symptons experienced.
>
>
>
>ISPs usually assign the DNS sever IP addresses dynamically.
>but there is an option on most routers to enter them manually (usually
>on the 'basic settings' page.
>determine which is the 'good' IP address, and enter that manually.
>web pages, etc. should then load more successfully.


Hmm - didn't know that you had to set that bit up manually <g>

My router only seems to have one 'slot' for DNS - but plugged in
Plusnet's recommended 212.159.13.49 - and on the basis of a short test
it seems to be working fine ! Many thanks !

I suppose that when I move to Ireland (soon!) and get a new ISP I'll
need to find out what their primary DNS is and plug that in instead ??

Thanks again
Adrian
======return email munged=================
take out the papers and the trash to reply
 
Reply With Quote
 
Alan J. Flavell
Guest
Posts: n/a

 
      06-02-2006, 06:06 PM
On Fri, 2 Jun 2006, Adrian Brentnall wrote:

> Hmm - didn't know that you had to set that bit up manually <g>


You don't *have* to, but it sometimes helps, as you've found.

ADSL routers typically offer to relay DNS requests automatically, so
you'd configure the router's DHCP table to say that the DNS server was
itself (192.168.1.1 - or whichever your own router uses at its own
address). Then you'd configure the hosts to get the DNS automatically
(i.e to get whatever the DHCP lookup tells them to use).

And this works fairly well, but sometimes it goes crabby. Then, a bit
of manual tweaking can help...

> My router only seems to have one 'slot' for DNS - but plugged in
> Plusnet's recommended 212.159.13.49


Yup, that should be fair enough. If it gets crabby, change 49 to 50.
And there's a third address in their list...

There's basically two other options, with increasing levels of
nuisance for the user (especially if you move around, e.g with a
laptop that you use in different places):

- configure the router to know some good DNS server(s) explicitly -
mine actually has slots for two - you say yours only has one.

- configure the individual hosts explicitly to know the address(es)
of suitable DNS servers, instead of getting them automatically.

> I suppose that when I move to Ireland (soon!) and get a new ISP I'll
> need to find out what their primary DNS is and plug that in instead
> ??


Yup.

all the best
 
Reply With Quote
 
jannerboy
Guest
Posts: n/a

 
      06-02-2006, 07:17 PM

Alan J. Flavell Wrote:
> On Fri, 2 Jun 2006, Adrian Brentnall wrote
>
> *Possibly* your DNS settings are sub-optimal, and it can't look up th
>
> name in time. By the time you try again, the DNS lookup has been don
>
> and you get immediate success. Seen that many a time.


yes, i agree
most ISPs have 2 DNS servers (a & b)
each request elicits a response from either a) or b) on a random basis
if one of the servers is flakey, then 50% of the requests will fail.
this could be the cause of the symptons experienced.



ISPs usually assign the DNS sever IP addresses dynamically.
but there is an option on most routers to enter them manually (usuall
on the 'basic settings' page.
determine which is the 'good' IP address, and enter that manually.
web pages, etc. should then load more successfully

--
jannerboy
 
Reply With Quote
 
Adrian Brentnall
Guest
Posts: n/a

 
      06-02-2006, 07:51 PM
HI Alan

On Fri, 2 Jun 2006 19:06:15 +0100, "Alan J. Flavell"
<(E-Mail Removed)> wrote:

>On Fri, 2 Jun 2006, Adrian Brentnall wrote:
>
>> Hmm - didn't know that you had to set that bit up manually <g>

>
>You don't *have* to, but it sometimes helps, as you've found.
>
>ADSL routers typically offer to relay DNS requests automatically, so
>you'd configure the router's DHCP table to say that the DNS server was
>itself (192.168.1.1 - or whichever your own router uses at its own
>address). Then you'd configure the hosts to get the DNS automatically
>(i.e to get whatever the DHCP lookup tells them to use).
>
>And this works fairly well, but sometimes it goes crabby. Then, a bit
>of manual tweaking can help...
>
>> My router only seems to have one 'slot' for DNS - but plugged in
>> Plusnet's recommended 212.159.13.49

>
>Yup, that should be fair enough. If it gets crabby, change 49 to 50.
>And there's a third address in their list...
>
>There's basically two other options, with increasing levels of
>nuisance for the user (especially if you move around, e.g with a
>laptop that you use in different places):
>
> - configure the router to know some good DNS server(s) explicitly -
> mine actually has slots for two - you say yours only has one.
>
> - configure the individual hosts explicitly to know the address(es)
> of suitable DNS servers, instead of getting them automatically.
>
>> I suppose that when I move to Ireland (soon!) and get a new ISP I'll
>> need to find out what their primary DNS is and plug that in instead
>> ??

>
>Yup.
>
>all the best


Thanks for clearing all that up - possibly more information than I
need or can comprehend <g> - but interesting all the same <g>

Seems to be running fine now (fingers crossed !)

Thanks
Adrian
======return email munged=================
take out the papers and the trash to reply
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Configure ARP-Request-Timeout? (NOT Cache-Timeout!) Mario lzteM Linux Networking 0 07-28-2008 09:41 AM
Wanadoo timeout problem this morning..? Ivor Jones Broadband 2 04-22-2006 11:16 PM
ADSL Idle Timeout - is there such a thing? cerberus@address.invalid Broadband 9 11-05-2005 11:04 AM
problem with NFS timeout options Tasos Kotaras Linux Networking 1 06-08-2005 08:11 AM
Strange VPN timeout problem. Need help. Nate Windows Networking 0 10-12-2004 03:22 AM



1 2 3 4 5 6 7 8 9 10 11