Abraham Deutsch
asked on
change network setting to create in VMware a network
I am setting a small lab for practice purposes. I created in VMware a server and a few computers. Now I want the computers to join the DNS server in order to do this I believe I need to change the network adapter settings on the virtual machines. Can someone guide me thru the process (without losing internet on the virtual machines?
ASKER
Currently the virtual machines uses the host machine (which is a window 7) to access the internet.
and what do you want to change ?
What VMware software are you using ?
What network configuration, are your VMs using 0- NAT, Bridged or Host only ?
What VMware software are you using ?
What network configuration, are your VMs using 0- NAT, Bridged or Host only ?
ASKER
The machines should join the gust server
VMware workstation 12 palyer
Net
VMware workstation 12 palyer
Net
ASKER
Sorry Guest
Okay, so you have some virtual machines guest, hosted using VMware Workstation 12, on a Windows 7 Host.
What is the networking -
1.NAT
2. BRIDGED
3. HOST ONLY
"join" the guest server in what ?
Computers do not join to DNS, Windows computers, can join a Domain, rather than a workgroup.
What is the networking -
1.NAT
2. BRIDGED
3. HOST ONLY
"join" the guest server in what ?
Computers do not join to DNS, Windows computers, can join a Domain, rather than a workgroup.
ASKER
NAT
Correct I want them to Join the Guest server domain. (sorry for my wrong description)
Correct I want them to Join the Guest server domain. (sorry for my wrong description)
Okay, so I assume there is a Domain Controller on the LAN, which the Windows 7 Host is a member of?
You will need to change the network settings of ALL VMs, to BRIDGED.
There will then be on the same LAN as the Host (Windows 7 Host) and Domain Controller, and will get IP Addresses from your DHCP server if you have one.
They Add to Domain as you would a physical computer.
You will need to change the network settings of ALL VMs, to BRIDGED.
There will then be on the same LAN as the Host (Windows 7 Host) and Domain Controller, and will get IP Addresses from your DHCP server if you have one.
They Add to Domain as you would a physical computer.
ASKER
No the window 7 is not part of a domain. its just a laptop getting internet from a hot spot.
What I am trying to accomplish, the guest Vserver should be the Domain controller for the guest Vmachines.
What I am trying to accomplish, the guest Vserver should be the Domain controller for the guest Vmachines.
You will need to install a server, which can have a role as a Domain Controller.
Windows 7 cannot be uses as a Domain Controller.
You will need to install Windows Server 2012 R2, and add he Active Directory Role.
Windows 7 cannot be uses as a Domain Controller.
You will need to install Windows Server 2012 R2, and add he Active Directory Role.
ASKER
I already installed a Vserver and added active directory. now I am trying to figure out how to join the Vmachines to the Vserver domain. thank you so much for your patience guiding me.
okay, first ALL VMs, must be set to bridged.
What server did you install ?
did you install the AD Role and DNS ?
what IP Address is the Domain Controller ?
what IP Addresses are you VMs ?
Normally, you would select Add to Domain, when you select This PC or Computer, but ALL your VMs must be in bridged mode, and must have the IP Address of the DNS Server/Domain Controller as their DNS.
What server did you install ?
did you install the AD Role and DNS ?
what IP Address is the Domain Controller ?
what IP Addresses are you VMs ?
Normally, you would select Add to Domain, when you select This PC or Computer, but ALL your VMs must be in bridged mode, and must have the IP Address of the DNS Server/Domain Controller as their DNS.
I get the impression your setup is as follows
Host Machine Windows 7
Guest 1 Windows Server with Active Directory Roles
Guest 2-x Windows Client machines
you have the guests using NAT host machine 192.168.1.xx doesn't matter
Guests in network 192.168.2.x again doesn't matter but the gateway will be the ip of the host machine
So if the ip address of vServer is 192.168.2.10 server dns settings in network adapter 192.168.2.10 and 127.0.0.1
you need to set the network adapter in the clients to not get dns automatically but from 192.168.2.10
Host Machine Windows 7
Guest 1 Windows Server with Active Directory Roles
Guest 2-x Windows Client machines
you have the guests using NAT host machine 192.168.1.xx doesn't matter
Guests in network 192.168.2.x again doesn't matter but the gateway will be the ip of the host machine
So if the ip address of vServer is 192.168.2.10 server dns settings in network adapter 192.168.2.10 and 127.0.0.1
you need to set the network adapter in the clients to not get dns automatically but from 192.168.2.10
ASKER
If I understand correctly what you are saying is to set the server in net mode not in bridge that Andrew recommended?
ASKER
lets work with the Active Directory server at present, and no Internet, we can resolve that later.
leave the vServer VM set to Bridged.
and set all the VMs to bridged.
You then need to ensure that all the VMs, have an IP Address, and DNS Name of he Vserver in their settings.
then add them to domain.
leave the vServer VM set to Bridged.
and set all the VMs to bridged.
You then need to ensure that all the VMs, have an IP Address, and DNS Name of he Vserver in their settings.
then add them to domain.
Yes, Bridged is correct.
now allocate the same IP address range to other VMs, and make them bridged, and then ensure, they can ping each other.
now allocate the same IP address range to other VMs, and make them bridged, and then ensure, they can ping each other.
so your dns server is 192.168.16.2 setup a reservation in your dhcp or make that address static
on your clients set the preferred dns set it to 192.168.16.2
Without a gateway you can't access outside of your subnet
on your clients set the preferred dns set it to 192.168.16.2
Without a gateway you can't access outside of your subnet
ASKER
your DNS values are incorrect.
8.8.8.8 is Google no your Active Directory Domain Controller.
127.0.0.1 is also not your Active Directory Domain Controller.
On your clients, that you want to join to a domain, you must put the IP Address of the DNS Server, e.g. Domain Controller, as the DNS server.
that is 192.168.16.2
I would not use a google IP Address 8.8.8.8 in your DNS settings, it will upset AD.
When we get your VMs domain joined and working, we can then sort out the Internet Access.
Don't try to run before you can walk!
8.8.8.8 is Google no your Active Directory Domain Controller.
127.0.0.1 is also not your Active Directory Domain Controller.
On your clients, that you want to join to a domain, you must put the IP Address of the DNS Server, e.g. Domain Controller, as the DNS server.
that is 192.168.16.2
I would not use a google IP Address 8.8.8.8 in your DNS settings, it will upset AD.
When we get your VMs domain joined and working, we can then sort out the Internet Access.
Don't try to run before you can walk!
ASKER
Try a ping using fqdn to the domain controller.
ASKER
I changed the network setting to net. It WORKS. it successfully joined the domain.
Now what about getting internet.
Now what about getting internet.
ASKER
David, whey do I also need the 127.0.0.1 it works fine without it?
ASKER
David I worked days to figure this out, and you gave the perfect solution with your first shot. I was written a little in short so it took me time to follow. thank you. but do you know why I don't have internet on the Vserver Vmachine?
okay, so you are domain joined.... so do you have internet now ?
ASKER
No
So the solution you have selected is not complete ?
ASKER
Correct
All domain computers should only have the local dns server in their dns server entries.
The domain controller should have (from my experience) in the dns application have forwarders set rather than just use root hints i.e. 8.8.8.8/8.8.4.4/208.67.222 .222/208.6 7.220.220 Use dnstest from grc.com and use the fastest ones for your area. do not rely on your isp's domain controllers for dns as they are notoriously unreliable and not maintained.
if you are using bridged networking the gateway should be the same as the rest of your network. (usually the routers address)
The domain controller should have (from my experience) in the dns application have forwarders set rather than just use root hints i.e. 8.8.8.8/8.8.4.4/208.67.222
if you are using bridged networking the gateway should be the same as the rest of your network. (usually the routers address)
if you get a 169.254.xxx.xxx address then you are using an apipa address automatically assigned by the operating system.. This means (a) not static address and (b) did not get an address via dhcp. you need to fix this and to get outside of your subnet you need a gateway address
If the client is unable to find the information, it uses APIPA to automatically configure itself with an IP address from a range that has been reserved especially for Microsoft. The IP address range is 169.254.0.1 through 169.254.255.254. The client also configures itself with a default class B subnet mask of 255.255.0.0. A client uses the self-configured IP address until a DHCP server becomes available.
http://www.webopedia.com/TERM/A/APIPA.html
If the client is unable to find the information, it uses APIPA to automatically configure itself with an IP address from a range that has been reserved especially for Microsoft. The IP address range is 169.254.0.1 through 169.254.255.254. The client also configures itself with a default class B subnet mask of 255.255.0.0. A client uses the self-configured IP address until a DHCP server becomes available.
http://www.webopedia.com/TERM/A/APIPA.html
ASKER
ASKER
Andrew, the header of my question is "change network setting to "create" in VMware a network" with David solution I "have" a network now if I have a issue with the network I would not say I don't have a network, its is a network even without internet, rather I consider it as a issue, and maybe grade the solution for a B. therefore I marked his solution as accepted solution. agree?
ASKER
You made it clear in your Question description,
if you are happy with the solution accepted that's fine, Question Closed then.
Can someone guide me thru the process (without losing internet on the virtual machines?
if you are happy with the solution accepted that's fine, Question Closed then.
it still isn't working properly since one of the requirements was have internet on the virtual machines. This in all likelihood is a configuration problem on the lab dns server. as a quick test can you ping 8.8.8.8 or do a tracert 8.8.8.8 and also a nslookup google.com please share the results.
as mentioned previously you require a gateway to get outside of your network.
Bridged network the gateway would typically be your routers address.
NAT (not NET) [one letter means a big difference] it would be the NAT ip address (vmware player)
Bridged network the gateway would typically be your routers address.
NAT (not NET) [one letter means a big difference] it would be the NAT ip address (vmware player)
ASKER
Andrew. You are right I did mention internet in my question. And Thank you for making me aware. Thank you David for reopening the question. I will try your solution and update you. Thank you all again.
ASKER
Sorry David but if you don't mind please explain me again what to do it order to get internet.
in the running operating system network settings or the result from ipconfig you will see the ip adress, netmask, and gateway.
i.e. 192.168.0.20 255.255.255.0 192.168.1.1 Addresses 192.168.0.0-255 will be considered in your local area network ip addresses out side of that range will be sent to 192.168.1.1 (the gateway) and then sent onward.. the gateway in a bridged network usually is your routers ip address in a NAT network it will be the host machines ip address
i.e. 192.168.0.20 255.255.255.0 192.168.1.1 Addresses 192.168.0.0-255 will be considered in your local area network ip addresses out side of that range will be sent to 192.168.1.1 (the gateway) and then sent onward.. the gateway in a bridged network usually is your routers ip address in a NAT network it will be the host machines ip address
vserver gateway should be the same as for the host 192.168.1.1
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
In few minuets you can have a domain up in running with internet. just leave all setting at its default accept the server as explained in my answer.
If you already have Internet Access, you virtual machines, must already be setup with a DNS server, otherwise, they would not know how to resolve DNS queries for Internet DNS names.