@Bigdave1357 you're right, my approach didn't work for a colleague of mine. 

For reference, you can 'reset' the vmnet-natd process by utilizing:

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --stop

sudo  /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli --start

Strangely enough, since I changed my setup and changed it back to the original, the issue is completely gone. Surviving reboots, suspension, sleep. Before that, I had the same experience as you.

Frustrating!