Common errors

The connection may still be using automatic DNS, a different saved slot, or a network that overrides your DNS.

1. Open the connection settings used by this game. Set Auto-obtain DNS to No and copy the current Primary DNS from the setup wizard. Keep IP address assignment automatic.
2. Save and test the same connection. For the Wi-Fi Room, use Connection 1. Gen 4 on DSi/3DS uses the legacy DS settings, not advanced WPA-only slots.
3. If the code persists, repeat the setup on another network. A router or provider may be intercepting DNS.

A successful console test is only the first check; load the save and retry the feature that failed.

Check the Wi-Fi name, signal, security, and the settings supported by your game and console.

1. Move closer to the access point and confirm the exact network name and password. Make the SSID visible.
2. For Gen 4 and DS/Lite, use a compatible 2.4 GHz open or WEP network. Modern WPA-only hotspots are not compatible with these legacy connections.
3. Try channel 1, 6, or 11. Gen 5 on DSi/3DS can use newer system Wi-Fi settings; follow the setup wizard for your exact hardware.

Use a temporary guest network for legacy Wi-Fi and turn it off when finished.

The console may see the access point but cannot complete the network connection.

1. Keep Auto-obtain IP Address enabled. Confirm that the router or hotspot provides DHCP addresses.
2. Check that the hotspot device itself has internet access. A Linux hotspot needs a working upstream connection through Ethernet or another adapter.
3. Recheck the Primary DNS and test again. If necessary, try another network to separate a local routing problem from a service problem.

Do not reset your WFC identity to fix an IP or DNS problem.

The game can use different connection settings, and a saved identity can still fail after the connection test succeeds.

1. Write down the exact error shown in-game and the feature you were opening.
2. If it is 60000, use the migration or reset choices above. This affects Gen 4 Wi-Fi Room entry and Gen 5 online activities, including GTS.
3. Otherwise, confirm the game uses the slot you tested. Gen 4 ignores advanced WPA-only settings; use the setup wizard for the game and console combination.

Test the actual GTS, Mystery Gift, or Wi-Fi Room activity again after correcting the settings.

Peer routing, NAT, or firewall restrictions can prevent a session even when both players can enter the room.

1. Both players should save each other’s current Pal Pad codes, leave the room, and re-enter. Wait 15–30 seconds before retrying an invitation.
2. Try with one player on another network. Avoid VPNs while testing. If the problem only happens behind one router, include that detail when asking for help.
3. For repeated failures, ask staff through the Wi-Fi Room guide about Relay Mode. After staff confirms the change, both players must leave and re-enter the room.
4. Only if multiple emulator instances run on the same computer and network, check that they do not share the same emulated DS identity or MAC address. Restart them after correcting a duplicate.

Migration fixes an existing identity; it does not resolve every peer connection problem.

A dropped session alone does not identify the cause. Keep the exact code and context so support can distinguish network, identity, and service issues.

1. Retry once after leaving and reopening the online feature. Check the service announcements before repeatedly changing settings.
2. Record your game, console or emulator, exact code, the activity, and when it failed. Mention whether the connection test and other online features work.
3. For trades or battles, say whether both players share a network and whether a different network helps. Use the support links in the Wi-Fi Room guide.

Do not repeatedly erase the WFC configuration after maintenance. If the error is 60000 and you want to keep your code, migrate first.