I have seen this problem a number of times now; i have been able to reproduce it with dlink routers. I know a lot of people have posted with the same issue. After some investigation, I believe whatís causing this issue is the dhcp server on the router. The TF connects first time and gets an address then once its dis-connected from the wireless network and re-connected it will request a new address the dhcp server ignores the request as it believes the tf already has the old address. Exactly what is happening here I have not had time to check with a sniffer. It seems to be something weird in the way the tf releases and requests the address with certain brands of routers (possibly the dhcp server implementation is custom for that brand router) a different dhcp server. This is why often a hard reset on the router works as it is deleting the dhcp address table. The current workaround I have used so far is setting the dhcp lease to a shorter time that way when the tf requests a address lease renew the old address should have already expired. Itís not a perfect solution as shorter dhcp lease causes more network traffic (and if you are playing a online game or using a cloud app it can momentarily lose its connection) but it will eliminate the obtaining ip address error till this is solved properly.
I would have suggested the static ip address but it seems with wifi each time you disconnect and reconnect the static address needs to be re-entered. Can anyone confirm if the static address can be permanently remembered or is it just mt TF trying to make me insane
I hope this helps at least someone out, itís a frustrating problem. I have currently set my lease to 10 minutes as I do travel and disconnect and reconnect a fair bit so this has solved my issues for the time being on the affected wifi networks I use.