Strictly EQEMuLoginServer.exe method

Shiny151 · #1 08-27-2009, 03:03 PM

Would someone please post their fully functional/proven (LAN & WAN) eqemu_config.xlm file (minus private data of course) so those of us who are having trouble getting WAN to work have a look?

I started a previous thread about this but I think the confusion lies where people jump in and post config files and methods for Minilogin which wouldn't necessarily apply in this case. I'm not even sure the config file is the problem but it is certainly a start since internally my server works great.

To recap, in my case and a few others; we can get LAN to play with recent eqemu server revisions and PEQ but NOT via WAN. Typically my friends will try to log in externally, they create a character and then they get disconnected from the server once they try to enter the world. Logs are not providing many clues and I've followed Vales guide stickied at the top of this forum with no luck.

And if I may restate within an Edit of this post; please be sure you're using EQEMuLoginServer.exe; Thank you!

**KLS** · #2 08-27-2009, 03:07 PM

Just fyi if you're getting to character creation then the problem is in zone server not login or world.

bergalas · #3 08-27-2009, 03:10 PM

Might want to check the wiki for the Nat/router work around fixes those seem like your best option

Shiny151 · #4 08-27-2009, 03:19 PM

Quote:

Originally Posted by KLS

Just fyi if you're getting to character creation then the problem is in zone server not login or world.

Thank you KLS; anything you can suggest that would lead me in the right direction to troubleshoot this?

bergalas · #5 08-27-2009, 03:28 PM

The nat fix should take care of it plus setting up your tcp address and the address options in eqemu_config.xml properly specificly you will need to do the natfix described in the below link and set your tcp adress in the config file to your internal ip same with localaddress ( NOT 127.0.0.1) you can rerieve your actual internal ip address on windows via start>run>cmd> ipconfig
your nat fix will only need to be done on the computer you play from once your config file is setup properly

http://www.eqemulator.net/wiki/wikka...akka=RouterFix
http://www.eqemulator.net/wiki/wikka.php?wakka=NatFix

EDIT:
You will need to do the ipconfig to retrieve the internal ip on the server as well for use in your config files and in the natfix make sure you set the ip to the internal ip of the SERVER not the local system you play on

pfyon · #6 08-27-2009, 03:31 PM

a) Check the world logs, might be the zone traffic isn't being sent quickly enough to the clients when they're outside your network causing it to timeout and kick back to server select or login (I don't remember which).

b) Check to be sure your zone ports are all forwarded properly. (I think) If they aren't, no clients outside your network will be able to connect to the zone ports.

Shiny151 · #7 08-27-2009, 03:34 PM

Quote:

Originally Posted by bergalas

The nat fix should take care of it plus setting up your tcp address and the address options in eqemu_config.xml properly specificly you will need to do the natfix described in the below link and set your tcp adress in the config file to your internal ip same with localaddress ( NOT 127.0.0.1) you can rerieve your actual internal ip address on windows via start>run>cmd> ipconfig
your nat fix will only need to be done on the computer you play from once your config file is setup properly

http://www.eqemulator.net/wiki/wikka...akka=RouterFix
http://www.eqemulator.net/wiki/wikka.php?wakka=NatFix

EDIT:
You will need to do the ipconfig to retrieve the internal ip on the server as well for use in your config files and in the natfix make sure you set the ip to the internal ip of the SERVER not the local system you play on

Thanks Berg. I have actually played around with these settings on my host file and dyndns.org etc. I'll go over this guide and have another look.

Thank you both

bergalas · #8 08-27-2009, 03:42 PM

Is kinda tricky tbh i had a hck of a time figuring out the right settings for this but this bit right here

Quote:

<address>example.dyndns.org</address>
<localaddress>192.168.1.100</localaddress>

and

Quote:

<tcp ip="192.168.1.100" port="9000" telnet="enable"/>

is what i had to mess with notice that the tcp ip in the default config file is localhost i had to change it in mine to work for both lan and wan and had to use the natfix for my local testing server

hope that helps