recv-parse: invalid login attempt from x.x.x.x

[tabitaru]

!

[fnx]

You are not the only one. I finally had a free day to do the updates to both my clients and server and am getting the same results. Even doing a vanilla install of the server does this so I am assuming that something changed in the client between the last check.

Win7 and MySQL.

[Aale]

Configure the ZoneIP for the Map Server

Now you need to determine what IP address that will be used for the Map Server, then update MySQL with it.

Most devs & enthusiasts will not have a separate map server, but will run both map server and login server on the same PC.


1. Determine what IP address will be used for the map server.

If the server will be public, then use your external IP in the next step. (Looks really random like 173.194.43.104)

If the server will be internal and you want it available on other PCs in your internal network, use the internal network IP (192.168.x.x) in the next step.

If you only plan to run the client and the server on the same PC, you can use the localhost address (127.0.0.1) in the next step.

2. Update the zone_settings table with the ip (flag) In Navicat double click on the table dspdb and expand

Click on Query

Right click and select New Query

Add the following code into the empty space, inserting the value calculated above. The value in the code below (127.0.0.1) would be used if only running the client from the same PC as the server.

UPDATE zone_settings SET zoneip = '127.0.0.1';

Select Run. You should get a message stating that many (280+) records were changed.

I recommend you save the Query in case you need to run it again later after updating the server.

Close Navicat.

Did you guys do this step? I seem to recall having the same issue when I set mine up from this reason.

Edit - Sorry, that was from the Linux install guide, posted Windows version.

[fnx]

Yes I have tried both internal server IP and external IP with proper ports forwarded. Game server responds unintelligibly, so the request/packet is making it that far. At this point I am assuming the July 3rd update changed something in packet and will just have to wait for a fix.

[tabitaru]

!

[kjLotus]

At this point I am assuming the July 3rd update changed something in packet and will just have to wait for a fix.

Not the case. I can log in fine to my server. That error is if the following sql query fails (or returns 0 rows): "SELECT charid FROM accounts_sessions WHERE inet_ntoa(client_addr) = '%s' LIMIT 1;".

You might want to double check that row is being populated (by the connect server) and if it isn't, why it isn't

[tabitaru]

!

[tabitaru]

!

[kjLotus]

Sounds more like your db is acting up than the server.

I don't know whether it's right or not that your old install doesn't have it, but it really doesn't matter since an old install isn't going to work anyways

[tabitaru]

!