This article is best viewed with a web browser.
What we know so far:
- This is unrelated to the previous widespread Error Code: 003-2101 issue which happened in 2015.
- The new isolated cases are coming from selected PLDT and Globe users.
- This problem affects all 3DS family handhelds: the regular 3DS, 3DS XL, 2DS, New 3DS, and New 3DS XL.
- Only the built-in 3DS browser works.
- All other 3DS online features including, but not limited to, the Nintendo 3DS eShop, System Update, Connection Test, and Online Multiplayer features will only generate the same dreadful error.
- Laptops, smartphones, and other gadgets are unaffected. They exhibit no obvious network-related anomalies even if they are using the same connection.
- It is usually a self-limiting problem which means that it will eventually disappear on its own.
As the saying goes, "something is better than nothing".
For PLDT Users:
- Unplug both your router and modem from their power outlet.
- Just to be safe, wait for 60 seconds before plugging them back in and turning them on.
- From your 3DS HOME Menu, highlight and select the System Settings Icon.
- Select Internet Settings
- Select Connection Settings
- Delete all existing connections. To do this, select the connection file, then select Delete Settings.
- Select Delete. Repeat until all connections are removed.
- Create a new connection for PLDT
- From the Connection Settings page, tap the New Connection option
- Tap Manual Setup when the prompt asks if you would like help with the Internet connection setup.
- Tap Search for an Access Point.
- Once the search has completed, locate and tap the name of your wireless access point.
- Enter your WiFi password.
- Tap OK to save your settings.
- Tap OK again to begin a connection test.
For Globe Users:
- Disconnect all devices that are currently connected to your router.
- Reboot your router. You can follow the steps mentioned under For PLDT Users above.
- If the Connection Test fails, reboot your router again and repeat all the steps.
- You need to keep repeating them until you find a "stable IP".
- Go to *https://www.vpnmentor.com/tools/ipinfo/ to check your IP.
- If your IP starts with 222.xxx, keep rebooting until you get **180.xxx.
*Thanks Vivian for the new lookup tool.
**Or any stable IP where the Connection Test will successfully connect.
Nintendo's Recommendations:
- Obtain your network's IP Address information.
- From the HOME Menu, highlight and select the System Settings Icon.
- Select Internet Settings.
- Select Connection Settings.
- On the connection settings screen, select the connection file, then select Change Settings.
- Select the right arrow, then select IP Address.
- Where it now says Auto-Obtain IP Address, select No, then select Detailed Setup.
- Select IP Address, then hold down the left arrow to delete the existing IP Address (it defaults to zeros).
- Enter the IP address listed in within your PC's network information, but add 10 to the last digit. For example, if your PC had an IPv4 address listed as 192.168.1.2, this will become 192.168.1.12. With this an all following entries, make sure to include the '.' (period) between each number.
- Select OK to return to the IP Address screen, then select Subnet Mask. Hold down the left arrow to delete the existing Subnet Mask, then enter the Subnet mask exactly as it appears in your PC.
- Select OK to return to the IP Address screen, then select Gateway. Hold down the left arrow to delete the existing Gateway, then enter the Default Gateway exactly as it appears in the PC.
- Select OK to confirm the changes. You will be asked to perform a DNS setup; select Set Up to be taken to the Auto-Obtain DNS screen with No already selected.
- Select Detailed Setup, then Primary DNS. Hold down the left arrow to delete the existing DNS, then enter 8.8.8.8.
- Select OK to return to the DNS screen. An option is available to enter a Secondary DNS. This is not required to complete the setup process.
- Select Save, then OK. Select Test to begin the connection test.
Don't be discouraged if the issue persists. The Error Code will eventually resolve by itself but the estimated window of resolution is random. For example, some people might get the error for several hours while others might experience it for few days. The longest recorded issue happened in 2015 where the problem persisted for 8 straight months.
The recommendations featured above are specifically tailored for Error Code 003-2101, 003-2102, and 003-2103. Other Error Codes may require a different approach.