Maybe it's not 'their' problem...
but a dns server / network / relay / problem anywhere from originating ISP thru relay points thru webhost to endpoint isp... try this quick workaround:
neteller.com with & w/ the www ---- http & https.......
there's a program that helps in these cases: in the background / on the fly it's bypassing servers with address translation issues & other bottlenecks...& it caches all that info in your ram, so that your connection doesn't have to go fetch someone to translate each time you go to a new site-- ergo speeding up your browsing as well.
Treewalk if your're on win9x, get their BindLe instead.
but a dns server / network / relay / problem anywhere from originating ISP thru relay points thru webhost to endpoint isp... try this quick workaround:
neteller.com with & w/ the www ---- http & https.......
there's a program that helps in these cases: in the background / on the fly it's bypassing servers with address translation issues & other bottlenecks...& it caches all that info in your ram, so that your connection doesn't have to go fetch someone to translate each time you go to a new site-- ergo speeding up your browsing as well.
Treewalk if your're on win9x, get their BindLe instead.
I don't either.JAYBIRD0711 said:
uppy: What i meant was: each url corresponds to an actual number address-- so each time we click / type a link, some computer somewhere has to look up that letter address & find its correspoding number address, where it's located, etc. And each click / request of ours does not go directly through one pipeline to the desired party: it usually goes thru several computers, servers, relay, routing points along the way.
So now, how about a program that keeps a lot of that data & the servers info in cache-- so another computer does not have to be queried...& if there's glitch or significant slowdown anywhere, our packets are immediately routed via another direction...
Now IF there's a case of some getting in & some not 'at the same time', then there's a problem at some ISP or somewhere along the way....someone having issues like these should always post their ISP & geographic location, and after a few posts we'd 'maybe' get a sense where or with who the issue might lie...'before' resorting to the usual diagnostics of ping/trace/etc.
But also, problems like these are usually fixed fairly fast-- before any significant troubleshooting gets going.
I guess TT is right. It's hard to tell if 'simultaneously' some folks get in & others don't....
