I have no idea if this is the right place to pose this type of question, feel free to direct me to a better place if is not.
We have had (a)dsl service for 2 years at 386k down. Other than a spot of trouble last November, it has worked flawlessly until June 27 when it died. We contacted the provider and ....
They detected a disconnect order from the trouble that we had last Nov. Without boring everyone with the whole story, the said that we could restart the service. So we submitted the request.
Fast forward to the service being started. We got connectivity but couldn't get out on http. I called service again and now they say I am 25000 feet away from the co and therefore can't get service.
So here is what I empirically know: I had good service for two years, it stopped3 weeks ago. I now have 13.5 db s/n and 64.5 db line atten. I can ping 512 bytes anywhere on the net. I can do traceroutes to most places on the net (for some reason att.com hangs and my provider is att (used to be sbc). When I go through my router and have my Linux box up, the weather comes through (assume its a low bw udp transmission). When I execute Thunderbird, I get connected to the server but when I send the password it usually says that the name/password is incorrect. If it does connect, it will timeout on trying to deliver a message.
The technician that came to the house said that the upstream data path is bad but they are going to deny service anyway since we are so far away. Anyone have ideas of things that can be checked or fixed?