Hi Pierre:
I think I know what may be causing your problem, as
I had something similar happen to me, and I had to add
a fix for it.
See if you can run to fix it:
route -n flush
setup
Basically, it was caused by the route table filling
up in a newer tcpip stack, where the older versions had
a set expire to delete old entries, and I have to check
what I changed to fix it . . . {:-)
later,
lin Baden
In
, rcpj@panix.com (Pierre Jelenc) writes:
>
>Oh well, every silver lining must have its cloud, doesn't it...
>
>The good news is that the DSL setup is running well. The bad news is that
>I seem to be having an http/https choke point somewhere.
>
>The symptoms: after a fresh boot, all is well for a while (I don't know
>yet whether this "while" is a time duration or an amount of usage) until
>suddenly some web sites (there will be a list below) simply do not load.
>
>Some of them do not load at all, some (about half; unfortunately I did not
>think of making a list) seem to load something because the proper title
>and favicon are displayed, and sometimes the background color changes, but
>no data actually come up, neither text nor graphics.
>
>Those sites that do load, seem to do so incompletely, although I don't see
>anything obviously missing: even after everything seems to have loaded,
>the loading indicators in SeaMonkey and FireFox continue to twirl.
>
>Once this phenomenon has started, it will not stop. I can close SM and FF,
>the blocked sites are still blocked later, until a reboot. Furthermore,
>the *same* sites also do not load in links, while those that are still
>accessible are also accessible by links (whether PM or text-mode).
>
>After a reboot, when the problem recurs after a while, it seems that the
>same sites that had been blocked before the reboot become blocked again,
>while those that had remained accessible do remain accessible.
>
>While this is happening in OS/2, my elderly Mac laptop (running 8.6)
>plugged into the same router (no wireless: Ethernet cables in both
>instances) will happily visit all the sites, whether accessible or not
>on the OS/2 machine.
>
>My take is that it's not the router (the Mac works), it's not the sites
>themselves (all the the blocked sites load without problem after a
>reboot), it's not the browse (SM, FF, links are equally affected), it's
>not PM (links is affected in both modes).
>
>Also, when I try to load a blocked site, there's a lot of activity
>(blinking lights) on the DSL and Ethernet lines, as though the entire HTML
>code is actually received, but not displayed. In some instances, I even
>have some evidence for that: the amazon.com home page displays title and
>favicon, and the backgound turns white, but nothing gets displayed.
>Nevertheless "View Page Source" shows the entire HTML for the page all the
>way to the final "