2. Using the Authentication Server Error Simulator

2.1. Framework for the Authentication Server Error Simulator

The Authentication Server Error Simulator has the following framework.

Figure 2-1. Framework for the Authentication Server Error Simulator

A dummy authentication server—separate from the normal authentication server—has been set up to simulate error responses. Because the 3DS system’s connection is configured to use the dummy authentication server, a dummy domain name system server has also been set up to return fake DNS responses. To check errors, you must manually configure the DNS server settings, using the Nintendo 3DS Internet connection settings, so that the 3DS system’s DNS requests are sent to this dummy DNS server.

2.2. Setting Errors

2.2.1. Manual DNS Settings for the Nintendo 3DS

You can manually configure the Nintendo 3DS DNS settings with the following procedure.

  1. Connect your computer to the same access point as the Nintendo 3DS and access https://nas-err2.mng.nintendo.net/. In the authentication window that appears, enter the login ID and password that are automatically issued by OMAS. To verify the login ID and password on OMAS, in the Common Title Data Information of the title to be verified, see Error Simulation Server.
  2. The error selection screen appears. Select any error with a 002 display code.
  3. Check the IP address for the dummy DNS server listed in the How to Use field at the top of the error selection screen, and then configure that for the Nintendo 3DS. All other settings can be left as is. Disable the automatic acquisition of DNS and enter the IP address in the Primary DNS field under Advanced Settings. Leave Secondary DNS set to 000.000.000.000.
  4. Save those settings and make sure the connection test works.
Note:

Configure the dummy DNS server, using the Nintendo 3DS Internet connection settings, and not the access point settings. Special access point settings are not needed. If the connection test fails, verify again that the PC and Nintendo 3DS are connected to the same access point, using the same global IP address, and that the connection failure error does not have a display code that begins with 003.



2.2.2. Setting the Error Response

Use the following steps to configure the errors returned to the 3DS system.

  1. As indicated in 2.2.1. Manual Domain Name Settings for the Nintendo 3DS, connect your computer to the same access point as the Nintendo 3DS and access https://nas-err2.mng.nintendo.net/.
  2. Select the error code to return from the list. You can cause the selected response error to occur on a 3DS system for which the dummy DNS server settings were performed manually, and that is connected to the same access point as the PC that made the settings (regardless of the title).
Table 2-1. List of Selectable Authentication Errors
Error Code Cause

002-0101

The response from the authentication server was empty.

There is a problem with the authentication server or the network.

002-0101

The authentication server returned an empty response code.

This error is caused by a bug in the authentication server.

002-0102

Service is stopped for this user (on the application server side).

002-0102

Service is stopped for this user (on the friend server side).

002-0106

A large number of user IDs have already been created for a single system.

002-0107

Application information does not exist on the server.

002-0109

Invalid information was returned to the authentication server during authentication.

002-0110

Service for the application has ended.

002-0119

The friend presence daemon version is old.

002-0120

The application version is old.

002-0121

The system has an invalid certificate.

002-0122

An invalid connection was set.

Try to connect to a different environment.

002-0123

The card information is invalid.

002-0124

This card is stopped.

002-0125

Application information does not exist on the server.

The reason for this error is different from the reason for 002-0107.

002-0999

Service is stopped for this user (on the application server side).

002-0999

Service is stopped for this user (on the friend server side).

002-3400

HTTP status code of 400 (on the application server side).

There is a problem on the authentication server.

002-3400

HTTP status code of 400 (on the friend server side).

There is a problem on the authentication server.

002-3503

HTTP status code of 503 (on the application server side).

The authentication server has stopped or is experiencing heavy network traffic.

002-3503

HTTP status code of 503 (on the friend server side).

The authentication server has stopped or is experiencing heavy network traffic.

003-21XX

Failed to connect to the connection authentication server.

003-30XX

There was a problem with the authentication server during Nintendo Zone authentication.

003-31XX

There is a problem with the Nintendo Zone authentication server.

003-32XX

Nintendo Zone authentication failed.

None.

Authentication was successful; the response was an invalid SVCLOC token (for licensee applications that use an independent server).

Note: This can only be selected for titles that use an independent server.

002-4127

Authentication was successful; the SVCLOC keyhash was invalid (for licensee applications that use an independent server).

Note: This can only be selected for titles that use an independent server.

Note:

After friend server authentication succeeds, the same token is maintained until either the token expires or the CTR system is turned off. Consequently, to check errors on the friend server after authentication has succeeded (after checking for errors on the application server), you must turn off and then restart the 3DS system. You must also power-cycle the 3DS system to check for any 003-XXXX errors after checking for 002-XXXX errors. Checking without rebooting the 3DS can cause other errors.

Note:

In the default state, 003-21XX is set. Also, depending on the router or access point used, you might receive the default error of 003-21XX when the device is reset.


CONFIDENTIAL