I have Windows Server 2003 installed in a VMware Workstation 8 virtual machine. I need this to learn and practice how to use the Active Directory. I also set up 3 Windows XP workstations connect to it, meaning that they can communicate with the Server 2003. What is missing is the Internet connection on all of them. When I run ping 8.8.8.8 in either of these VMs I get, "Destination host unreachable."
What I am not sure about, is whether the issue comes from the settings in Windows or from the settings in the VM.
Can someone help me out?
Thank you, guys. I was eventually able to set it up. It was quite an ordeal to deal with IPs and virtual networks. Here's how I did it (in screenshots) in case someone else needs it.
(I also admit that it may be one of many ways to set it up. Maybe there's an easier way to do it with DHCP...)
1. In your actual computer where VMware Workstation 8 is set up start the "Virtual Network Editor." It is located in the folder where VMware Workstation is installed. And set up the following network (VMnet2 in my case):
2. Then in VMware Workstation itself in the VM where Windows Server 2003 is installed set up two network connections as such:
This one is for the outside access to the Internet:
And this one for the intranet AD communications:
3. Then in the VM for Windows Server 2003 set up the following for both network adapters:
For the Internet access:
Then you will need to allow that connection to be shared:
And then for the AD access to workstations (make sure that the static IP is in the range specified in the Virtual Network Editor above for the VMnet2 network). I also set up DNS to 127.0.0.1 because I have DNS server installed on this Windows 2003:
4. From the Windows 2003 VM try to ping 8.8.8.8. It should work now.
5. Switch to each workstation, in my case Windows XP, each in its own VM, and set up the network in the VMware Workstation as follows:
6. Then in the VM set up network connection for Windows XP workstation. Keep in mind to assign a new static IP address for each workstation, that doesn't coinside with the domain's IP (this IP must be from the range specified in the Virtual Network Editor above for the VMnet2 network):
7. Try first to ping the domain, in my case ping 192.168.237.128. And then Internet, ping 8.8.8.8. Both should work!
Keep going with steps [5-7].
First , in your VM machines , make sure that they have Network Cards installed successfully.
Second , in your VM settings from outside in Vmware , make sure that all VMs are bridged to your host.
They can be assigned IPs manually or from DHCP if it exists on the host or from your modem or router.
In this case (Windows 2003 AD + clients) I'd suggest you configure "NAT" networking in the VM's settings and assign static IP addresses (unless you want to configure DHCP on the virtual DC) from within the NAT (VMnet8) range.
Static IP Addresses: 192.168.xxx.3...127
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.xxx.2
For the Clients set the DNS Server address to the DC's IP address and for the DC set it to 127.0.0.1 (the default). To be able to resolve Internet URLs, you need to configure DNS forwarding for other domains than the own one in the DC's DNS server configuration. The IP address to forward DNS queries should be 192.168.xxx.2
André
Thank you, guys. I was eventually able to set it up. It was quite an ordeal to deal with IPs and virtual networks. Here's how I did it (in screenshots) in case someone else needs it.
(I also admit that it may be one of many ways to set it up. Maybe there's an easier way to do it with DHCP...)
1. In your actual computer where VMware Workstation 8 is set up start the "Virtual Network Editor." It is located in the folder where VMware Workstation is installed. And set up the following network (VMnet2 in my case):
2. Then in VMware Workstation itself in the VM where Windows Server 2003 is installed set up two network connections as such:
This one is for the outside access to the Internet:
And this one for the intranet AD communications:
3. Then in the VM for Windows Server 2003 set up the following for both network adapters:
For the Internet access:
Then you will need to allow that connection to be shared:
And then for the AD access to workstations (make sure that the static IP is in the range specified in the Virtual Network Editor above for the VMnet2 network). I also set up DNS to 127.0.0.1 because I have DNS server installed on this Windows 2003:
4. From the Windows 2003 VM try to ping 8.8.8.8. It should work now.
5. Switch to each workstation, in my case Windows XP, each in its own VM, and set up the network in the VMware Workstation as follows:
6. Then in the VM set up network connection for Windows XP workstation. Keep in mind to assign a new static IP address for each workstation, that doesn't coinside with the domain's IP (this IP must be from the range specified in the Virtual Network Editor above for the VMnet2 network):
7. Try first to ping the domain, in my case ping 192.168.237.128. And then Internet, ping 8.8.8.8. Both should work!
Keep going with steps [5-7].
Hey friend, you can refer to a tutorial here, it have a three way for VmWare Workstation connect Internet (Brigde, NAT and Host Only) https://www.youtube.com/watch?v=aX7BqeBGTY8
there can be a number of reasons why the networking might stop working in VMware Workstation. Validate each of these troubleshooting steps to verify if it is true for your environment. Each step provides instructions or a link to a document to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.
After each numbered step, check whether your virtual machine has an Internet connection. There is no need to proceed with further steps once the issue is resolved.
To troubleshoot your network and Internet connection:
Warning: Turning off your firewall can leave your computer open to attack. This is a troubleshooting step only. If turning off the firewall resolves the issue, consult the operating system's documentation for instructions to configure it properly so that it does not completely block this connection.
If your problem continues to exist after performing the steps in this article, please file a support request: