Comment 24 for bug 1037192

I've experienced this issue on machines which have:
- ubuntu 12.04 installed
- used network manager with dhcp
- have a 3.2 kernel installed
- used nfs4 with kerberos

Error Messages on the nfs server in syslog are:
~~~~~~ snip ~~~~~~
rpc.gssd[737]: ERROR: unable to resolve 0.0.0.0 to hostname: Name or service not known
rpc.gssd[737]: ERROR: failed to read service info
~~~~~~ snap ~~~~~~

Until now i could only test one box, but after i upgraded it to a 3.8 kernel (via linux-image-generic-lts-raring package) the ip address was set properly in clientaddr.
I will test further systems during this week and hope that also resolves the issue on them.
Maybe this helps others also to resolve this issue or at least find a workaround.