[quote name='io']OK, so right out of the box mine doesn't connect to the wireless signal that every other device in my house uses (including a couple of 3DS's)... OK, so I always had problems with the Wii in the same spot so I thought maybe the signal was just bad there. But my network was showing 2 out of 3 bars so I didn't think so.
I just found this info on the web:
and so far it is working - it is
downloading the update now at least. But what has always sucked about Nintendo is the error messages. The stupid error says it "couldn't find the wireless network" (or something to that effect). Well, yeah, it actually could, but something else was wrong. Then in the detailed info it says to check the security setting. What I don't understand is can't they diagnose a little more precisely what the problem is? I mean, if the security setting is wrong or the network is out of range it would be nice to know if that is the actual problem instead of this half-assed handwaving error message that gives you all sorts of confilcting info. It was neither of those in my case since the instructions above (posted by a random user on the Nintendo support forum - not by Nintendo themselves of course) worked.
I'm not looking forward to the Wii system transfer since that means having both touchy systems up and running and on wireless at the same time.
Edit:

ing A! I spoke too soon. Just went back out to check on the progress and "An error has occured". Yeah, that's really helpful. Now it is back wanting me to reconfigure my network settings again #-o.
Now after "checking for update" for like a minute I get error 105-4011. The update never starts downloading. Really useful Nintendo.[/QUOTE]
I don't think the issue is Nintendo's fault.
You can set any IP address within the range of your subnet. It doesn't have to be the IP your computer has + 10. Depending on your setup, that IP could be out of the subnet range. So, try +2. Make sure the subnet mask remains the same.
For DNS, try auto obtaining. You can't just enter any number you want, or "8.8.8.8". If your ISP has a different DNS server than the one listed, then it's address wont be 8.8.8.8. (Think of it this way, when you mail a package, you put the recipients address. Not some random address found online.)
The 8.8.8.8 DNS belongs to Google. This could lead to problems if too many Wii U's (or other connections) are requesting Domain Name lookups from the server, AKA too many requests which could cause a timeout. (DNS = Domain Name Server. It turns "www.whatever.org" to the appopriate IP address. Without DNS, you'd have to enter a website's IP address to access it).
If you're still having issues, type cmd into start, then type "ipconfig /all". Scroll up to your ethernet or wireless adapter, and note down it's DNS. Try using this on the Wii U. (Will appear under "DNS Servers").
Just remember that all relatively new consoles have had issues on launch day. You're bound to encounter problems with the network as there's so many people using the Wii U, and they're all trying to connect and have fun. Just give it some time if the above steps and info didn't solve your problem(s).
To put it easily; It's the first day of summer. You're driving your car (information/packets) to the beach (server). But you get stuck in a traffic jam due to everyone wanting to visit the beach (too many requests from the server, so the server drops packets and/or denies information).
Does anyone know if the Wii U has a VPN setting in it's Network options? Would be nice to use it through my VPN.