chatting with support again...

Ok, an observation:

From the connection I have that does work, is using two different routes. One works, and one doesn't (luck of the draw). Here is the route that fails:



And the one that works:




Snipped the common stuff. #15 is the last hop common between the two, then the route seems to change occasionally. I'd say there is a screw up with some of The Planet's routing:

I think you've hit the nail on the head.

Router A sends your request to Router B. B sends it to C. C sends it to D. D sends it to E, but E gets confused and sends it back to B. Then B sends it to C. (haven't we been here already?) And round and round it goes.

In theory, a packet of data could live forever, going round and round in circles in a misconfigured mess like this. But, every data packet has a special field called a Time-to-Live (TTL). It contains a number, usually something fairly high like 256. Every time a router passes this packet on to the next hop, it replaces this number with the next lower number. If a router ever receives a packet with a TTL of zero, it must discard it. That way if you get an endless spiral, the TTL eventually gets reduced to zero and is dropped.

Since the title of this thread is "DNS issues", I'll add a little more to sladnas's explanation. When you tell your browser to go to DT, first off your browser says "WTF is dirttreaders.com? I need an address!" See, all this routing stuff requires a numeric address, sort of like a phone number. So your 'puter sends a request to a "DNS server" to look up the numeric address. DNS is the Domain Name System, which is basically a globally distributed database of names (like "dirttreaders.com" or "google.com") and what their numeric addresses are. Your puter first contacts the local DNS server, which your ISP provides. If it's never heard of dirttreaders, it goes to a higher-authority server to get the info, and so on. Once your local DNS server gets the info back to you, it remembers it for the next person who asks for it. Once your computer gets the numeric address back (it's called an IP address), it uses that to send a request to the actual web site. The request goes to your local ISP's router (sometimes called a gateway), who looks at the IP address and decides where to send it next. Each router along the way does the same thing: look at the address, and decide where to send it next. Eventually/hopefully, it reaches the correct final destination without going into a death spiral.

i wonder if this would work: someone that isn't getting through, contact your isp's tech support.

anyone willing to endure that?

Gawd, no! It's much more fun spewing techno-babble to the masses!

Not me. Too much hassle dealing with those guys.

_________________
THOSE WHO KNOW, RIDE TURNER

sladnas and chuckanado, thanks for your posts. I learned something new!

Stop being a chode poop7 & get this fixed, as of this morning, still can't log on from my crackberry.

You

_________________
If you have any Real Estate questions, or looking to buy or sell a home, PM me.

i just got off a chat with att support and they're retarded. they say the browser works different than a computer browser and aahhhhhhhhhh!!!!!! fuck i wanna kill something right about now.

[quote=\"Ld00d\"]i wonder if this would work: someone that isn\'t getting through, contact your isp\'s tech support.

anyone willing to endure that?[/quote]
I will take one for the team. BRB

_________________
Ride it until they CDFW it.

[quote=\"24v\"][quote=\\\"Ld00d\\\"]i wonder if this would work: someone that isn\\\'t getting through, contact your isp\\\'s tech support.

anyone willing to endure that?[/quote]
I will take one for the team. BRB[/quote]

Thanks for the spit-chewing gum-and-baling wire solution you provided through MTBR, but I\'m looking forward to being able to log on the good old-fashioned way.

_________________
A bicycle is a splendid thing.
~Ernest Hemingway

Tech support says whoever the ISP is for the hosting company is blocking AT&T\'s network. I was on the phone with them for an hour, and that is what I got.

_________________
Ride it until they CDFW it.

I know someone using AT$T that's also frozen out, so good call.

Perhaps if there is a fix on the user side of things it could also be posted on mtbr.com. At least they can reach that for info. Posting here only works if you cell is frozen but you computer not. That is, if it's a user work around.

_________________
Ambition is a poor excuse for not having sense enough to be lazy. ~Milan Kundera

[quote=\"jSatch\"] Posting here only works if you cell is frozen but you computer not. That is, if it\'s a user work around.[/quote]

Actually, anyone can get on even if they cannot do it like normal. All they have to do is go through a proxy. If someone cannot get on, tell them to go to:

http://www.freeproxyserver.net
or
www.freeproxyserver.ca
They can type dirttreaders.com in the box, and it will bring them here.
Then if they want to logon, follow the quote below.

You can login, just login, click submit, and then when it takes you to the redirect screen click on \"view active topics\" right away. For some reason the proxy doesnt like the redirect screen, so as lng as you don\'t let it sit there, you will be fine.

_________________
Ride it until they CDFW it.

Another work around (which is what I am doing at the moment) is to use a website translator. I am using:

http://www.worldlingo.com/en/websites/u ... lator.html

and translating the DT website from Japanese to English.... there is no Japanese on this site and comes out as normal. Just FYI.

_________________
Panoramic Places