creative555
asked on
No internet connection on the test lab server using VMware 10 and NAT
Hello,
I have virtual lab running on VMWare workstation 10 and using NAT (VMNet8) (shared host's IP address with VMS) for networking.
Below are the settings:
I installed DNS and DHCP on my servers 2008 R2 and set NAT settings as VMNET8 to use the following:
Nat settings:
Subnet IP: 192.168.174.0
SM: C
GW: 192.168.174.2
DNS settings for the VMNET8 adapter set to "Autodetect available DNS servers"
I dont have internet for my servers. Please help
I have virtual lab running on VMWare workstation 10 and using NAT (VMNet8) (shared host's IP address with VMS) for networking.
Below are the settings:
I installed DNS and DHCP on my servers 2008 R2 and set NAT settings as VMNET8 to use the following:
Nat settings:
Subnet IP: 192.168.174.0
SM: C
GW: 192.168.174.2
DNS settings for the VMNET8 adapter set to "Autodetect available DNS servers"
I dont have internet for my servers. Please help
ASKER
Hi,
I need to be absolutely sure with this Bridge networking that my servers are not touching production environment.....I am running DNS and DHCP on my servers.... Is there possibility that it might affect the existing production network ?
My laptop is connected to the production network (joined to the domain) and I am running VMware workstation 10.
My servers in the test lab are configured with the new domain and new forest name (different from production name). Will it be an issue?
I need to be absolutely sure with this Bridge networking that my servers are not touching production environment.....I am running DNS and DHCP on my servers.... Is there possibility that it might affect the existing production network ?
My laptop is connected to the production network (joined to the domain) and I am running VMware workstation 10.
My servers in the test lab are configured with the new domain and new forest name (different from production name). Will it be an issue?
VMware NAT (VMNet8) is its own DHCP server. If you are also running DHCP in the guest server, you could have a conflict. I think you need to use Bridged Networking here. It just means DHCP is external to the Host Machine.
I would create your own defined network using the Network Editor, and turn OFF VMware DHCP.
This will keep your network isolated.
This will keep your network isolated.
ASKER
Thank you. I do have a network defined in virtual editor called vmnet8 that uses NAT network. VMware dhcp is turned off. I have dhcp running on my DC and DNS server and it is working. It is distributing IPs to machines. I used the scope and range that I indicated in my first post. Not sure where I took this number for gateway..GW: 192.168.174.2
It is not the address of my router. It was suggested in vmware editor.....Am I suppose to be able to connect to internet? My host laptop can access Internet without issues. But it does go through proxy.....I have it set for IE to use our company's proxy. Please advise why vm servers can't connect to the Internet to download updates.
It is not the address of my router. It was suggested in vmware editor.....Am I suppose to be able to connect to internet? My host laptop can access Internet without issues. But it does go through proxy.....I have it set for IE to use our company's proxy. Please advise why vm servers can't connect to the Internet to download updates.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
what is this Cascaded Proxy??
ASKER
THank you Andrew, so seems that that proxy is the issue. Is there a way around it like you said to do Cascaded Proxy?
You would need to install some software or server, in between the upstream proxy and your VMs.
Internet Requests would go to this first proxy, and then send to the second proxy.
Internet Requests would go to this first proxy, and then send to the second proxy.
ASKER
Oh. Thank you so much. What software?
ASKER
Thanks!!!
1. Try Bridged Networking as a test to see if that makes a difference.
2. Go to the VMware Network Editor (Run as Administrator), click on the VMNet8 line, and then click on the button Reset to Default. This resets the internal network components and will change the IP address for VMNet8. Restart the Host computer after this.