Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 193504

Re: DHCP/DNS/Network issues with testlab - Virtual Network Editor is killing me!

$
0
0

Hello André,

 

I've tried this before - configuring VMNet8 (NAT) to those specifications (192.168.100.0/24, Gateway at default xxx.2) - assigning that static IP/creating the DHCP scope, assigning the xxx.2/gateway as a forwarding address (validated and applied).

 

I'm not sure what VMNet to place my clients on though... assigning to Bridged will have it draw its IP from my physical router and not my VM'd DC. If I give it a LAN Segment it gets the link-local/169.xxx address. Host-to-Host with a different subnet IP maybe?

 

If I put my client on NAT as well as the DC being on that custom VMNet 8 NAT, my client grabs an IP from my DC's DHCP server but, though my DC can resolve the client's computername to its dynamically assigned IP, a ping times out. My client, however, can ping/resolve my DC though. Strangely, in this configuration, my DC's NIC says "no internet access" though that isn't the case. Any clues? Thanks!


Viewing all articles
Browse latest Browse all 193504

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>