Folks Can't Connect to My Server (1017)

[JasonC]

Hello, all...

Whenever someone tries connecting to my server they receive a 1017 error. I can connect to it perfectly fine myself.

I'm behind a Netgear router, and I've forwarded all the ports I'm supposed to (I think) to my box, which is 192.168.0.3.
I have the latest version of the eqemu software, and it's running the proper patch version as well. I'm using XP, and no I'm not running the Firewall.

I used the adduser command in DOS as well for the appropriate people. Didn't resolve the issue.

Any help would be greatly appreciated. Thanks!

Here's my info:

[LoginServer]
loginserver=eqlogin1.eqemu.net
loginserver2=eqlogin2.eqemu.net
loginport=5999
loginport2=5999
worldname=Ehh
locked=false
worldaddress=192.168.0.3 (as a note, when I change worldaddress to my global IP, I can no longer connect)

[WorldServer]
Defaultstatus=
Unavailzone=

[LoginConfig]
ServerMode=Standalone
ServerPort=5999
UplinkAddress=
UplinkPort=
UplinkAccount=
UplinkPassword=


@echo off
start zone . 192.168.0.3 7995 192.168.0.3
start zone . 192.168.0.3 7996 192.168.0.3
start zone . 192.168.0.3 7997 192.168.0.3
start zone . 192.168.0.3 7998 192.168.0.3
start zone . 192.168.0.3 7999 192.168.0.3
exit
cls

[tamarae]

Are the people trying to connect on your lan? (Ie: does their ip address start with 192.168?)

If the answer is no, there's your first problem. 192.168.x.x is a restricted address.. you cant receive outside traffic to it, without first traversing through the outside world ip address. You will have to set up your server to use your public IP address in the line that says worldaddress in the LoginServer.ini and in boot5zones.bat. From there, for you to be able to connect, I'd suggest reading up on NAT:

http://forums.eqemu.net/showthread.php?s=&threadid=1134
http://forums.eqemu.net/showthread.php?s=&threadid=3904

While those are in the linux forum, the same ideas will still apply to a pure windows network with a router.

If the people are on your lan (ie: their ip addresses also starts with 192.168.x.x) make sure you do have all the right ports forwarded if needed and that they also have no firewall software running. Also check to make sure that when you run the batch files to boot the server, that they return no errors at all.

[JasonC]

As I stated, when I use my global IP, not even I can connect to the server.

As far as boot5zones go, just to confirm...say 1.2.3.4 is my gobal IP, and 192.168.0.3 is my local. Which would go where in boot5zones?

I am on a LAN, however the people connecting are coming in externally. I receive no errors as far as the batch files go.

I read through those links on NAT, but I'm still somewhat at a loss for what to do. Do I need to register a domain name? I'd like to avoid a fee if possible. I downloaded the zip file that's supposed to update NAT, however after unzipping it what do I do with it?

Sorry for the newbish questions, but thanks all the same.

[astemus]

In your boot5zones.bat, you need your internet IP, which should also go in your worldserver="ip here". without that, you won't have any outside traffic. and listen to tamarae, she's got a nice server setup already :)

[JasonC]

Ok, I've changed Boot5Zones to 100% global IP as follows...

@echo off
start zone . 68.81.164.242 7995 68.81.164.242
start zone . 68.81.164.242 7996 68.81.164.242
start zone . 68.81.164.242 7997 68.81.164.242
start zone . 68.81.164.242 7998 68.81.164.242
start zone . 68.81.164.242 7999 68.81.164.242
exit
cls

...and now it's giving me an error when I run it.

WorldServer connect: Connecting to the server failed. Error: 10060

[Trumpcard]

Try this..

@echo off
start zone . 68.81.164.242 7995 127.0.0.1
start zone . 68.81.164.242 7996 127.0.0.1
start zone . 68.81.164.242 7997 127.0.0.1
start zone . 68.81.164.242 7998 127.0.0.1
start zone . 68.81.164.242 7999 127.0.0.1
exit
cls

[JasonC]

Cool! That got rid of the error at least, but I still can't connect to my server.

Just to show you where I'm at:

[LoginServer]
loginserver=eqlogin1.eqemu.net
loginserver2=eqlogin2.eqemu.net
loginport=5999
loginport2=5999
worldname=Sarizon
locked=false
worldaddress=68.81.164.2

@echo off
start zone . 68.81.164.242 7995 127.0.0.1
start zone . 68.81.164.242 7996 127.0.0.1
start zone . 68.81.164.242 7997 127.0.0.1
start zone . 68.81.164.242 7998 127.0.0.1
start zone . 68.81.164.242 7999 127.0.0.1
exit
cls

I have the following ports forwarded to 192.168.0.3:

7995-7999
5999
9000

Am I missing any? At this point I can only assume it's router related, as when I change worldserver in loginserver.ini to 192.168.0.3, I can connect.

Thanks as always.

[tamarae]

Its probably router/NAT/host file related... hence the reason I pointed out the 2 threads that I went through to get the same situation corrected for my server.

The bit about changing your windows host file to point to a dyndns type address just may help you so that you can connect from inside your lan while others connect from outside your lan.

As it stands right now can any friends join from outside? That would confirm that the server is at least running to the outside world, which was where I started. If you can get other ppl to connect from the outside, you know that your network is what's keeping you from connecting, and will have it narrowed down nicely to proceed.

As well as forwarding those tcp ports, you'll need to forward all udp ports > 1024 I believe, since everquest tends to flood those ports. (see also sony's firewall troubleshooting page under tech support on the EQ official site)

[JasonC]

I downloaded the file "eqemu-0.3.0-nat.patch.tar.gz.zip" from the first link above. Would this be worth trying? If so, how would I go about using it?

I've unzipped the file, but I'm not sure how to get it rolling.

[Trumpcard]

It won't work anymore, the code has changed to much.

Btuch posted an updated change in the linux forum, you'll need to modify your console.cpp in the world directory so the world server listens on a single interface only.

I finally got mine to work by overloading my dns name in the windows host file to my masq servers local ip (192.168.0.1)

Instructions should be in the NAT Problem Understood thread on the linux forum.

[JasonC]

Well, the deeper I dig the more confused I get. :)

At this point I'm just gonna hang it up.

Thanks a bunch for helping me along.

[mudman]

did you ever resolve this,
i am having the same problems
thanks mudman