Packet Loss Problems with Windows 2012R2 guests in NAT Netw

[Spille]

I did Setup a System of two guests running Windows Server 2012R2. One core for AD Services and a Standard Server containing a SharePoint 2013 Installation. Both are Setup in a NAT Network 10.0.2.0 with 10.0.2.1 the Gateway and 10.0.2.10/11 the guests. No DHCP is active. DNS Forwardes on the AD machine are Setup to DNS Servers in HOST Network.

The host is a Windows 7 System with 16GB ram, Core I7, 2720QM Intel processor running current virtualbox Version. AD machine has 512M RAM, SharePoint machine has 10GB RAM.

On both guest machines there are issues with the NAT Network. It works most of the time but sometimes there are packet losses for a greater time. This example is possibly bad. Sometimes the Phase of packet loss is not only seconds but 1-2 minutes.

Memory usage on the host is about 12GB, CPU load about 20%. Is this a known issue?

I´ve also running a SharePoint 2010 VM NAT only (not NAT Network). I did not experience similar Problems with this machine.

Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time=3ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time=2ms TTL=127
Request timed out.
Request timed out.
Reply from 10.0.2.11: Destination host unreachable.
Reply from 10.0.2.11: Destination host unreachable.
Reply from 10.0.2.11: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.2.11: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time=1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127
Reply from 172.20.103.49: bytes=32 time<1ms TTL=127

[mpack]

Ping testing is not reliable when you use NAT. Check the user manual.