EQEmulator Forums - Possible Login Server Issue

EQEmulator Forums (https://www.eqemulator.org/forums/index.php)

- Support::Windows Servers (https://www.eqemulator.org/forums/forumdisplay.php?f=587)

- - Possible Login Server Issue (https://www.eqemulator.org/forums/showthread.php?t=32733)

Well I might jinxed it. We just had a reboot and the server keep reconnecting to eqemu LS (same issue as before). Our private LS is fine.

anyways, Happy New Year :)

On EZ server, seems this issue is back.

So is anything being done about this? Just wanted to know if i should just switch over to the other login server.

Yeah, this issue is still going on for Storm Haven as well. As long as I keep EQEmu as the only LS we are configured for, it stays connected most of the time without as many disconnects. As soon as I configure the other LS's, it starts dropping off of EQEmu very quickly and stops reconnecting to it at all eventually.

Very odd issue indeed. Hopefully I can find some time to help troubleshoot the issue more from my side (as much as is possible anyway).

I just noticed that the LS for peqtgc.net and tsahosting.net both resolve to the same IP address. I am not sure if one of those 2 took over for the other, or if they are both trying to be ran from the same host. My server had been configured to connect to both, but doesn't seem to actually connect if I use my tsahosting login info for my server, but I think it did connect to it last time using no login info (which is what I used for the peqtgc.net LS). So, I assume the tsahosting.net login server is now actually the peqtgc.net login server. I wonder if servers trying to use both (like mine was) is what is causing all of the weird reconnect issues.

Gaeorn or Cavedude, can one of you confirm which LS is running at your host now?

Code:

C:\Users\Trevius>nslookup eqemulator.net

Server:  DD-WRT

Address:  192.168.1.1



Non-authoritative answer:

Name:    eqemulator.net

Address:  67.23.190.71





C:\Users\Trevius>nslookup peqtgc.net

Server:  DD-WRT

Address:  192.168.1.1



Non-authoritative answer:

Name:    peqtgc.net

Address:  72.67.6.37





C:\Users\Trevius>nslookup tsahosting.net

Server:  DD-WRT

Address:  192.168.1.1



Non-authoritative answer:

Name:    tsahosting.net

Address:  72.67.6.37

I am pretty sure we should only be set to use one of those, but not both, as I don't think both can run on the same host and use the same port. Once we know for sure which to use, maybe if all servers correct their config, it will resolve the problem seen on the EQEmu LS as well?

Nevermind, it looks like the PEQ LS is actually login.peqtgc.net, which resolves to a different IP.

Code:

C:\Users\Trevius>nslookup login.peqtgc.net

Server:  DD-WRT

Address:  192.168.1.1



Non-authoritative answer:

Name:    peq.peqtgc.net

Address:  67.23.190.82

Aliases:  login.peqtgc.net

So, I am not sure if it is related after-all (probably not), other than maybe some servers aren't using the login.peqtgc.net address.

This is now fully resolved as of about an hour ago.

The issue was in our Toplayer appliance that was implemented on 12/19, due to a rule automatically in place for port 5998 typically used for the Borland service. The rule blocked certain packets due to a buffer overflow vulnerability that would have crashed that specific software. Since we do not run Borland, this rule was disabled.

Quote:

Description EXPLT: Borland InterBase Remote Buffer Overflow Exploit
This rule is triggered when an exploit of the Borland InterBase database service (ibserver.exe) in Borland InterBase 2007 before SP2 is detected. The exploit allows remote attackers to execute arbitrary code via a long size value in a create request to port 3050/tcp

Thank you very very much for everyone who contributed to resolving this issue. Very awesome work.