[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fwd: Windows Limitation Curbs Web Browsing
>From: Mitch Stone <[email protected]>
>To: Multiple recipients of list AM-INFO <[email protected]>
>Subject: Windows Limitation Curbs Web Browsing
>
>http://7am.com/cgi-bin/twires.cgi?1000_t9809180.htm
>
>Windows Limitation Curbs Web Browsing
>11:00am PDT, 18 September 1998
>
>"Site Unreachable; No Response From Server" - what does it mean when you
>get these, or similar messages when trying to access a Web site?
>
>Maybe the web site you're trying to connect to is down. Perhaps one of
>the data links between your computer and that site has failed. Or,
>perhaps it's just that the Net is getting too big!
>
>At least one Net user has discovered that the Net has grown too big for
>Windows-based software.
>
>When Kim Hendrikse of Nexial Systems (new window) discovered some large
>and normally very reliable sites half a world away were becoming
>increasingly unreachable, he investigated further.
>
>Using the standard "traceroute" utility (that's tracert.exe for Windows
>users), Hendrikse discovered to his consternation that the path from his
>computer in the Netherlands to the ASB Bank (new window) in New Zealand
>was an astounding 34 hops, two more than 32 hops that Windows-based
>Internet software allows.
>
>As a result, his Windows 95 based computer was erroneously reporting that
>the site was down - when in fact it was alive and well - but two hops too
>far away.
>
>Looking at this traceroute (new window) from a site based in The
>Netherlands to a popular newspaper site in New Zealand shows just how
>many hops are required for connections between the two countries. Indeed,
>under the standard Windows configuration this, and many other New Zealand
>sites are effectively unreachable from parts of Europe.
>
>As the Net continues to grow it is likely that path lengths will increase
>and that means the once "more than adequate" setting of 32 hops in
>Windows 95 software may begin to interfere with long-distance Web
>surfing.
>
>Hendrikse says he's found the solution to the problem though...
>
>You add the string value for "DefaultTTL" and set a value of say "64"
>(The same as my unix machine) into the registry with regedit in the path:
>
>
>Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP
>
>The document that details this is:
>
>http://support.microsoft.com/support/kb/articles/q158/4/74.asp
>
>However, this is hardly the kind of solution that will appeal, or even be
>practical for the average Net surfer to employ - tampering with the
>Windows registry is not something for the faint-hearted.
>
>---
>
>James S. Baughn http://i-want-a-website.com/about-microsoft
>
>Mitch Stone
>[email protected]
>
--
Eric Bennett (http://www.pobox.com/~ericb/)
Cornell University, Field of Biochemistry
377 Olin Chemistry Lab
What's good for Standard Oil is good for Microsoft.
===
This message was sent to mph-humor. No guarantees of actual humor are
provided. Archives and instructions are available from
<http://www.pobox.com/~mph/humor/>.