Server not 'serving' properly

[nyquist]

Just updated database and recompiled with latest code, fresh from the SVN. With that said, eq2world starts up fine, aside from:
[Error] LoginServer::ConnectToUpdateServer: Connect info incomplete, cannot connect.



After that, everything goes smooth, I created a new character, added him but the client stopped on "connecting to zone server," after which it returns to the login screen (i.e. prompts me for Login info). The server output shows "[Status] AddAuth: XXXX Key: YYYYYYYYYY" and nothing after that.


Any clue on what I'm missing? Any more info I need to provide?

[ZexisStryfe]

Can you please post the contents of your loginserver.ini file (minus your username and password)?

[nyquist]

Here ya go:

Code: Select all

[LoginServer]
loginserver=eq2emulator.net
loginport=9100
worldname=Retribution
worldaddress=128.61.59.100
#internalworldaddress=10.0.2.15 (tried this as well since that is the VM's internal IP address)
worldport=9000
locked=false
account=XXXX
password=XXXX
#autotableupdates retrieves the latest table updates and applies them to your database
#autotableupdates valid options=always, ask, and never
autotableupdates=never
#autotableverbose displays detailed information about the updates; options=true or false
autotableverbose=false
#autotabledata retrieves the latest data for tables like the opcodes table; options=true or false
autotabledata=true

[WorldServer]
Defaultstatus=
Unavailzone=

[UpdateServer]
updateserveraddress=eq2emulator.net
updateserverport=9101

[LoginConfig]
ServerMode=StandAlone
ServerPort=9100

[ZexisStryfe]

well, I believe your updateserverport should = 9103.

also you have autotableupdates=never which means you won't get any DB table structure updates. I would switch that to always.

[John Adams]

We really need to get that loginserver.ini changed. The URL is updates.eq2emulator.net, too.

[nyquist]

you have autotableupdates=never which means you won't get any DB table structure updates. I would switch that to always.

Yeah before getting to this point I had it updating my tables, which then caused eq2world to throw an error because my lua_script field was changed to zone_script :/

also will these changes affect my client to server connection? I'll try them in a bit when I get home

[John Adams]

Actually, zone_script was change to lua_script quite a while ago. That was to make the similar fields uniform throughout the DB.

[nyquist]

consistency is usually a good thing


but I just tried those changes and still getting stuck at the same point...server is still running fine, client hangs for a bit at the same place then boots me back to login screen

[John Adams]

So you got this section right?

Code: Select all

[UpdateServer]
updateserveraddress=updates.eq2emulator.net
updateserverport=9103

and turned on the autotable updates?

Code: Select all

autotableupdates=always

And... (dumb question time) you have forwarded port 9000 through your firewall/router to point to your World server's IP address (TCP/UDP)?

[Zcoretri]

Another dumb question...are you using Windows 7?

[nyquist]

So you got this section right?

Code: Select all

[UpdateServer]
updateserveraddress=updates.eq2emulator.net
updateserverport=9103

and turned on the autotable updates?

Code: Select all

autotableupdates=always

And... (dumb question time) you have forwarded port 9000 through your firewall/router to point to your World server's IP address (TCP/UDP)?

yup yup firewall:

Code: Select all

To                         Action  From
--                         ------  ----
80                         ALLOW   Anywhere
22                         ALLOW   Anywhere
9100                       ALLOW   Anywhere
9103                       ALLOW   Anywhere
9000                       ALLOW   Anywhere
3306                       ALLOW   Anywhere

and changed the update address as well as port and autotableupdates

Another dumb question...are you using Windows 7?

Kind of...passing all of the pertinent, previously listed ports to my Ubuntu VM, but Windows 7 is my host

[Zcoretri]

Turn off your Windows 7 firewall and see if things start working.

[nyquist]

No change upon disabling firewall (windows firewall was disabled to begin with, but I disabled my 3rd party one as well)

and just fyi, "[Error] LoginServer::ConnectToUpdateServer: Connect info incomplete, cannot connect." is still showing up on server start