You're correct, you didn't understand my post. (Sorry, maybe I worded it poorly this time.)
What I intended was this:
If you're using NAT for the guest, you're correct, in that the guest (IF configured for DHCP) will get an address from the NAT, and be able to use that address to reach the outside world. (Per my statement - IF the NAT adapter on the host IS on the same subnet as the guest (if IT is configured for NAT, also) then the guest SHOULD be able to ping the outside world and / or browse the internet.)
I then should've clarified, when I talked about the NAT adapter. I meant to say the NAT network configured for the NAT adapter on the host should have a subnet matching the IP that the guest shows. If the guest showed an IP of 192.168.1.8 (as he noted) and the host NAT configured network was 192.168.220.1 (which was what I wanted to clarify) then he obviously didn't have the client getting address from DHCP on the NAT, and the address would NOT ping out. (Which you noted when you said - This part obviously does not work if the guest's NAT network adapter is assigned a static IP which is different to the internal network.)
Sorry if I left it vague. I had meant to say the NAT network in the config in VMWare, not the adapter, itself. Was very preoccupied today, with work, and somehow, missed that I said it that way. Sorry for any confusion.
~ hayabusa ~
"All men can see these tactics whereby I conquer,
but what none can see is the strategy out of which victory is evolved."
- Sun Tzu, 'The Art of War'
OSCE, OSCP (Former - GPEN, C|EH - both expiring / expired)