Yes it is a recurring theme which I have had a rant about in the past.
Nothing much seems to have changed with regards to it being suggested as the panacea to every question mentioning networking.
The problem of being connected but no internet access can be caused by a number of things, and using static addressing on a wireless interface of a (client) device is almost never the right answer (in fact one of the few examples I can think of is for the ends of a wireless bridge link where in any case the addresses of those ends may not matter to network using the link).
E7er never really explains why the cause must always be dynamic addressing or else how the suggested steps magically fix any problem and in any case the OP hasn't asked how to port forward something to the wireless device either.
(to the OP)
My general advice on wireless is that on anything newer than 5 years old,
Firstly, for b/g/n devices check the router or access point is set for 20MHz (or failing that, Auto 20/40MHz) rather than 40MHz only as some clients cannot reliably connect in that mode.
Then if you are using a passphrase for wireless security choose a security mode of WPA2-AES (CCMP) on the router as the devices can usually perform this optimally, and try to find driver or OS updates if it seems to support WEP or WPA(1) only (or TKIP only).
But if having problems or are trying to establish a connection for the first time then fall back to no security and add encryption when you know the devices work together in that mode.
Be prepared to "forget this network" on client devices then look for the network to join again (old settings including wrong security mode can cause problems).
prompt $P - Invalid drive specification - Abort, Retry, Fail? $G
prlzx on iDNET: ADSL2+ / 21CN at ~4Mbps / 700kbps with IP4/6
Edited by prlzx (Tue 30-Apr-13 20:54:09)