Question : Routing between virtual and physical LAN under Hyper-V in Windows Server 2008

I need the advice of someone who has experience with Microsoft's virtual servers and routing.

I am working with a pre-release edition of Windows Server Enterprise 2008. The HOST machine has one physical NIC with IP 192.168.0.100 on the 192.168.0.0/24 subnet. Default gateway is 192.168.0.1

I have installed Hyper-V and created a virtual machine running Windows XP Professional. I want to put this machine on a separate subnet (10.99.99.0/24) and allow it to talk to 192.168.0.0 and to the internet (and vice-versa)? I will be running services on and remotely managing the virtual machines, so I need routing rather than NAT.

I have tried creating a virtual External adapter which I bound to a loopback adapter. I set the IP on this to 10.99.99.1 with no gateway. I configured the GUEST machine adapter for 10.99.99.100 and installed RRAS for LAN routing only.

From GUEST I can ping to 10.99.99.1 and to 192.168.0.100, but can't get anywhere else in the 192 subnet or on the internet (although I can resolve internet ip addresses and the DNS server is on the 192 subnet - confusing). I can ping all adapters from HOST. From my own workstation on the 192 subnet, I can ping 192.168.0.100 and 10.99.99.1, but I cant get to the GUEST at 10.99.99.100.

How should I configure the virtual and physical NICs to make this work? Do I need RRAS?

*Internet*
     |
Gateway (192.168.0.1)
     |
HOST physical (192.168.0.100)
HOST virtual (10.99.99.1)
     |
GUEST (10.99.99.100)

Answer : Routing between virtual and physical LAN under Hyper-V in Windows Server 2008

i think you should create an alias on your network card on your host for 10.99.99.1 then connect the virtual machine to the network card not a virtual network. then use the route command in a shell to setup routing.