Got 1017? Then let's fix it!

[Magick]

What are the real causes of 1017 errors?


It seems to me from scanning the various forum posts and reading any and all information I can about setting up EQEmu and about the various woes of other people trying to setup servers that quite a few are encountering 1017 errors - many of them unable to do anything to correct the issues.

The 1017 problem was blamed, usually, on the current client version and it's incompatibility with EQEmu. Now, a patcher was put out (great program btw) that "should" patch the client to one that does work, and, it has apparently fixed the problem for quite a number of people. But I ponder... why hasn't it fixed it for the others?

If you have a client version proven to work on some systems, and you clone that to another system, What are any/all reasons that it would not fuction properly? (I'm asking for a list here)

1. Obviously the server you are trying to connect to could be incorrectly setup. But, if you are trying to connect to a server with 30+ people on it already, this one wouldn't apply to you.

2. I don't know.. I'm out of guesses seeing as the client (eqgame.exe) should be compatible.


Checking out EQ's own site with more detailed information on 1017's we find:

This error can be confusing because it has to do more with connectivity to the world servers rather then the patch server. Included below are ways to troubleshoot this problem based on your connection type, whether you dial up to connect or you use some type of broadband connection (Cable, DSL). Of course, if the tips below do not help then you will want to also refer to our Network/Connection Support page for additional information on connectivity problems.

If you connect to the Internet using a dial-up modem then you will first want to check to see if you have a network card installed on your computer along with the modem. If you do have a network card installed as well as the modem then you will want to disable it. Most often network cards will have a default subnet mask of 255.0.0.0, which would cause your computer to search itself internally for the EverQuest servers. Since the EverQuest servers are not located on your computer it will never find them, and you will get the 1017 error listed above. If you do not have a network card installed along with the modem then you will want to make sure you have the proper subnet mask. To check this you will want to click on the Start button at your desktop. In the start menu, click on run, and type in 'winipcfg' in the "Open" line. The IP configuration window should pop up and you will be able to check your subnet mask there. If it is set to 255.0.0.0, then you will want to release and renew your IP address until you get a subnet mask that is something other then 255.0.0.0. Ideally you will want to have 255.255.255.0. If you are unable to get a different subnet mask after releasing and renewing then you will need to contact your Internet Service Provider for further assistance.

The same mainly applies to broadband connections as well. Most troubles with the 1017 error come from improper subnet masks. You will want to be careful of multiple network cards in a single machine. Even though one may be set up properly to connect to EverQuest, the other could be defaulting the subnet mask to 255.0.0.0. You will be able to check your subnet mask the same as listed above.

If you are running a firewall or proxy server and are receiving the 1017 error, then please visit our Network/Connection support page to find all the settings to configure your Firewall to be able to connect to EverQuest.


Okay, absorbing that information makes one wonder if part of the problem some are experiencing has to do with network settings. But, if you can connect to EQ Live but cannot connect to EQEmu... then where is the problem? Is it a fair assumption that if it works with Live there should not be a problem with the Emu?

I have spent literally hours reading post after post, exploring various "1017 - Help me!" posts for answers to why it happens to some but not others. Sure, sometimes they just have things setup incorrectly and naturally I don't spend much time when I see that is the problem. But, what about the others who post the problem, the logs with no sign of trouble, and yet nobody can ever give them an answer. It seems the problem gets bigger as the emulator becomes more popular yet I have never seen a true trouble shooting guide to solving it (or at least attempting to).

Myself... I have been cursed by 1017 for quite a few versions. As a matter of fact, I think I first played with EQEmu months ago and got the same error. At that point I shrugged it off to a buggy emulator and figured the kinks would be ironed out down the road. Now, the emulator is looking pretty polished. Sure, still some kinks but considering many people are playing on emulated servers and hosting their own, it's stable to the point that I can't blame a 1017 on the server - at least not entirely.

In my own case, EVERYTHING loads up perfectly... World.exe has no errors... The Zones have no errors... everything is connected and ready (using the login1.eqemu.net). Yet, if I try to log in to myself - 1017!!

If I run minilogin, same thing: Everything boots perfectly. I select my server, I get about 2 seconds on black (anticipating the character select screen) and boom... kicked back with a 1017. My logs show a connection made, and then my client disconnecting. But why?

Going back to network connections, I have done, literally, every sequence from going COMPLETELY local (localhost, 127.0.0.1) to using my actual IP, to even having a domain name assigned to my IP and using that in every combination possible to try to get it to work. The previous was using both local and the EQEmu login methods. The IP or Network ajustments don't appear to be the issue. Ok.. so can I host a server on my ISP? Maybe that's the problem. Sure... I can and have done both ftp and http servers without a problem. But even if I couldn't -- what would stop me from connecting to someone else's server (with people already playing on it)? I try with no Firewall program, no XP networking firewall activated, No AV program running, "world adduser..." done (when trying to serve), and I'm not on a router. /shrug


I don't have the answers, nor did I post figuring I'd see a magical answer appear. Instead, I'd appreciate it if my questions could be replied to by anyone who KNOWS the answer(s) to them. I don't mean "how do I fix", I mean questions like:

If you have a client version proven to work on some systems, and you clone that to another system, What are any/all reasons that it would not fuction properly? (I'm asking for a list here)


Also, anyone who HAS had a 1017 issue in the past, but managed to correct it, could you please recap what your problem was and what you did to correct it? I'd like to make a troubleshooting guide if we get enough information, but unfortunately, many have either not been able to fix (it seems), or they post the problem and later a "nm.. it works now" without any clues to how they got it working (those would be handy for those who post in the future).


Input is welcome and encouraged. Thanks in advance.

[Sabryn]

OS: Win98
Current Emu Ver. 4.3
Last Patch 01/06/2003

This has always been the way to correct the 1017's for me. Like you, I get them with every patch release. However, I only get them when I patch from EQLive & EQEmu. Both at once <~~ Take note of that.

The problem, as far as I can tell, is normally based in the 'eqhost.txt' file.

Most of the 'Readme.txt' releases in the past year have always given the same example of "Cut and Paste this into your 'EQHost.txt' file . . . but that never worked for me. Ever. I had to get in there and tinker with it.

Now, this is theory here, not fact . . . I believe that EQ has a built in way of detecting whether there is something wrong with the 'eqhost.txt' or not. I believe the software checks for how many lines long the document is, and the exact size, or more to the point, a mix of both I haven't been able to pinpoint.

Example time !!

This is my current configuration:
----------------------------------------------------------
[Registration Servers]
{
"localhost:5999"
"localhost:5999"
}
[Login Servers]
{
"localhost:5999"
"localhost:5999"
"localhost:5999"
"localhost:5999"
}
----------------------------------------------------------

See, now, that looks like a bit of overkill, right? It works, sure. But why not just use:

----------------------------------------------------------
[Registration Servers]
{
"localhost:5999"
}
[Login Servers]
{
"localhost:5999"
}
----------------------------------------------------------

BANG !! 1017 !! Why? No clue. . . . now, one more:

----------------------------------------------------------
[Registration Servers]
{
"localhost:5999"
;
;
;
;
;
}
[Login Servers]
{
"localhost:5999"
;
;
;
;
}
----------------------------------------------------------

Working fine. No 1017. That is perfectly functional. I have no idea why, because it makes no sense. But, oh well.

These examples work fine on my system. You can test them out yourself and see if you come up with the same results.

One aspect of this (and a lot of other similar problems) that has never fully been explored is whether the system of theoretical checks and balances by the software is expansion-specific. IE: Basic EQ doesn't have it, but EQ:SoL does. That would explain the random occurance of the 'Notorious 1017'. But it could also be simply the OS. Win95, Win95 OSR2, Win98, Win2k, Win2kProf, WinXP, . . . all of these have a moderately different way of handling networking. From the top it all looks pretty much the same (Big words, cryptic anagrams, bad math) but there's a lot of differences in there.

Now, the mind boggling part . . . there's a good chance we're dealing with a combination of OS-Based networking flukes & EQExpansion-Based checks and balances . . . which leaves, roughly, 12,000 possible combination configurations, not including Windows Program Setup configuration for different networking software/drivers (which would push it well over 500,000 probably) then tossing in Firewall software, AOL-specialty TCP/IP drivers, etc, etc, . . . there's no point in even bothering thinking about it . . . Especially when chances are there is 1 single thing all these cases have in common.

Now, back to Earth, in conclusion, from my year of research into the 1017, I'd tell everyone who followed the readme exactly and is still pulling a 1017, to tinker with their 'EQHost.txt' file. Not the addresses or anything, just the length, number of lines, etc. Patch your EQLive (after backing up your files) and compare VI's 'eqhost.txt' with the one you're currently using. Try to make them as similar as possible. Trimming here, fluffing there, never actually changing addresses, just the number of them. This will normally fix it for you. Well, theoretically anyway.

[nekero]

I fixed mine by sourcing new database,then typing
insert into account set name='yourname', password=
'yourpassword', status=200;.I have to type this in msql
everytime i use a new database or i get 1017 error.Works
everytime for me now.

[Memener]

you know the real way to get ride of the 1017 error go under MSDOS an type format C:
or fdisk

[Memener]

oh one more thing Sabryn you have no idea what your talking about... if your running a EQemu server with Minilogin.exe all on one computer dont use localhost use this IP 127.0.0.1 it is also in the read me file

[Magick]

Sabryn,

I'm curious, about several things:

1. Are you able to play on another Emu server using the standard eqhost.txt (ie., eqlogin1.eqemu.net)? If not, does it work if you alter it like you do for your local server?

2. When you alter your eqhost.txt, are you doing it to the exact byte? Sony's is 215 bytes, and me being willing to try anything, I played with it to see what I could do. The best I could tweak it to was 214 bytes or 217 bytes and as you put it "BANG!! 1017!". I'll swap some info around (like using my domain address or IP instead of 127.0.0.1 and see if it makes a difference).

3. As Memenerr noted, the readme states you should be using 127.0.0.1 as opposed to "localhost". What happens if you use 127.0.0.1 instead? Another visit from the Ghost of 1017's past?

Your solution, certainly unique, will probably make some scratch their heads but if it's working for you FANTASTIC! And definately, it's worth exploring more (hence the questions) since there might just be more to eqhost.txt than meets the eye.


---------------------------------------------------------

nekero,

Yes, that's a solution alot of people miss when setting up a local server - very good point!

I do that each time as well and while it may solve some issues for those hosting locally, it wouldn't affect those who get a 1017 when both trying to locally host - or - trying to connect to someone else's server (ie., Foreverhacking).

Unrelated but.... Anyone know if the eqemu:eqemu login/pass always coded into the database? It works on mine locally (at least to get to server select), yet it never shows up as an account when viewing the database (using Admin Tools)? This is a clean db so I know I never added it.

[diOxy]

I have the same error, 1017...

World.exe display thats :

Unknown opcode: 0x0286 size:196
   0: xx xx xx xx xx xx xx 00 - xx xx xx xx xx 00 00 00  | myname_.passwd...
  16: 00 00 00 00 33 B6 4A 78 - 43 00 00 C0 00 00 00 00  | ....3.JxC.......
  32: 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  | ................
  48: 00 00 00 00 3E 00 00 00 - 00 FD 12 00 7E 00 80 00  | ....>.......~...
  64: 00 EC FD 7F D0 21 13 00 - C3 2D 46 78 B0 FB 12 00  | .....!...-Fx....
  80: 80 E3 EC 77 00 00 00 00 - 88 FB 12 00 C8 F3 EC 77  | ...w...........w
  96: 38 F9 12 00 00 EC FD 7F - 02 00 00 00 00 00 13 00  | 8...............
 112: 45 00 00 00 00 00 0A 00 - 7C 96 46 78 7E 00 00 00  | E.......|.Fx~...
 128: 01 00 00 00 00 00 00 00 - 33 B6 4A 78 A8 FB 12 00  | ........3.Jx....
 144: 43 00 00 C0 25 84 46 78 - 43 00 00 C0 28 FC 12 00  | C...%.FxC...(...
 160: F1 6A E7 77 20 00 00 00 - 33 B6 4A 78 2F A4 E7 77  | .j.w ...3.Jx/..w
 176: 43 00 00 C0 FC FD 12 00 - FC FD 00 00 00 00 00 00  | C...............
 192: C2 00 00 00                                        | ....
Unknown opcode: 0x0286 size:196

___
Win2k Pro
On localhost
All is correct
But i get always the 1017 Error.
And its not possible for me to use EqEmu Patcher. :'(
Im behind a proxy and i need to modify some paramters.

[Sabryn]

Originally Posted by Memenerr

oh one more thing Sabryn you have no idea what your talking about... if your running a EQemu server with Minilogin.exe all on one computer dont use localhost use this IP 127.0.0.1 it is also in the read me file

I don't argue or mudsling in public. But I stand by what I said as being right. Look at the date I joined this forum as compared to your January 16, 2003 date for authority reference.

[Sabryn]

Originally Posted by Memenerr

you know the real way to get ride of the 1017 error go under MSDOS an type format C:
or fdisk

You seriously don't need to be dwelling around on support forums. You may find that funny in some 'meet me at the monkey bars at 3:00' sort of way, but it's not. Not everyone here has a outstanding knowledge of stuff like this and it could mess up their system pretty bad. Please, don't say stuff like that.

[Sabryn]

Originally Posted by Magick

Sabryn,

I'm curious, about several things:

1. Are you able to play on another Emu server using the standard eqhost.txt (ie., eqlogin1.eqemu.net)? If not, does it work if you alter it like you do for your local server?

Wow, that's a good question. I haven't touched a public Emu server in over 8 months . . . but, I think (not sure) that the basic 'eqhost.txt' recommended out of the 'readme.txt' at the time worked fine. I remember using the 'eqlogin1.eqemu.net' 'eqhost.txt' as a reference for forming my personal 'eqhost.txt' for my MiniLogin.

Originally Posted by Magick

2. When you alter your eqhost.txt, are you doing it to the exact byte? Sony's is 215 bytes, and me being willing to try anything, I played with it to see what I could do. The best I could tweak it to was 214 bytes or 217 bytes and as you put it "BANG!! 1017!". I'll swap some info around (like using my domain address or IP instead of 127.0.0.1 and see if it makes a difference).

What I would recommend is . . . following the EXACT layout of Sony's 'eqhost.txt'. As in, if 4 '[login servers]' are listed, use 4 of your own. Use the same ones 4 times in a row if need be. Exact byte may, or may not, affect it. But I know for sure what I just mentioned above always affects the 1017 on my system. Once again, all systems are different, though. But I would try matching the amount of lines and entries before digging as deep as exact byte size. Side note, '127.0.0.1:5999' is more stable than 'localhost:5999' in most cases. Localhost works on mine, but most people have issues with it. . . . just thought I'd throw that in.

Originally Posted by Magick

3. As Memenerr noted, the readme states you should be using 127.0.0.1 as opposed to "localhost". What happens if you use 127.0.0.1 instead? Another visit from the Ghost of 1017's past?

Well, I want to point out first off the Memenerr also said the best way to fix the problem is to format or repartitian your hard drive.

More to the point, the 'readme.txt' is setup to help beginners get their systems up and running with minimal problems on a wide variety of platforms. Like all readme's, they are made to be extremely simple and generalized. The readme isn't going to say how/when/why '127.0.01' and 'localhost' can be interchanged, because it's not immediately related to the task of just getting the Emu going except where noted.

To answer your question, '127.0.0.1' causes a 1017 on my system when I fill in, say, all 4 of the [login servers] with it. But once again, interchanged, it works fine. LOL. Here's an example of what I mean:
----------------------------------------------------------------------------
[Registration Servers]
{
"localhost:5999"
}
[Login Servers]
{
"localhost:15900"
"127.0.0.1:15901"
"localhost:15902"
"127.0.0.1:15903"
}
-------------------------------------------------------------------------------

That works fine. As long as 'localhost' is mentioned somewhere in there, it knows where to go. I could fill in the bottom 3 'Login Servers' with Sony's own addresses, and it still works. To the best of my experience and knowledge, they are nothing more than space fillers when it comes to running the Server/Client on the same box. Connecting to Gotfrags (Do they still use gotfrags?) or whatever EQ Emu's current public server is, is a completely different story.

Originally Posted by Magick

Your solution, certainly unique, will probably make some scratch their heads but if it's working for you FANTASTIC! And definately, it's worth exploring more (hence the questions) since there might just be more to eqhost.txt than meets the eye.

Well, I made it more complex than it really is. Most of that was simply theory. I know, factually, the amount of lines in the EQ Host (as mentioned above) directly effects the 1017 for boxes running the server and client simultaniously. I forgot to mention there might be something in the 'MiniLogin.exe' itself that's causing part of the issue. I haven't broken it down and checked yet, though.

[Magick]

diOxy....

It seems the opcode errors have usually come from an incompatible version of the eqgame.exe client. If you haven't, download the patcher from here, run it, and see if you still get the same problem. That client version "should" work and end your error - at least that one.

EDIT: Sorry, just caught the proxy server. Well, if you can't run the patcher you'd likely need to hope you have a friend who can patch a version of the client and send you a copy. I think that still falls under pirating legalities so I wouldn't ask anyone to post a link In any case, I would point my finger at the wrong eqgame.exe and say that is your primary problem.

[Magick]

Well, I want to point out first off the Memenerr also said the best way to fix the problem is to format or repartitian your hard drive.

Point taken It surprises me how many Tech Support people from Gateway generously post well thought out tips on this board.

Thanks again for the post Sabryn! I'll play with it somemore and see if I can get it to do anything.

[houdini]

the answer is probley here allready but as i am blind and cant read... i will have to ask.....

my server comes up just fine but i am getting 1 error

[Status] CURRENT_WORLD_VERSION:EQEMu 0.4.4-DR1
[Error] CURRENT_WORLD_VERSION:EQEMu 0.4.4-DR1

zone.bat comes up ok... and when run eq (on a different system) i get to the server scelect menu and find my server there waiting for me.....but when i try to logon to it 1017
this only happens when i try ot get into my server from a system that is NOT RUNNING EQEMU.... i can logon to other servers from this system no prob...i can logon to my server if i run eq on the same system as i am running emu......

i am useing a linksys router with ports 9000, 2000-3000, 7994-8000 fowarded to the local ip of the eqemu sys192.168.1.x and the dmz host is on for this system...... any ideas......not including large ammounts of high explosive...grin thanks in advance

ps..... i am useing the name for my system "xxxx.xxx.xx.xxx" rather than the numbers as i do not have a static internet ip and this name stays the same even when the ip changes....... could this be causing the problem and if so will a redirect service help/work??

[hedeon]

I have a similar problem. I can login fine on other listed servers, but when I try to login on my own server I get the infamous 1017 error.

My router is already setup to forward all ports to the computer which is running the server. (Alcatel, using the command 'defserver'
(yes, I am lazy maybe) I also tried to bind all ports manually (TCP 7995-7999 and 9000), no luck either).

Neither zone.exe or world.exe give any errors except for the version (see above post). And no apparent errors in the .ini files.
Yes, and I use the patcher.

Haven't tried minilogin yet. It used to work with version 0.3 though...

Any help appreciated. I can give more info if asked.

Regards,

Hedeon.

[Memener]

Memenerr wrote:
oh one more thing Sabryn you have no idea what your talking about... if your running a EQemu server with Minilogin.exe all on one computer dont use localhost use this IP 127.0.0.1 it is also in the read me file


I don't argue or mudsling in public. But I stand by what I said as being right. Look at the date I joined this forum as compared to your January 16, 2003 date for authority reference.
_________________
~*~*~ Sabryn the Everlost ~*~*~

"OMG WTF WTF WTF WTF U aEr KS !!!!1?//
I aEr snAreD iT i wUz ownLy hAf a ZoNe aWay !!!!111///"

Lol i know this is an old post BUT i think it is funny he said i joined January 16, 2003 which is very ture but the thing i think is funny is that he join feb 2002 and still dosent know what is talking about

also my frist post to this is ture if your here try to set up a sever with mysql and sourcing stuff in a dos like window now i think if you want to do this your should know alittle about dos #1 (LOL) you CAN NOT format your HD in WINDOWS (DUH) #2 you can not use Fdisk unless you know how to use and it dose SAVE under windows i dont everthing it works LOL so if your still out there Sabryn i go by what i said YOU dont know what your talking