When I had sonic.net, my Wii console connected to the Nintendo server just fine. Now, with AT&T DSL, it sees the SSID, connects to the wireless router, but can't get to the Nintendo Server.
"Error 52232 Unable to Connect to the Server."
All the computers in the house work fine through this router.
Apparently it's some firewall issue in the 2Wire 2701HG-B, though I did find someone that apparently got it to work with the 2701HG-B being sold in the Southeast.
The Nintendo support site states:
------------------------------------ Error Code: 52232
There appears to be an issue with your wireless router's firewall.
- To ensure wireless interference is not causing the problem, click here to review our "Slow Downloads or Errors Received While Connecting" help.
- It is possible that your Internet Service Provider (ISP) is not compatible with the Wii console. For instance, if you need to login with a user name and password when you try to go online for the first time after restrarting your PC, your ISP is likely not compatible. Please contact your service provider for more information.
- If this error occurs regularly, while you are playing at home, it is likely a connection problem related to your firewall settings. For more information on firewalls, click here.
- Comcast users, please click here to view the Wireless Routers with Comcast-branded firmware which we have identified as being potentially incompatible with the Wii console.
- Are you using a Netgear brand wireless router? Our expeirence shows disabling the "SPI Firewall" of the router may help the connection. The "SPI Firewall" option is typically found under the "WAN Setup" tab of the router's settings. For information on accessing your router's settings, please click here and select the model of the Netgear router you own (if available).
If you are still receiving this error code, please click here for assistance.
Naturally AT&T Tech Support in Bangalore was no help, though they did offer to help me for $139.
The only thing I tried was manually putting in the DNS addresses, to no avail (assuming I have them correct at 126.96.36.199 and 188.8.131.52.).