Everytime I try to open 2gnt, Mozilla says the connection cannot be completed and that the 2gnt server is taking too long to respond. I have tried from work and home on different computers. All same response. What can I do to fix this, is it my machine?
#885, "RE: 2gnt connection issues" In response to Reply # 0
I could not log on at all today from work. I ran repeated tracerts to 2gnt.com and found the packet being tripped up between a couple routers for Level3.net. I also had my GF and a friend run them after Dino told me the site was up. Turns out it's likely the ISP - in our case Qwest - fucking something up as usual. All three terminals with connectivity issues are running through Qwest by my testing.
I also found a couple websites which would run a tracert to a site for you and display the results. Both of them went right through the router I was hanging on and hit their target.
I called Level3 and they told me that I would need to contact the ISP and have them troubleshoot and elevate to Level3.net if required, but everything they had tested fine.
If you're using Qwest, you're fucked. I don't even want to go to work tomorrow because of this.
#890, "RE: 2gnt connection issues" In response to Reply # 3
This is what I get all day .
"Error 504 '' Gateway Timeout. Try reloading the Web page. Retype the address in your browser. Check your computer's Internet connection."
It happens everytime I go to a thread or a diffrent section on 2gnt. I cant get into the 4g63 section at all at this point. I am just going to go away for a week or so and see if things change. Right now its just way to annoying to try to surf these forums right now.
--Remy
---------------------------------------- GT35 and stuff. Lucky Number 6 ...
#891, "RE: 2gnt connection issues" In response to Reply # 6
It's been happening to me for the last week or so... using Comcast internet, DirecWay Satellite Internet and BellSouth DSL. Something is definetely wrong.
#892, "RE: 2gnt connection issues" In response to Reply # 7
Dino and I got this isolated and fixed this afternoon. It was a DNS issue that was resulting requests getting stuck in a routing loop in Level3. The address was wrong because the zone file on the DNS server got overwritten with an older version. Everyone should be up and working tonight. If you guys want it to work sooner from everywhere else add the following entries into your host file ... located typically in c:\windows\system32\drivers\etc.
#893, "RE: 2gnt connection issues" In response to Reply # 8
Stupid F*(&(CKING cron job overwrote my updated zones every night at 12:23. Next time I'd bounce named, shit'd be all fucked up.
This happened once before. I fixed it for good this time, though.
______________________________ If a sentence found online has 35% misspellings or greater and includes at least two racially charged expletives, chances are it is a YouTube comment.
'95 Eclipse TurboGS (garage deco) '95 TSi AWD (restoring a survivor) '97 Talon ESi-T (poor impulse control) '99 Eclipse RS-T (daily beater) '13 Evo X (mostly stock) '17 Sienna (Middle Aged Dad Mobile)
