Internal network with Internet access

[ioann.sys]

Good day!

On the host (Windows 7 Pro SP1, Core i5 / 8GB RAM / 1 Ethernet adapter), installed VirtualBox 4.3.14. Created two virtual machines:
1. Windows Server 2012 R2 (AD / DNS / DHCP); has two network adapters:
LAN - 192.168.10.1 - adapter mode internal network (intnet);
WAN - 172.24.xxx.xxx - adapter mode network bridge with nat. Host adapter;

2. Debian GNU / Linux 8 (jessie); has only one network adapter:
eth0 - 192.168.10.10 - adapter mode internal network (intnet). This IP-address, the machine receives from Windows Server 2012R2.

Two virtual machines in a virtual network can see each other. Ie ping 192.168.10.1 and ping 192.168.10.10 on both systems are working properly. But with the second-machines (Debian), it is impossible to access the Internet, though, if ping mail.ru, permitted DNS name, but do not pass packets.

Sorry for my bad English (Google translate)

[mpack]

"internal network" means no internet access, by definition.

If you are asking why VM2 can't use VM1's internet access... you would have to configure a network bridge yourself to do that (not to be confused with bridged networking provided by VirtualBox). Merely adding a second NIC to VM1 won't extend the first network. You'd have to configure a gateway, router, proxy server - something of that nature.

This really isn't a VirtualBox issue. It's exactly the same as if you had two physical PCs: PC-A has wireless access to a router and an unused Ethernet port, and PC-B has an Ethernet port and no wireless. You hook an ethernet cable between the two PCs. Does PC-B now have internet access? Certainly not! There are two networks involved, and PC-B is still on the wrong one.

I'm curious why you didn't just add a WAN bridge to VM2 as well.

[ioann.sys]

Solved the problem as follows:
On the Virtual Server 2012 R2 (VM1) added as a router and set it as a NAT. Now it works

Thank you very much!

[mpack]

I assume you mean NAT network, rather than the original NAT feature. NAT network is a relatively new feature that I haven't tried yet - I don't normally run more than one VM at a time.