gunntims0103
November 22nd, 2006, 16:48
news via ars (http://arstechnica.com/journals/thumbs.ars/2006/11/22/6056)
One of the Imperial Wii units has been stuck with a nasty problem. Seems that although we could connect using WiFi to Nintendo and grab system updates, we could not connect to the Wii store in order to view the EULA that's necessary before buying virtual console games. Every time we tried, we received error 220602.
When we called Nintendo, they had no idea what the problem was all about. The suggested the following, which you should try, too: a) changing your WiFi router to channel 1 or 11, and b) moving your Wii closer to the router. For many people, this is a solution. For us, it wasn't.
It looks like Nintendo may not be at fault for this error, as some snooping about led us to realize that the real issue was a crappy DNS server. It seems as though the various hostnames Nintendo is using haven't fully propagated throughout the 'net, even several days after launch. After talking with some support specialists, it looks like this DNS problem is affecting pockets of users here and there.
In Wii Settings you can adjust your Internet connection and manually specify a new DNS server, if you wish. We took a different route, and changed the DNS servers on our WiFi router. From what we can tell, the Wii will use whatever is set as your Primary DNS, or DNS 1. It was enough for us to swap our primary and secondary DNS. You may have to set out in search of another DNS server to use, at least temporarily, until the DNS propagation is complete (surely by the end of this week).
One of the Imperial Wii units has been stuck with a nasty problem. Seems that although we could connect using WiFi to Nintendo and grab system updates, we could not connect to the Wii store in order to view the EULA that's necessary before buying virtual console games. Every time we tried, we received error 220602.
When we called Nintendo, they had no idea what the problem was all about. The suggested the following, which you should try, too: a) changing your WiFi router to channel 1 or 11, and b) moving your Wii closer to the router. For many people, this is a solution. For us, it wasn't.
It looks like Nintendo may not be at fault for this error, as some snooping about led us to realize that the real issue was a crappy DNS server. It seems as though the various hostnames Nintendo is using haven't fully propagated throughout the 'net, even several days after launch. After talking with some support specialists, it looks like this DNS problem is affecting pockets of users here and there.
In Wii Settings you can adjust your Internet connection and manually specify a new DNS server, if you wish. We took a different route, and changed the DNS servers on our WiFi router. From what we can tell, the Wii will use whatever is set as your Primary DNS, or DNS 1. It was enough for us to swap our primary and secondary DNS. You may have to set out in search of another DNS server to use, at least temporarily, until the DNS propagation is complete (surely by the end of this week).