Hello
I installed a Windows 7 ultimate and a Windows 2008 server. Now I want to connect the client to the server.
But i can't get the Windows 7 in the domain of the server..
A while ago, I did this with loopback adapter, but I can't manage that again. Then i don't used DNS server of the 2008.
On my W7 I have now 2 network connections.. One of them is the loopback adapter.
This are the settings of my server:
ipv4 address: 10.0.2.15
Subnet Mask 255.255.255.0
Default Gateway: 10.0.2.2
Now I want to change the settings of the loopback adapter:
ipv4 address: 10.0.2.31
Subnet mask: 255.255.255.0
Default Gateway: 10.0.2.2
DNS server: 10.0.2.15
But i can't get my client connected with the server. Still problems with DNS server (it says that it has to use 127.0.0.1 or 10.0.2.15 (server). Someone can say what i'm doing wrong?
Windows 7 client on Windows 2008
-
socratis
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Windows 7 client on Windows 2008
You should leave the loopback adapter alone. If you think of the word loopback, it's a dummy interface with IP 127.0.0.1 and it means the computer itself (actual or virtual).
You seem to be using NAT as your network option. NAT's main purpose is to give internet connectivity to a guest through the resources of the host. Only that. Not inter-VM communications. For that, you need the "Internal" network, or the "NAT Network". Please read the first few paragraphs of Chapter 6.2. Introduction to networking modes to see more details. Bear in mind that you can have more than one network card in your VM setup, one for example assigned to NAT and one to Internal.
You seem to be using NAT as your network option. NAT's main purpose is to give internet connectivity to a guest through the resources of the host. Only that. Not inter-VM communications. For that, you need the "Internal" network, or the "NAT Network". Please read the first few paragraphs of Chapter 6.2. Introduction to networking modes to see more details. Bear in mind that you can have more than one network card in your VM setup, one for example assigned to NAT and one to Internal.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
-
Finduilas
- Posts: 8
- Joined: 26. Aug 2014, 21:37
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Windows Server 2008, Windows 7
Re: Windows 7 client on Windows 2008
Thnx for the answer
I have chosen for Internal Network, with intranet as name. I have set in ipv4 everything to automatic.
For the client, it seems not to be a problem. I can ping to the server.
But if i want to ping from the server to the client, it timeout. Also the DNS server gives errors because of the ip.
I have chosen for Internal Network, with intranet as name. I have set in ipv4 everything to automatic.
For the client, it seems not to be a problem. I can ping to the server.
But if i want to ping from the server to the client, it timeout. Also the DNS server gives errors because of the ip.
- Attachments
-
- Schermafbeelding 2014-08-28 om 18.34.32.png (27.36 KiB) Viewed 1568 times
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Windows 7 client on Windows 2008
What exactly are you trying to do here? What is the host OS? What OS is running in the guest(s)?
If you are trying to install a domain controller in a vm and join the host to that domain I would advise you to think again.
Setting up a domain controller and a client in two vms on the internal network works fine.
If you are trying to install a domain controller in a vm and join the host to that domain I would advise you to think again.
Setting up a domain controller and a client in two vms on the internal network works fine.
Bill
-
Finduilas
- Posts: 8
- Joined: 26. Aug 2014, 21:37
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Windows Server 2008, Windows 7
Re: Windows 7 client on Windows 2008
I have OS X 10.9.2.
I'm trying to install a server (Windows 2008) and a client(windows 7) to connect to it. It's just to try things out.
So i'm not trying to connect the host pc to the server, only another VM.
Seems that i only have a problem to put the server now in a network.
I'm trying to install a server (Windows 2008) and a client(windows 7) to connect to it. It's just to try things out.
So i'm not trying to connect the host pc to the server, only another VM.
Seems that i only have a problem to put the server now in a network.
-
Finduilas
- Posts: 8
- Joined: 26. Aug 2014, 21:37
- Primary OS: Mac OS X other
- VBox Version: OSE other
- Guest OSses: Windows Server 2008, Windows 7
Re: Windows 7 client on Windows 2008
After reinstalling the DNS server and doing all the IP settings again, it seems the client is member of the network..
The server had problems with the DNS.
Things who helped me:
http://www.youtube.com/watch?v=K_n58IMdMh8
http://technet.microsoft.com/en-us/libr ... 10%29.aspx
http://technet.microsoft.com/en-us/libr ... 10%29.aspx
The server had problems with the DNS.
Things who helped me:
http://www.youtube.com/watch?v=K_n58IMdMh8
http://technet.microsoft.com/en-us/libr ... 10%29.aspx
http://technet.microsoft.com/en-us/libr ... 10%29.aspx
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Windows 7 client on Windows 2008
Sounds like your problems have nothing to do with VirtualBox. If both server and client are using the internal network the setup is the same as with two physical machines on the same hub/switch. Have you installed DNS in the server? Does the client use the server as its only DNS address (it should).
Bill