Hello - my first post here!
Have been racking my brains over this issue for long time. Relates to sharing broadband internet connection via a broadband router. I remember I had the exact same issue when a dial-up sharing device was in use, several years ago.
The broadband router is configured to dial-out on demand. So, what I want to happen is, when a client computer requests and internet resource (e.g. web page) and the connection status is currently disconnected, then the connection process will be triggered. As far as the client PC is concerned, the client PC is on the LAN since it is plugged into one of the router's LAN ports.
The connect-on-demand process works as designed - except, of course, the connection process takes time - 20 seconds or so. It seems that this is JUST SLIGHTLY in excess of what Windows allows as the maximum timeout before producing a "Cannot find server or DNS error".
Obviously, what I need is for Windows to WAIT just a LITTLE BIT LONGER before timing out the request.
Having scoured the internet, I am starting to feel that the timout settings I require are actually HARD-CODED into the MS TCPIP stack. All the registry settings I checked out with respect to the MS TCP stack don't appear to make any difference. Using Windows ME. I remember this happening on Win98 also. Not sure if it also happens on 2K/XP.
Hopefully the experts here can shed some light. Many thanks for any advice.
Graham Marsh
Hong Kong
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I don't understand why "The broadband router is configured to dial-out on demand". One of the main advantages of a DSL connection over dial-up (besides increased speed) is that it is (or should be) always connected. Couldn't you reconfigure your router so that it stays connected? That would certainly solve the 20+ seconds in finding the DNS server.
>>I don't understand why "The broadband router is configured to dial-out on demand". One of the main advantages of a DSL connection over dial-up (besides increased speed) is that it is (or should be) always connected. Couldn't you reconfigure your router so that it stays connected? That would certainly solve the 20+ seconds in finding the DNS server.
By "dial-out on demand" I specifically mean "establish the PPPoE connection on demand" just to be clear that it's PPPoE I am talking about. I could in fact tell the broadband router to maintain the PPPoE connection all the time, because I do now happen to have unlimited time allocation. However, for those who do not, or for whatever reason, don't wish to maintain a 24x7 connection, I can see that they would have this timeout issue for the first networked PC that happens to be the one that triggers the connection process.
Neither of the comments posted are solutions - I'd even hesitate to call them workarounds. Not the information I am looking for - sorry!! Registry settings to extend timeouts would be along the right lines.
Thanks anyway. I will keep checking back for further responses.
With PPPoE and a broadband router, it will establish the connection automtically (it does this with my Dlink 704 and Linksys BEFSR41. Then, it has a keep alive session to keep the session going if there is no activity. If you set that value to 0, it will hang up the connection when activity discontinues.
I think you must be in an area that charges for internet connection time (like in Asia). I'm in Taiwan and I selected the service where I could use the internet 24/7...they had other options of per hour use.
Try setting your keep-session-alive to 0 (I think this is what the manual said to deactivate keep-alive)
After a while...it should just hang up.
One thing you must do to insure this works...stop all programs like AOL/ICQ/Yahoo. They have keep-alives built in internally.
Never dial a connection
This is a normal setting if the computer is on a LAN (Local Area Network). The WinSock DLL will be set to expect a direct connection via the network rather than via a dialer, & entries within the Hosts file may be important here.
Otherwise, Internet Explorer will always show Page Cannot Be Displayed messages, since it can only show pages from the local cache (Temporary Internet Files, containing pages already viewed) if not connected. Try making the setting on the connections page to dial whenever a network connection is not present. This should slow things up a bit since you do not have a cable modem or dsl which is "always on". If it is always on you are barking up the wrong tree as it is not a registry setting but a router setting that fails to do its job.
It is already set to "dial when network conn not present". In terms of detecting the "presence of a network connection", Windows doesn't care whether it can get to the internet or not, it only cares whether your network cable is plugged into a live port as far as I can see. In that case, Windows "sees" that it is plugged into a live network, and attempts to go directly to the web page, but doesn't know that there will be a delay while the DSL router establishes the PPPoE connection.
Anyway, I recently found some interesting behaviour... it seems that the DSL router *is* establishing the connection *before* Windows times out the connection. I say this because, if I launch IE and try to load a web page the first time, then a few seconds later launch another window, the *second* window will successfully get to the site, but the *first* window will eventually time out even though I am now browsing OK on the 2nd window. Only when the first window is *refreshed* will it behave normally.
This being the case, it seems that if I could change the "re-try" behaviour (e.g. retry for more times or for a longer period) then it might work.
cheers
gm
You may also want to have your temporary internet file handling changed. Try changing the settings on temporary internet files to "check for newer versions of stored pages" to either "every time you start Internet Explorer". I am assuming you have deleted your temporary internet files to see if this would change anything for you.
Business Accounts
Answer for Membership
by: ridPosted on 2003-06-04 at 09:35:55ID: 8650106
You might consider setting the start page to a local file instead. At startup IE would display this locally stored file, in which case a DNS lookup is not necessary.
When connection is established, you can begin browsing at will.
You could make a simple HTML document by using Word, if available, or by going to some site and try making it available off-line. This should store all needed
files on your hard drive, to be accessed as start page.
Regards
/RID