Just fixed my error 1017 problem
 

I spent about 6 hours yesterday screwing with settings, updating (in most cases already current) drivers, installing and reinstalling the client and all the tools/patches, checking and rechecking router and firewall settings, even using my phone as a hotspot to take out my internet connection from the equation.

Solution
Proc: AMD FX-9370 stock at 4.4 GHz, 8 cores.

Went into the BIOS, dropped the clock multiplier from 22X to 18X dropping the core speed down to 3.6 GHz.

Logged right in, played for about 11 hours straight, no problems.

Note: Software (AMD Overdrive) did not work for me, this had to be done in the BIOS.

-encopitt

This worked for me as well. The game ran fine on my PC, but on my son’s it would just kick back to the login screen after selecting a server. (Only occasionally would he actually see the error 1017 message, but that seemed to be what was happening.)

After googling variations of “[motherboard brand] disable overclocking in bios”, I started to find what keywords we needed to look for and disable. EQ worked like a charm after that.

I've played with this a bit more.
CPU multiplier (Clock speed) - results:
18X (3.6G) - Works fine
19X (3.8G) - 1017 error
20X (4.0G) - 1017 error
21X (4.2G) - Can't connect to server error
22X (4.4G) - 1017 error
23X (4.6G) - Can't connect to server error
24X (4.8G) - Works fine
25X (5.0G) - *Works (Very weird and probably game breaking things happen. I won't elaborate here, but probably need to file a bug or something).
26X (5.2G) - Crashes after login
27X (5.4G) - Crashes on loading zone

Anyway, I hope that helps.

-encopitt

Thank you. I didn't think I had any OC going on... went into BIOS and turned off my computer performance boost. Started right up!!

Cheers!

I have a question for anybody who understands why the above fix works:

Is it possible that having too LOW of a frequency would also cause issues?

Additionally, is it possible that trying to run on a CPU that's clocked with FSB would cause issues?

Seems Random
 

Not sure about OCing via FSB, but it does seem a little random to me. I reset my clock speed to 4.4 Ghz after the last patch, thinking the 60 FPS lock might have something to do with it, but still got the same results as before.
My advice is (if you're comfortable doing it) to adjust your clock speed incrementally (up and down) until you are able to get the client to connect properly.

-encopitt

I'm playing on a Ryzen 2700X at 4.1 Ghz and the game runs fine no crashes, especially after setting compatibility in WIN10. I don't think I set any Overclock on the CPU, interesting crash problem.

I just had to reset my BIOS to defaults (new ram install), and got 1017 consistently until I underclocked my proc again... This has to be a simple fix, obviously there's some check going on with the client on the server side. Stepping down multipliers on my machine (that has no problems running any other game) just to play this one, is beyond stupid.

-encopitt

EQ doesnt run over 4.0 ghz reprogram the entire client if you dont like it.

It was originally designed to run on like 255 mhz

the multiplier needs to be based on 6