How to succesfully modify the NAT networks addresses?

[Poltsi]

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-sub...

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

[neergaard]

I am having a similar problem and wonder if you ever figured this out.

My input is: what appears to be happening is that the VMware services on Windows get their configuration information from the Windows registry (not through the config files).  When you make changes through the virtual network editor, the updates are pushed to both the registry and the config files. 

But, if you edit the config files are changed, they have no affect since the processes don't read them directly.  On linux, there is no registry, so changing the config file works.

I am hoping to find some way (through the command line) to cause Workstation to read the config files and update the registry.  No luck so far.