Access VM from External Source

[JMorse1988]

Hi,

I have looked over some of the available threads on similar issues, but I am unable to get this working. I would like everything to communicate, but I'm only half way there with my current configuration.

I've got Workstation on a Laptop, which hosts 1 VM. I've configured IPv4 on the VM. I've also configured a Domain, DNS, and I've got overall communication with my VM's and host. However, I'm adding a physical server into the mix, and would like to be able to communicate with my physical server, which is connected via switch to the laptop.

Physical Server <---> 4-port, simple switch <---> Laptop w/Workstation hosting 1 VM.

With the current configuration, I have communication between my Laptop, and my VM. I have full communication between my Laptop & VM, and I am able to do the same from my Server to my Laptop. I am also able to Ping my Server from my VM, but that is about it. I am unable to ping my VM from my Server. I am curious to know if I need to completely reconfigure my IP Scheme and utilize Bridging, or if there is simply a configuration change I need to make. When I disabled NAT, and attempted to utilize bridged networking,  I had no communication at all.

Here is my current configuration:

Virtual Network Editor

• VMnet0 - Bridged - Automatic
• VMnet8 - NAT - Subnet of 192.168.174.0 | 255.255.255.0 | DG 192.168.174.2 | The rest is default

Machine configuration:

• VM (Network Adaptor set to NAT)
  • IPv4 192.168.174.2
  • Sub 255.255.255.0
  • DG 192.168.174.2
  • DNS 192.168.174.133
• Laptop
  • IPv4 192.168.1.10
  • Sub 255.255.255.0
  • DG 192.168.1.2
  • DNS 192.168.174.133
    • 192.168.1.10
• Server
  • IPv4 192.168.1.15
  • Sub 255.255.255.0
  • DG 192.168.1.2
  • DNS 192.168.174.133
    • 192.168.1.10

I may end up starting over, but any assistance with this would be helpful, since I have full communication between my Laptop and VM, and I can even ping the Server from the VM, the hostname resolves as well. This tells me it's most likely a NAT issue. I tried port forwarding, but it didn't work.

Thank you,

Justin

[Aiden1]

Hi

Welcome to communities.

First set all your vm NIC to bridge mode and check .

[JMorse1988 · Accepted solution]

Aiden1, thank you for your response. I was able to resolve this issue on my own, and it did included switching the NIC configuration to Bridged in VM properties.

Here is how I was able to resolve. This may not work for everyone, or may not be the desired or standard configuration, but so far I've not had any issues. I'm fairly new to this, so please feel free to make recommendations, or to point out any errors or redundancies you see:

1. Configure vmware workstation Virtual Network Editor configuration:
   • VMnet 0 - Bridged - Auto Bridging
   • VMnet - Host-only - Subnet IP: 192.168.1.0 Subnet Mask: 255.255.255.0
2. Configure VM
   • Edit Network Adapter properties of VM's - Set Network Connection to Bridged, I also enabled "Replicate physical network connection state". 
3. Configure my Laptop NIC.
   • IP 192.168.1.10
   • Subnet 255.255.255.0
   • DG 192.168.1.0
   • DNS (My DC hosts DNS and is configured as such) 192.168.1.133 (IP of DC)
4. Configure my VM NIC's to match this configuration:
   • IP of 192.168.1.* desired vm address
   • Subnet 255.255.255.0
   • DG 192.168.1.0
   • DNS 192.168.1.* (Desired address of DNS Server)

I added the VM IP's in DNS, both forward and reverse, and I am now able to fully communicate between my Laptop, the VM's hosted on my Laptop, and the physical server connected to my Laptop via Ethernet cable. This includes file-sharing, setting up a domain, pings, etc. The server and Laptop are connected to a simple, dumb 4 port switch I got at a computer store.

In case anyone is having issues, or would like to match my IP config:

Laptop (Physical) - 192.168.1.10

Domain Controller\DNS (VM)- 192.168.1.133

Oracle Database Server (VM) - 192.168.1.134

Exchange (Physical Server) - 192.168.1.15

Hope this helps someone!

Thanks,

Justin

[JMorse1988]

Update: You may need to un-tick the "Replicate physical network connection state" option, I did experience some issues and disabling this function seemed to help.

Thanks,

Justin