Error code 52212 and "This Wi-Fi Connection ID does not exist."

[Camwoodstock]

When trying to connect to Game Sync, the game spits out this error code--both from the main menu and in-game. Trying to follow both the protocol for 052110-x or 60000 are dead ends;

• In the former's case, I cannot locate anything Java-related in the firewall; neither an inclusion nor an exclusion. Perhaps I didn't look hard enough because I was tired? Admittedly, I'm not used to searching the firewall, but no key words such as "Java", "Adoptium", or "Temurin" were present.
• In the latter's case, I tried to follow the protocol for 60000, despite getting 52212 to start with and not seeing any 60000 code. After grabbing the Pal Pad code and Wifi CID, it bafflingly declared the Wi-Fi CID didn't exist and didn't clarify further. I double-checked, there was not a typo in there, so I have zero clue what that's about.

Admittedly, I've got no clue what is going on here. My only guess is an obscure firewall setting, but it's unclear just what I need to do there (at least, to my tired brain, it is 2:12 AM as I write this).

[kuroppoi]

I don't think I've ever seen that one before. Try searching the firewall for programs containing OpenJDK or some such as well.

In the meantime, please provide program logs so I can see if perhaps it goes wrong at a specific step:

1. Use the newest version if you aren't already (1.3.6 as of this message)
2. Start the program and try using Game Sync
3. After failing to connect and getting the error code screen, send the log file located at logs/debug.log here

[Camwoodstock]

There's no OpenJDK in the list--neither to include nor exclude. I tried entering a rule for javaw in the Eclipse folder--nothin'.

Already on 1.3.6, don't worry! I have... no idea how useful the debug log is, it doesn't seem very helpful at all. The only thing I noticed is that, in-game, it started green, turned red briefly, then turned green again for a few seconds before turning red. debug.log

[Camwoodstock]

That is well and truly baffling. Connected to the Poke Classic Network, and then on opening the game, it immediately yells OY WHAT'RE YOU DOING YOUR WIFI DATA MAY HAVE JUST BEEN ERASED!!!

...my friendcode is entirely unchanged, no clue what that was about.

[kuroppoi]

According to the debug log, your DS successfully connected to the DNS server, but nothing else. I guess something on your PC might specifically be blocking traffic on port 80 and/or 443, so you may want to check your advanced firewall settings to see if any rules are configured that block it. Maybe some antivirus software could potentially block network traffic, but I'm not sure on that.

[kuroppoi]

That is well and truly baffling. Connected to the Poke Classic Network, and then on opening the game, it immediately yells OY WHAT'RE YOU DOING YOUR WIFI DATA MAY HAVE JUST BEEN ERASED!!!

...my friendcode is entirely unchanged, no clue what that was about.

Did you switch to another DS perhaps? If not, it probably doesn't mean anything... probably

[Camwoodstock]

He's getting a text message later.

I did not switch to another DS; to be more precise, I did, but it was BEFORE I futzed with the internet, so I didn't think it mattered. Literally only changed the DNS, and it wigged out like that. Anyways, now I need to wait out the in-game day without futzing with the system clock. I'll report back if things bork in that time?

[kuroppoi]

If you got that message then it is at least successfully connecting to the Game Sync server, which means that everything should be working correctly. As for the cooldown -- it just seems to happen sometimes when the game detects that you've recently changed the time or played on another system. The best thing to do is to not do either of those things while you wait for the cooldown to expire. I'll close the issue as resolved, but feel free to comment here if you have any other problems or questions regarding this issue.

Also, I take it that some sort of antivirus was causing the problem? Would be helpful to know for future reference, in case anyone else runs into similar problems :)

[Camwoodstock]

The antivirus in specific was VIPRE, but I'd wager just about any antivirus with a firewall option that acts independently of Windows' in-house one can also decide to act a fool. The fix was fortunately simple; it was port 80 from "javaw.exe", so whitelist that executable.