Post by dd on Apr 7, 2013 20:03:44 GMT -5
I first reported this problem in the corrections thread but quickly realized, with Chris's help, that I misunderstood the problem.
I'm wondering if anybody else is encountering this or if anybody lots smarter than me can help me figure it out.
I often find that when I first attempt to go to soxprospects.com (or I get an error saying I should try to reload the web page later. After two or three minutes this stops happening and I get through thereafter.
When I say "I first attempt", I don't mean that the computer has been off, just that I'd closed my previous session with SP.
This happened a few minutes ago and I pinged www.soxprospects.com. It resolved to 98.136.92.79 which is an address belonging to Yahoo, the host for soxprospects.com (AIUI). The Request timed out ad infinitum.
After I was able to get through with the browser, I stopped and restarted the continual ping and it resolved to 67.195.61.65. That one also belongs to Yahoo, which makes sense.
As I see it the problem could be my PC, my router, Verizon (my ISP) or Yahoo. The last two choices would likely indicate that I'm not the only one having the problem.
Any ideas anybody?
- Dick
I'm wondering if anybody else is encountering this or if anybody lots smarter than me can help me figure it out.
I often find that when I first attempt to go to soxprospects.com (or I get an error saying I should try to reload the web page later. After two or three minutes this stops happening and I get through thereafter.
When I say "I first attempt", I don't mean that the computer has been off, just that I'd closed my previous session with SP.
This happened a few minutes ago and I pinged www.soxprospects.com. It resolved to 98.136.92.79 which is an address belonging to Yahoo, the host for soxprospects.com (AIUI). The Request timed out ad infinitum.
After I was able to get through with the browser, I stopped and restarted the continual ping and it resolved to 67.195.61.65. That one also belongs to Yahoo, which makes sense.
As I see it the problem could be my PC, my router, Verizon (my ISP) or Yahoo. The last two choices would likely indicate that I'm not the only one having the problem.
Any ideas anybody?
- Dick
