Routing Issues

[BShortland]

Right I must be really dim or I am missing something really simple.

Host connected to a router via ethernet which is giving out dhcp. 192.168.1.0/24

VM1: Windows 2008 R2 VM.1st VNIC Bridged onto the NIC connected to the router (192.168.1.0/24).Obtains DHCP address from hardware router) 2nd VNIC connected to internal network(192.168.10.0/24). Internet access fine on this VM.

RRAS installed as NAT onto the the Bridged VNIC.

VM2: Windows 2008 R2. VNIC1 connected to internal network from DHCP from VM1 (192.168.10.0/24). Default Gateway set at 2nd VNIC on VM1 on the internal network.

No internet access on VM2.

Tracert to Internet: Finds default gateway (Internal adapter on VM1) then nothing
Ping Bridged Adapter on VM1: Success
Ping Hardware Router: Fail cannot find

I have looked on blogs etc and allowed for All VMs on the bridged but still nothing.

Could someone please shine a light on this? Its driving me mad.

[BillG]

That should work. Have you rebooted the router vm?

Next thing to try is disable the RRAS config and do it again. Check that you assign the correct NICs as the internal and external interfaces in NAT. Also make sure the default gateway setting on the internal interface is blank.

[BShortland]

The router VM has been rebooted on and I have disabled and reconfigured RRAS setting the Bridged adapter as the external interface with NAT. Default Gateway is left as blank.

Hardware Router 192.168.1.1
Host IP Address 192.168.1.2 (DHCP) (Hardwire)
VM1 Bridged Hardware NIC 192.168.1.10 in VM (VNIC1)
VM1 Internal Network 192.168.10.1 (Static)
VM1 RRAS - NAT to 192.168.1.10

VM2 - Internal Network 192.168.10.2 (DHCP from VM1)

Firewall Exception for icmp v4 packets for ping on both VMs.

I would like to say its the first time I have that this problem...but it isnt. I have had multiple labs and never got it working. When I attempt to activate windows on my Virtual Servers I have to always do it by setting the VNIC to NAT first, activate and then put on the internal network. Unfortunately however in this case however I need internet access on all clients to perform lab tasks with IIS. I don't fancy added another interface on each VM set as NAT just to enable internet access. I have always put it down to Virtualbox not being able to do it, as I have been fine with other Virtual applications.

I prey someone can let me out of this frustration box!

[BShortland]

I managed to sort it finally...
wasn't VirtualBox, RRAS needed additional routing feature for NAT to work which was missing on the "setup the machine like this" step in my lab book.

Sorry for wasting the time of anyone who read or replied to my post.