Comment 2 for bug 946856

I've had the same issue; workaround is to go back to the network configuration, configure it again and off you go.
Don't ask why, but after that it work, so the problem is probably somewhere in the network configuration the first time