-----Original Message-----
From: Michael Andersson [mailto:micand@vh.volvo.se]
Sent: 11 August 2001 13:28
To: 'Kavanagh, Darrell'
Subject: SV: [SLE] Dial on DemandHi!I´ve had the exact same problem for quite some time now. Although this on the Windoze-boxes on the LAN that has this problem. I didn´t think this was browser-related but rather network-related and have been trying to find some info on a solution without any luck. The windoze-boxes all use IE. If you find something out I´d be glad if you drop me a line. I´ll do the same if I find something out.By the way, I have a ISDN-connection so I don´t think I have a timeout problem. The ISDN-connection gets up and running long before I get the timeout-error in the browser.BRMike A-----Ursprungligt meddelande-----
Från: Kavanagh, Darrell [mailto:Darrell.Kavanagh@newellandbudge.com]
Skickat: den 9 augusti 2001 15:39
Till: suse-linux-e@suse.com
Ämne: [SLE] Dial on DemandHi everyone
I've just got SuSE 7.2 (kernel 2.4.4) installed on my home pc and have configured dial-on-demand to connect to my ISP (dynamic IP addressing) using the supplied wvdial.dod script. Everything works fine (almost).
When using any flavour of Netscape or Mozilla, and Galeon, the first request to a remote site when the modem is down does not work. The "not found" message comes back after modem has connected. Hitting the refresh button after this has no effect, but refreshing the URL by double clicking the address then hitting enter loads the site immediately .
The puzzling thing is that if I use Konquerer, I do not get this problem. This browser somehow waits until the IP connection is established - maybe it is sending the initial request multiple times, rather than just waiting for a response to the first until it times out as the other browsers/mail clients seem to do. Or maybe the time out settings are different.
I have tried the various suggestions regarding ip_dynaddr and aysnc dns for Netscape/Mozilla, with no effect. I have also tried using ip_resend, the utility shipped with my dist.
I am thinking that tweaking the Mozilla preferences might help, although I have already tried putting massive numbers into any which seem to relate to timeouts for DNS, IP, HTTP etc, without any success. Could it be that I need to repeat the request after a specified time if no reply is received, and can this be set anywhere in the Mozilla conf files? Does anyone know their way round the Mozilla config files?
Many thanks,
Darrell.
******************************************************************************** This electronic mail system is used for information purposes and is not intended to form any legal contract or binding agreement. The content is confidential and may be legally privileged. Access by anyone other than the addressee(s) is unauthorised and any disclosure, copying, distribution or any other action taken in reliance on it is prohibited and maybe unlawful ********************************************************************************