Hello,
My env is as follows:
Host: Windows 7 Prof 64bit / Fedora 20 64bit
VMWare Player version: 6.0.4
Guest: CentOS 6.5 64bit
Networking mode: NAT
What I tried to do is change the address space of the Windows host NAT from whatever it has randomly selected to that used by the Linux host (and which is also hardcoded in the actual application server running within the guest CentOS).
I found these instructions:http://nodsw.com/blog/leeland/2012/02/03-change-vmware-player-networking-settings-especially-nat-subnet-range
Executing the commands goes well, and the configurations (vmnetdhcp.conf, vmnetnat.conf) in C:\ProgramData\VMWare\ looks correct, but as a result after having rebooted the host, and started the guest, I can log on with a SSH-client to the new address (which means that the new network configurations work in this aspect), but from the guest I can not even ping the address from which I am connecting to, and the NAT is not working either.
If I remove the *conf mentioned above, reboot the Windows host and let VMPlayer create new files with new random network for NAT by starting the guest, the NAT works as expected, I can connect to external addresses (such as the yum repositories) and ping the host address.
AFAIK this problem has plagued VMPlayer since 4.0
The reason why I need to manually configure the NAT-value is that as I mentioned before, I'm using the same guest image both in Linux and multiple Windows (I have a Win laptop and a WKS), and I'm running applications which require that I set the listen-address, so the VMPlayer needs to give the same address space in NAT.
Any advice is greatly appreciated,
Poltsi