At time of posting...

Are some of you guys having similar problems? Can't get about 50% of sites, can't log onto EQ (first got 1017 at login, now can't even get that far)

Others seem to be suffering difficulties, yet there are still many who say... "what problem? Everything's fine here!"

ust admit, the other folks with the same problem have mainly been UK, so maybe one of the pipes is broken.

(Maybe the same pipe we tried to whip Bush with on his way back! *chuckles*) (Sorry couldn't resist - hey, just kidding, stand down your flames! *winces*)

Haven't had any problems here, on the East Coast in the US. Some sites are acting slow..like EZBoard...what a surprise =-p But beyond that, it's fine.

And please don't be kidding =-( Whip him with the pipe for a very long time, please use a whole crowd of pipe whippers.

Just tried to log in and can't get past login... :(

ezBoard acting slow is nothing new *smirk* I still visit a couple, and it hurts. Unfortunately they don't really have a choice, or so it seems!

*cough*eqlogin3*cough*

/sigh Still can't connect to login server. Any ideas?

*sniffle*eqhost.txt*cough*eqlogin3*snort*eqgame.ex e patchme*haarrk*
/em looks around and hurries away.

For a fellow Squall-avatar-user it'd be nice if he didn't speak in elitist riddles and just speak the knowledge that is to be shared.

I've plucked usefulness out of the riddles however, here's the translation:

Go to your Everquest directory

Edit eqhost.txt (preferably in Wordpad rather than Notepad for the correct formatting)

change all the eqlogin1 entires to say eqlogin3

Bypass the patcher by running 'eqgame.exe patchme'
e.g. Start, Run, enter the following into the box (WITH quotes):
"C:\program files\Everquest\eqgame.exe" patchme
Click OK

This does indeed work. You could've been clearer Kagonis, but thank you for the pointer :)

Huh? I never did it, I swear ;)

Live 2 hours away from the servers in San Diego and never have this problem. /nod

"California! Land of Fruits and Nuts!"

Few things happened last night in uk btw.

NTLs resolvers or proxys went mental.
They all just went 'errr, stuff this' and died.

As a result, no web pages would work.
They seemed to bring some of them back up which ment on a 1/<however many servers they have> chance of hitting a web page.

Therefor you sometimes got some and sometimes didnt.

I ended up manually putting in :
158.43.128.1 into my dns settings to get round the problem.
( uunet's primary dns server )
I knew the addy of the top of my head as, er, I used to run the server ;)

ON top of that... and this is classic, uunet ( worldcom / MCI - whatever they called today ) who supply most of the main pipes around uk and transatlantic had an 'issue'
This 'issue' couldnt be resolved.
Know why ?
Cosssss they desided to relocate our office to Reading and none of the techys wanted to go... as a result, nobody left who knew how to fix it :P
Even the folks in the states didnt know the config.
Skillz.
Think its fixed now though, aint spoke to the folks left there yet this morning ;)

Sooooo there ya have it, 2 reasons why your connect sucked ass yesterday.

Bosh that ip addy into your DNS, should sort out problems. Its rare that server goes down ( well used to be ;) ).

- nieros

Interesting stuff nieros - cheers

so, wait, that was
"C:\Califiornia!\Land of Fruits and Nuts!" chenierneedsanewsig

... right?

I heard on the news that a major fiber optic line from the U.K. to the U.S. was damaged, which would explain the trouble you're having. It's not a local issue, since the connection from San Francisco is just fine.

Thankfully, all seems well now. Guess they patched the cable up (speaking metaphorically)