Kickback on attempt to Connect

[KLS]

Can you post your config with the sensitive information redacted?

[Akkadius]

Done with this.

[KLS]

Okay well it probably has to do with a difference in how the svn server handles local lan addresses. I think trev has been connecting via his lan and maybe can add on how to successfully connect behind one atm. I'll look into what needs to change loginserver side to get similar out of the box functionality with it to the old one.

[Akkadius]

Thank you Kimmy, I don't need to get on soon because I will be busy in RL for a week or so, but whenever we can get that all squared that'd be awesome.

Thank you again 8 D

[trevius]

If you have the GM IP restriction setup and are using the gm_ips table, there seems to have been a change in what IP the LS sends you to your server as if you are playing from the same LAN. It used to come in as my PC's LAN address of 192.168.1.101, but now it comes in as my router/gateway LAN address of 192.168.1.1.

An easy way to verify what IP you are being seen as now is to check the EQEmu web tool and lookup your GM account there in the database / account lookup. If you are running the latest web tool updates, it will now show your connecting IP information even if you don't get all of the way in. That is how I found that mine had changed. You could also just look in your accounts_ip table and check your connecting IPs that way.

I ran into a problem last night that was crashing my client while connecting due to whatever change on the LS that changed the IP that is sent to the server. Took me a few minutes to figure out, but once I added my gateway address to my gm_ips table, it started working just fine.

Hope this helps.

[501st]

Hey

I'm having the same issue. Basically whats happening is the server connects to the LS fine and shows up on the server list without problems. I click my server and click play and the screen turns to black for about 1-1 and a half minutes then boots me back to login. At first there is no error message but if you type your password in again and return to server select then an error pops up saying "Error 1017: Cannot login to the Everquest server. You may need to rerun the update patch. Repeatedly seeing this message indicates a loss of connectivity to the Patch Server. This is usually temporary." From here if i click "ok" i can select another server and i can login and play fine, just not my own.

Basically what you're saying Trev is that the new LS changes causes some sort of IP changing error when logging into you server from the same box the server is running on? Well i think i followed your directions correctly. I got a hold of my gateway IP and plugged it into the gm_ips table in the database. The table was originally completely empty. I plugged in the name, account id and then my gateway ip and tried again but nothing changed.

I should probably also note that world.exe doesn't change at all through the login process, it no longer says the usual "received connection from IP blah blah blah" as it usually does and instead just sits silent, as if it's not even receiving a connection. Don't know if that means anything or not.. lol

[trevius]

By default, the rules for GM IP Restricting is disabled, so if you haven't enabled that yourself in your rules, then it isn't the problem. Here are the 2 related rules:

World:MinGMAntiHackStatus
World:GMAccountIPList

Unless you enabled those 2, then the IP problem I had is not the same problem you are having.

Some things you can try are:

1. Check your EQ dbg.txt file located in your Everquest /logs folder. See if the logs near the bottom are of any help, and maybe post the contents of that file (maybe in a new thread).

2. Check your account_ip table and see what IP(s) are showing as connecting from your GM account.

3. Check the FAQ in my sig to see if it helps with anything. I think you would specifically want to check the parts related to port range forwarding. You may need to make sure that you are not forwarding port 5998, as that may cause some issues.

4. Have you ever been able to connect to your own server fully? If not, then you probably have some other issue. Check your server log files (probably the world ones) to see if you are getting any errors. If you have connected to your own server, exactly when did you start having this new problem, and did you change anything on your end before it started?

5. You may also want to check your hosts file that I think should be in your windows/system32/drivers/etc/ folder. Make sure you don't have any custom host settings in there.

Normally, the problem you are describing occurs when there is a port range forwarding issue, so it is probably most important that you make sure you have that setup correctly.