Its been problematic for 6 weeks. Tell lag, lag lag. But today!

3 freaking times 1017!

WTH is 1017????

I NEVER got a 1017 error until they "fixed" the 1018!

Now instead of 1018 I get 1017...great fix!

And to add insult to injury, me and the dozens of other people who get booted out 3 times today, get treated to the GM moderators in chat channels directing the coversation to a debate between oreos and chips ahoy. Then the next minute they are speculating that its a problem with routers at Comcast ISP. Well, I DON'T HAVE COMCAST AS MY ISP!

I HATE this.

Thanks for your attention.

Hear Hear!
That damned 1017 bug got me last night as well. Bristlebane Server is the most <strong>appropriately</strong> named server in all of EQ (God of Mischief for those of you not keeping score). They even acknowledged the problem Saturday night by taking the server down specifially to allow those people with 1017 issues to come back into the game. Yanno, 386 boxes used to be really great computers but there comes a time when you have to retire them. ;)

Its the monkeys they use to run the servers. They still haven't trained them to not chew on the power cords. Fried monkey smells bad.

In case anyone was wondering what powerful decisions were made as a result of this whole chain of events:

Oreos are favored over Chips Ahoy by eq players on Bristlebane about 2:1.

:rolleyes:

OMFG.... Oreo's rule

Oreo nerf incoming!!!!

1017, I believe is a router error.

Zones are still available and the server is not really down.

Usually only LDs certain people.

<blockquote><strong><em>Quote:</em></strong><hr>1017, I believe is a router error.

Zones are still available and the server is not really down.

Usually only LDs certain people.[/quote]

I am not an internet guru, but since the 1017s occur after the players have made it through the patch server and logged in to the server select screen suggests to me that the router with the error is property of SOE. Oh. And I doubt "it is working as intended".

"suggests to me that the router with the error is property of SOE."

That is my assumption, as well.

We're having a lot of trouble staying connected sometimes, but we're not getting this error message. I'm not sure if it's on our end or theirs.

<blockquote><strong><em>Quote:</em></strong><hr>Hear Hear!
That damned 1017 bug got me last night as well. Bristlebane Server is the most appropriately named server in all of EQ (God of Mischief for those of you not keeping score). They even acknowledged the problem Saturday night by taking the server down specifially to allow those people with 1017 issues to come back into the game. Yanno, 386 boxes used to be really great computers but there comes a time when you have to retire them[/quote]

We had Vulak at 10% and get the message "Bristlebane will be coming down for a brief amount of time to fix 1017 errors."

JOY!

And Whoever mentioned the monkeys - The other servers get monkeys..

We have Sammy the Gerbil. (He probably died though, they go through 7-10 a week.)

<blockquote><strong><em>Quote:</em></strong><hr>
Oreo nerf incoming!!!!
[/quote]
About time, IMO. Too many people are bypassing content to get to the creamy filling.

Used to be a saying -- The wheel is spinning but the hamster is dead.

BB hamster is mummified at this point.