NAT Troubleshooting in 0.4.2

Vaft · #1 02-17-2003, 02:22 PM

I have three computers on my local network. One computer runs the 0.4.2 server, the other two computers run everquest. All three computers are behind a linksys RP614 router... The internal IP address of the server machine is 192.168.0.100, The router is configured to forward ports 7995-7999 and port 9000 to 192.168.0.100...

I am using dyndns service to set my external IP address to mospeda.ath.cx, and then I have edited the hosts file on the LAN machines to set mospeda.ath.cx to 192.168.0.100..

Both of the local machines are able to connect to the server machine, create characters, and play everquest fine. However, all external everquest clients are booted as soon as they get to the character select screen.

The log of a failed connection looks like this:

---------------------------------------
Logged in: LS#3899: (Account Name)
Guild send Request...
Sending character information.
Client disconnected.
---------------------------------------

This is what my config files look like:

Loginserver.ini:

[LoginServer]
loginserver=eqlogin1.eqemu.net
loginserver2=eqlogin2.eqemu.net
loginport=5999
loginport2=5999
worldname=Mospeda EverQuest
locked=false
worldaddress=mospeda.ath.cx

[WorldServer]
Defaultstatus=
Unavailzone=

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

----------

Boot5zones.bat:

start zone . mospeda.ath.cx 7995 localhost
start zone . mospeda.ath.cx 7996 localhost
start zone . mospeda.ath.cx 7997 localhost
start zone . mospeda.ath.cx 7998 localhost
start zone . mospeda.ath.cx 7999 localhost
exit
cls
----------

Not sure what to do. It seems like I've followed all the directions to a tee. As a side note, I am able to run other servers fine behind the router - I typically run FTP and HTTP servers with no problems. Also, the WinXP firewall features are disabled. Any ideas here?

Lurker_005 · #2 02-17-2003, 03:15 PM

There was a problem with running 4.1 servers if there wasn't enough bandwidth. I'm not sure if that was addressed in 4.2 or not.

It was said you needed to have at least 256Kbs up and down to allow people on the internet to connect or they got dropped. Most broadband users only have about 128Kbs upload

Vaft · #3 02-17-2003, 08:49 PM

Not sure if that is my problem or not, considering they get disconnected before they can even pick a character. It seems to be happening within the worldserver, which shouldn't require much bandwidth, right? If nothing obvious pops out to anyone, maybe I will have to sniff some packets and see what the very last data sent/recieved was?