Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 52200 when connecting, disconnecting, then trying to connect again. #30

Open
AdmiralCurtiss opened this issue May 30, 2014 · 11 comments
Labels

Comments

@AdmiralCurtiss
Copy link
Collaborator

Might as well make this official. This is a big error and we're all quite puzzled what actually causes it. It has to be either in conntest, nas, profile or qr -- most likely either nas or profile.

@ghost
Copy link

ghost commented Oct 11, 2014

I encountered this bug too, i have to reset sometines my NDS

@ghost
Copy link

ghost commented Oct 12, 2014

it only happens on ds games not on wii which strange but bad for ds games but at least wii games don't encounter it

@mm201
Copy link

mm201 commented Mar 12, 2015

I think it's memory corruption on the DS. On MKDS, the error happens right after the DHCP request but before any actual traffic, but Pokémon Platinum makes it as far as conntest.

@LuisMayo
Copy link

This happens on Animal Crossing Wild Word with error code 552201

@AiyionPrime
Copy link

This happens on Animal Crossing Wild Word

It does here, too.

Interestingly enough, it did not with the original server iirc.

@InternalLoss
Copy link

This even happens on Wiimmfi - it's possible its just some weird DS bug that's finally arisen, since it does seem to error out on bandbroseuds right after the connection test.

@Jiriki79
Copy link

Also seem to be getting this on megaman. Starforce dragon/leo/pegasus

@patapancakes
Copy link

It is also possible to get the DS into an inconsistent state if gpcm.gs.nintendowifi.net fails to return a valid LOGGED_IN response (e.g. if the proof-of-login is incorrect). In this case, the user must restart the DS with a soft reboot before Wi-Fi connections can be made. Until the user does so, all attempts to connect will fail at the connection test stage, as if the connection test server did not respond.

This sounds like it could be relevant to this issue. It's from this page.

@patapancakes
Copy link

I found the issue. The server treats the 13 digit console-provided userid as the GameSpy userid, which is supposed to be only 9 digits and generated by the server.

@smpial
Copy link

smpial commented Jan 5, 2025

I found the issue. The server treats the 13 digit console-provided userid as the GameSpy userid, which is supposed to be only 9 digits and generated by the server.

How to fix it?

@patapancakes
Copy link

I found the issue. The server treats the 13 digit console-provided userid as the GameSpy userid, which is supposed to be only 9 digits and generated by the server.

How to fix it?

See my fork here, it's not a great fix but it should work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants