SoD connection issue on private server

[Baruuk]

Okay - I have to either be missing it or I have to be a retard - or both. I'm willing to accept the latter. My Titanium client connects perfectly to my server and has for some time when my files are configured with port 5998. However, after modifying my eqemulogin.ini and replacing 5998 with 5999, changing the eqemulogin.ini 'loginserver' value to 5999 and even my 'listen_port' value in login.ini (not sure if it's necessary) to 5999 - I can't connect.

So I load up my SoD client which I use with PEQ, EZ, etc and and change my eqhost.txt file to my IP:5999 and no go. My server is at my private office with a static IP - no issues there in the past. I can make Titanium work but not SoD.
I should also mention that the client just HANGS on "Logging in to the server. Please wait..." What's interesting is that I can see my client attempt to connect on the server's console - it says 'New Client UDP Connection from <IP Address>:1948. I also have port 5999 open in the firewall (otherwise the former wouldn't happen I'd assume).

Any suggestions?

Thanks in advance.

[Burningsoul]

I'm also having this issue, I'm going to dig a little deeper and post back if I find a solution.

[Rykeau]

I'm guessing you meant eqemu_config.xml in one of your comments but if you didn't modify that you'll need to...

<loginserver>
<host>your server name</host>
<port>5999</port>
<account></account>
<password></password>

See if that helps.

[Capheus]

In your eqemulogin.ini you have to cahnge the login opcodes.

Titanium
OPCodePathAndFileName=login_opcodes.conf

SoD
OPCodePathAndFileName=login_opcodes.sod.conf

I use port 5999 for both Titanium and SoD, you might wanna give that a try too.

[Baruuk]

That helped thank you - I changed my eqemulogin.ini to reflect the code below - however I guess I was a little confused on two things. First - if my eqemulogin.ini should look differently, considering now it'd probably only allow SoD clients to connect (if I'm missing lines) and second, what is the difference between login.ini and eqemulogin.ini. Here are both:

EQEMULOGIN.INI
Port=5999
DumpPacketsIn=true
DumpPacketsOut=true
Trace=true
DatabaseServerName=localhost
DatabaseCatalogName=PEQLoginDB
DatabaseUserName=<mylogingoeshere>
DatabaseUserPassword=<mypasswordgoeshere>
OPCodePathAndFileName=login_opcodes_sod.conf

LOGIN.INI

[database]
host = localhost
port = 3306
db = peq
user = <myusernamegoeshere>
password = <mypasswordgoeshere>
subsystem = MySQL

[options]
unregistered_allowed = TRUE
reject_duplicate_servers = FALSE
trace = TRUE
world_trace = FALSE
dump_packets_in = FALSE
dump_packets_out = FALSE
listen_port = 5999
local_network = localhost

[security]
plugin = EQEmuAuthCrypto
mode = 5

[Titanium]
port = 5998
opcodes = login_opcodes.conf

[SoD]
port = 5999
opcodes = login_opcodes_sod.conf

[schema]
account_table = tblLoginServerAccounts
world_registration_table = tblWorldServerRegistration
world_admin_registration_table = tblServerAdminRegistration
world_server_type_table = tblServerListType

[Capheus]

Not sure what the login.ini is for. I'm currently not using it. To the best of my knowledge it isn't used and when I tried to use it in login.ini or embedded in eqemulogin.ini it didn't work. It's in the SVN so it might be something in testing? Someone else would know more.

[Baruuk]

Thank you Capheus. Does your eqemulogin.ini look like mine or is there something special you have to do to support both Titanium and SOD clients?

[Capheus]

Looks just like yours does. If just add and remove the "sod" part for the opcodes.