Mh, NAT should work. Did you try Bridged? Can you connect from your Guest OS to your Host OS or vice versa?
Which product from VMware are you using?

I just looked and the WF is off.  I am using VMWare Player 3.0.1.  I tried bridge and bridge + replicate physical network state and nothing yet.  I cannot ping my WMClient from my host OS and vice versa.  My IP on my host is 192.168.220.1 and my IP on my client is 192.168.1.8.  Could this be the issue?

Thanks guys.  I am VERY new to VMWare and thought once I saw it that the subnets being different could be the reason, but thought I'd ask first. 

Well, again, that MIGHT not be the reason for the Internet access failure.  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.  But if the host NAT adapter is the one you gave the IP address for, then you definitely aren't going anywhere.

Whatever mode your guest is on (Bridged or NAT,) you need to make sure it's IP is on the subnet with the IP of the host's adapter for the network, in question.  (Also, if you're bridged in the guest, you need to make sure WHICH adapter on the host the bridge is assigned to, and make sure that the IP of the guest is on the network that your host is on.)

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.

I suppose you are working wireless!!

Well VMware does not work on the build-in radio adaptar!!  You have to use a USB-adaptar or plug your device on a CAT5

Well I only have experience with VM in combination with Backtrack. The PCI card within Backtrack virtual does not work. After investigating the forum of Backtrack, I found a confirmation that Backtrack only works with USB-adaptars.

So It seems VM OS or VM distro dependent if the PCI-card is working!!