virtualbox.org

I have a server 2012 (who is domain controller) with host-only adapter. The server has a static adres 192.168.101.20/24.
The host-only dhcp-server is disabled.
There is also a windows 8 workstation dhcp client with host-only adapter. The connection between the workstation and the server works.
The host-only adapter on the server is called adapter internetconnectie in control panel/network/adapter.
I want internet connection on the server. I have a home router connected to my host laptop connected with wifi therefore
I added the nat adapter as second network adapter to the server.
When I boot I get a static address 192.168.101.11 Therefor I've changed static to dhcp for the nat adapter (which is called
lan adapter).After booting the problem is that the received? dns server is 127.0.0.1
I can ping to the internet ip adress but not to the domain name.
(on my laptop I have dhcp dns connection)

I've added ipconfig /all after the last boot.

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : PFSV1
Primary Dns Suffix . . . . . . . : PoliForma.nl
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : PoliForma.nl
telenet.be

Ethernet adapter LanConnectie:

Connection-specific DNS Suffix . : telenet.be
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
Physical Address. . . . . . . . . : 08-00-27-03-7F-D8
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.0.3.15(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : zaterdag 4 oktober 2014 16:56:05
Lease Expires . . . . . . . . . . : zondag 5 oktober 2014 16:56:05
Default Gateway . . . . . . . . . : 10.0.3.2
DHCP Server . . . . . . . . . . . : 10.0.3.2
DNS Servers . . . . . . . . . . . : 127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter InternetConnectie:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Desktop Adapter
Physical Address. . . . . . . . . : 08-00-27-AE-06-2B
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.101.20(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.101.1
DNS Servers . . . . . . . . . . . : 192.168.101.20
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{AB356F5C-5958-44DF-AE7E-0FDA4D60CD75}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.telenet.be:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : telenet.be
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\Administrator>

Running a Windows domain with Internet access is a tricky business, because of the way Active Directory uses DNS. Your problem has more to do with that than with VirtualBox. It has been discussed at length in both the Windows forums and here.

I would not attempt this using host only adapters. The best solution is to run your domain on an internal virtual network and use a vm as a router between this network and your physical LAN. In fact I would recommend that you get your domain set up and running on the internal network (without Internet access), then configure the router and modify the DNS.

Thanks for your reply BillG.
I suppose when I follow your proposal with the router and the DNS modifications then the windows 8 dhcp domain clients have also internet access as they use the DC as default gw and DNS server.

Indeed they will if you configure the router and the DNS properly, but that really is not a VirtualBox matter: it would be just the same with physical machines.