VMware Communities
kevinbanks71
Contributor
Contributor

VMware Workstation 8.0.2 on Windows 8 (host) with CentOS 7 (Guests) won't allow Guest networking with other CentOS guest

VMware Workstation 8.0.2 on Windows 8 (host) with CentOS 7 (Guests) won't allow Guest networking with other CentOS guest

I have a Windows 8 laptop (64-bit / 16GB ram / i7-5600U CPU @ 2.60Ghz / 31Gb free of a 260GB drive). I have VMWare Workstation 8.0.2 installed on my Win8 Host.  I have successfully created a CentOS 7 Guest.  The original Guest (CentOS) can successfully ping the real world and browse the internet.  The Guest can also access files on the Host workstation.  All of this is done with NAT enabled on the Guest.

I can also create multiple (at this time, 3) guest workstations with no problem.

This issue is that I can not create network settings on my CentOS 7 guest VMs that will survive a reboot AND that will allow me to have the following net configurations:

VM1 (Server1)

IP: 192.168.122.50

Netw: 192.168.122.0 /24

Domain: .example.com

VM2 (Client1)

IP: 192.168.122.150

Netw: 192.168.122.0 /24

Domain: .example.com

VM3 (Outside1)

IP: 192.168.100.100

Netw: 192.168.100.0 /24

Domain: .example.org

I am using this setup to study for my RHCSA & then my RHCE exams.  But networking settings need to be easily configurable, reliable, and survive a reboot.

Thank you for your assistance.

Kevin Banks

kevinbanks71@gmail.com

0 Kudos
1 Reply
continuum
Immortal
Immortal

Make sure your 3 Centos-VMs use different mac-addresses.
For troubleshooting try a static-setup - which should not change all by itself once correctly configured.

The NAT-servce assigns IPs starting with *.*.*.100 - if you disable DHCP inside the VMs and assign IPs in the range from *.*.*.3 - *.*.*.99 you can continue to use VMnat8.
If you really want to use the IPs you listed you need to set a extra long lease-time


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos