![]() |
As Steph said, I was having the same issues. Now that I know it's not on the LOT side of things, they'll be getting contact from me, too.
|
Don't know if these will work for everyone, but 202.27.184.3 and 202.27.184.5 are DNS server addresses that at least one Earthlink customer has been given as a work around. You could give those a try while waiting for a response from customer service.
|
Those are the ones that earthlink gave me last night and they worked for me.
|
I'm going through a proxy server right now. Neither of the DNS server addresses work for me. I need to go get back with them, since I"ve now rebooted, and get this fixed so I can type in the url.
And 'oh, it's not an Earthlink issue' - bull pucky. The only people who can't get to LOT are earthlink customers and they USED to be able to get to it, so YOU (earthlink) clearly changed something. Can you tell I'm a little peeved? |
Well, if anybody in SoCal is interested in a reliable ISP, check out www.dslextreme.com
I've been with them for several years now, and it's been a wonderful time. |
Quote:
Great, now the servers will be overloaded and shut down.:rolleyes: Thanks for posting them GD!;) :D |
Quote:
|
Well... I reconfigured the router to use the DNS addresses GD posted. I still can't bring up LoT on m desktop computer, but now I can from the laptop (via a wireless connection to the router). :rolleyes:
|
This is the first issue I've had with them that wasn't easily resolved. None of the options they gave me except the proxy server (which is molasses-like) worked - they said they'd escalate to the engineers and that he thought it was on the Earthlink side of things (wow, you think?)
I'd consider switching to a cable-system, but I was able to come home a lot earlier last year because my phone (and therefore my DSL) was working a couple of weeks before my cable was working. I felt for the neighbors that have ALL their communication through Cox Cable. I can work from home if I can't work from the office only if I have a high-speed connection. |
From what I've seen, they've known about this problem for 4 days and still haven't come up with a permanent fix. :rolleyes:
|
All times are GMT -7. The time now is 06:10 PM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.