Accepted Solutions
The main problem seems to be the virtual networks for "host-only", "NAT" and "shared".
For these 3 virtual networks there are 3 ethernet adapters added to your Mac OS-X.
By default only 2 not 3 virtual networks are created by VMware Fusion, VMnet1 (Host Only or Private to my Mac) and VMnet8 (NAT or Share with my Mac). The "add_bridge_mapping en0 2" is not a default and is created if a User chooses to bind the Bridge to a specific Host NIC.
Where yes needs to be no.Stop VMWare Fusion and restart.
With the following command in the terminal you will see only the en0 ethernet adapter:
ifconfig
Now startup the host OS and voila it should work.
Be aware that it might be possible that you need to do these steps again once you altered the network settings through the GUI of VMWare.
Because it is a configuration file and it might be edited again by VMWare Fusion.
I have not tested this since its now working for me.
Removing VMnet1 and VMnet8 from the Host and not having them available for the Guest's is fine if you only ever need to use Bridged Networking however it is not always practical so while this particular workaround may have helped you it is not necessarily the answer for others having Internet/Network Connectivity issues! 
Additionally if one is going to manually edit any of VMware Fusion's configuration files it should be done with the Virtual Machines shutdown, not suspended, and VMware Fusion closed... so your steps are not in proper context!
As you mentions Network adapter in VM is configured to be bridged (to get its own IP address) and when i am within the OS that is installed on the VM the IP i get back is a diffirent one then the host OS. If you are using brodge network then you have to get same subnet ip address as your host. I think you configure the vm NIC as DHCP then renew the ip address also make sure that you are getting same subnet IP address as your host.
The main problem seems to be the virtual networks for "host-only", "NAT" and "shared".
For these 3 virtual networks there are 3 ethernet adapters added to your Mac OS-X.
By default only 2 not 3 virtual networks are created by VMware Fusion, VMnet1 (Host Only or Private to my Mac) and VMnet8 (NAT or Share with my Mac). The "add_bridge_mapping en0 2" is not a default and is created if a User chooses to bind the Bridge to a specific Host NIC.
Where yes needs to be no.Stop VMWare Fusion and restart.
With the following command in the terminal you will see only the en0 ethernet adapter:
ifconfig
Now startup the host OS and voila it should work.
Be aware that it might be possible that you need to do these steps again once you altered the network settings through the GUI of VMWare.
Because it is a configuration file and it might be edited again by VMWare Fusion.
I have not tested this since its now working for me.
Removing VMnet1 and VMnet8 from the Host and not having them available for the Guest's is fine if you only ever need to use Bridged Networking however it is not always practical so while this particular workaround may have helped you it is not necessarily the answer for others having Internet/Network Connectivity issues!
Additionally if one is going to manually edit any of VMware Fusion's configuration files it should be done with the Virtual Machines shutdown, not suspended, and VMware Fusion closed... so your steps are not in proper context!
You are right on everything you say.It just helped me to get VMWare Fusion to work on my Mac.
And it working well in my particular situation.
It maybe helpfull to someone.
Yes it was helpful in your situation and it may also be for some others but not necessarily all others and also I posted what I did because while it was a workaround solution in your particular case nonetheless I consider it to be an extreme workaround and should only be implemented if one only needs Bridged Networking and or another fix/workaround can be implemented that doesn't cripple the defaults.
I just wish it was possible to control the network settings on this level in VMWare userinterace.
With VMware Fusion 5 Professional there is a Virtual Network Editor in VMware Fusion's Preferences. So between that and the Virtual Machine's Network Adapter Settings GUI the same should have been able to accomplish without manually editing the networking file. If you don't have VMware Fusion 5 Professional then manually editing is the other native option however there is a third party tool out there that can do it also although I'd opt for manual editing if I didn't have VMware Fusion 5 Professional.
To awnser your question why i did not post the entire network settings is easy, i am just not allowed to do so.
In Corporate environments this is certainly understandable however if it was as I suspect an IANA IP Address in the 169.254.0.0/16 range (RFC 5735 — Special-Use IPv4 Addresses) I doubt that it would have been an issue to report that. Again the reason for mentioning including relevant technical information when seeking help with technical issues to make it easier for those of us that help in these forums to do it more easily and as others read they hopefully will become aware that technical issues may need technical details to resolve more easily. I probably would have helped you when you first posted however I've been, and still am for another week, on vacation so I haven't responded to as many posts in the last two weeks as I normally would.
Disabling the network adapters like i did was the trick that helped me.It may help someone else.
It's always good to post what helped resolve an issue so others can benifite from it! For others having connectivity issues just remember in cases such as this, removing the defaults, it needs to be done with proper considerations.
I was not at a system I could check and that is why I said "should" not "could" when I said "...the same should have..." believing because the Virtual Network Editor in VMware Workstation does allow for the removal of the default VMnets. This is just one more thing about the "Professional" version of VMware Fusion that make its a joke! Looks like, as it been from the beginning of VMware Fusion, manually editing configurations files for things such as this it the only way to go! 