> I've installed one Guest and gone through the process of installing
> RRAS on the host, setting up routes in RRAS and at this point I am
> able to get from the guest machine to the external network. I can
> contact any machines on my physical network, get to the internet,
> basically everything from the vm outward.
> On the host I can ping the guest vm, and have no trouble there. From
> another machine on the physical network, though, I can't reach the
> guest vm. I set up a local route on my workstation pointing to the vm
> network, but get Request timed out.
> Setup is like so:
>
> Physical network is 192.168.1.0, mask 255.255.255.0, gateway
> 192.168.1.1 Host machine is 192.168.1.24
> VM network is 192.168.5.0, mask 255.255.255.0, gateway is 192.168.5.1.
> VM guest is 192.168.5.2, gateway set to 192.168.5.1
>
> This looks to me like it's a problem with the route on my physical
> network, that my workstation isn't able to find the 192.168.5.0
> network. I'd be grateful for any hints or pointers.
> Thanks
> Bob Grabbe
> (email address - cut out)

> That is pretty much what always happens with multiple routers. You
> can't use default routing to get you both ways through a multi-router
> network.
>
> If you want the machines in the physical network to see the machines in
> the virtual network, you need to modify the routing in the physical
> network. You can't make any changes at the RRAS router to do this because
> that isn't where the problem lies.
>
> I am not too sure why you were setting up local routes. You shouldn't
> need any of those.
>
> All you need to do on the RRAS router is enable IP routing. The probelm
> you describe indicates that you have configured it as a NAT router. This
> solves the routing problem to the Internet but blocks access from the
> physical LAN (because the machines on the physical LAN are on the "public"
> side of the NAT).
>
> To be able to access the virtual network from the physical network you
> must use normal IP routing on the RRAS server. To solve the routing
> problem you must add routing info to the router at 192.168.1.1 so that it
> knows how to reach the virtual network 192.168.5.0 (via the RRAS router).
> Here is a diagram of the setup.
>
> Internet
> |
> gateway
> 192.168.1.1
> |
> client machines
> 192.168.1.x dg 192.168.1.1
> |
> 192.168.1.24 dg 192.168.1.1
> RRAS
> 192.168.5.1 dg blank
> |
> client vms
> 192.168.5.x dg 192.168.5.1
>
> The only route you need to add is to the router at 192.168.1.1 . The
> route it needs is
>
> 192.168.5.0 255.255.255.0 192.168.1.24
>
> Traffic from the vms goes to the RRAS router by default. Traffic for
> the physical LAN is delivered directly, everything else continues to the
> router at 192.168.1.1 by default.
>
> Traffic from the machines on the physical LAN goes to the router at
> 192.168.1.1 . Traffic for 192.168.5.0 is bounced to the RRAS router and
> delivered directly. The rest continues to the Internet.
>
> Bob Grabbe wrote:
>> I've installed one Guest and gone through the process of installing
>> RRAS on the host, setting up routes in RRAS and at this point I am
>> able to get from the guest machine to the external network. I can
>> contact any machines on my physical network, get to the internet,
>> basically everything from the vm outward.
>> On the host I can ping the guest vm, and have no trouble there. From
>> another machine on the physical network, though, I can't reach the
>> guest vm. I set up a local route on my workstation pointing to the vm
>> network, but get Request timed out.
>> Setup is like so:
>>
>> Physical network is 192.168.1.0, mask 255.255.255.0, gateway
>> 192.168.1.1 Host machine is 192.168.1.24
>> VM network is 192.168.5.0, mask 255.255.255.0, gateway is 192.168.5.1.
>> VM guest is 192.168.5.2, gateway set to 192.168.5.1
>>
>> This looks to me like it's a problem with the route on my physical
>> network, that my workstation isn't able to find the 192.168.5.0
>> network. I'd be grateful for any hints or pointers.
>> Thanks
>> Bob Grabbe
>> (email address - cut out)
>
>

> I'm trying something different, that is almost working.
> What I wanted to do is have the VM be able to talk to my physical
> network. Looking through the Admin guide I found somehow a section
> that mentions having the Vm nic connected to either the internal
> network or the external network. I.e., "connecting the VM to the
> external network through the network adapter of the physical
> computer". This seems to be what I wanted, so I created another virtual
> network
> connected to the external physical nic, and set the VM to connect to
> the external virtual network instead of the internal one. With this
> configuration the vm is able to join the domain, I can remote desktop
> to it, etc.
> What I'm wondering is if this setup meeds RRAS on the host. It
> doesn't seem like it would need it, but it also seems like this is
> too easy. My goal was not really to create a separate internal
> network, but to have any VM's I create look like they are on my
> normal physical net.
> FYI, to answer the isues below, the local route was just to try to
> get my workstation to be able to route to the vm. I was trying this
> morning to set up a route on my network router, but had problems with
> it. Thanks for the help.
> Bob Grabbe
> (email address - cut out)
>
> "Bill Grant" <not.available@online> wrote in message
> news:(email address - cut out)...
>> That is pretty much what always happens with multiple routers. You
>> can't use default routing to get you both ways through a multi-router
>> network.
>>
>> If you want the machines in the physical network to see the
>> machines in the virtual network, you need to modify the routing in
>> the physical network. You can't make any changes at the RRAS router
>> to do this because that isn't where the problem lies.
>>
>> I am not too sure why you were setting up local routes. You
>> shouldn't need any of those.
>>
>> All you need to do on the RRAS router is enable IP routing. The
>> probelm you describe indicates that you have configured it as a NAT
>> router. This solves the routing problem to the Internet but blocks
>> access from the physical LAN (because the machines on the physical
>> LAN are on the "public" side of the NAT).
>>
>> To be able to access the virtual network from the physical
>> network you must use normal IP routing on the RRAS server. To solve
>> the routing problem you must add routing info to the router at
>> 192.168.1.1 so that it knows how to reach the virtual network
>> 192.168.5.0 (via the RRAS router). Here is a diagram of the setup.
>>
>> Internet
>> |
>> gateway
>> 192.168.1.1
>> |
>> client machines
>> 192.168.1.x dg 192.168.1.1
>> |
>> 192.168.1.24 dg 192.168.1.1
>> RRAS
>> 192.168.5.1 dg blank
>> |
>> client vms
>> 192.168.5.x dg 192.168.5.1
>>
>> The only route you need to add is to the router at 192.168.1.1 .
>> The route it needs is
>>
>> 192.168.5.0 255.255.255.0 192.168.1.24
>>
>> Traffic from the vms goes to the RRAS router by default. Traffic
>> for the physical LAN is delivered directly, everything else
>> continues to the router at 192.168.1.1 by default.
>>
>> Traffic from the machines on the physical LAN goes to the router
>> at 192.168.1.1 . Traffic for 192.168.5.0 is bounced to the RRAS
>> router and delivered directly. The rest continues to the Internet.
>>
>> Bob Grabbe wrote:
>>> I've installed one Guest and gone through the process of installing
>>> RRAS on the host, setting up routes in RRAS and at this point I am
>>> able to get from the guest machine to the external network. I can
>>> contact any machines on my physical network, get to the internet,
>>> basically everything from the vm outward.
>>> On the host I can ping the guest vm, and have no trouble there. From
>>> another machine on the physical network, though, I can't reach the
>>> guest vm. I set up a local route on my workstation pointing to the
>>> vm network, but get Request timed out.
>>> Setup is like so:
>>>
>>> Physical network is 192.168.1.0, mask 255.255.255.0, gateway
>>> 192.168.1.1 Host machine is 192.168.1.24
>>> VM network is 192.168.5.0, mask 255.255.255.0, gateway is
>>> 192.168.5.1. VM guest is 192.168.5.2, gateway set to 192.168.5.1
>>>
>>> This looks to me like it's a problem with the route on my physical
>>> network, that my workstation isn't able to find the 192.168.5.0
>>> network. I'd be grateful for any hints or pointers.
>>> Thanks
>>> Bob Grabbe
>>> (email address - cut out)

> If you want the vm to look like another machine on the network, then
> that is all you need to do. You set it up so that it is on the network
> linked to the physical NIC in the host. You don't need RRAS and you don't
> need two NICs in the vm.
>
> The vm has its own MAC address and gets its own IP address from DHCP,
> just like any other machine on the LAN.You only need two NICs and RRAS if
> you want to set up a private LAN isolated from the physical LAN. (For
> example, if you want to emulate a private network running its own AD, DNS
> and DHCP)
>
> Bob Grabbe wrote:
>> I'm trying something different, that is almost working.
>> What I wanted to do is have the VM be able to talk to my physical
>> network. Looking through the Admin guide I found somehow a section
>> that mentions having the Vm nic connected to either the internal
>> network or the external network. I.e., "connecting the VM to the
>> external network through the network adapter of the physical
>> computer". This seems to be what I wanted, so I created another virtual
>> network
>> connected to the external physical nic, and set the VM to connect to
>> the external virtual network instead of the internal one. With this
>> configuration the vm is able to join the domain, I can remote desktop
>> to it, etc.
>> What I'm wondering is if this setup meeds RRAS on the host. It
>> doesn't seem like it would need it, but it also seems like this is
>> too easy. My goal was not really to create a separate internal
>> network, but to have any VM's I create look like they are on my
>> normal physical net.
>> FYI, to answer the isues below, the local route was just to try to
>> get my workstation to be able to route to the vm. I was trying this
>> morning to set up a route on my network router, but had problems with
>> it. Thanks for the help.
>> Bob Grabbe
>> (email address - cut out)
>>
>> "Bill Grant" <not.available@online> wrote in message
>> news:(email address - cut out)...
>>> That is pretty much what always happens with multiple routers. You
>>> can't use default routing to get you both ways through a multi-router
>>> network.
>>>
>>> If you want the machines in the physical network to see the
>>> machines in the virtual network, you need to modify the routing in
>>> the physical network. You can't make any changes at the RRAS router
>>> to do this because that isn't where the problem lies.
>>>
>>> I am not too sure why you were setting up local routes. You
>>> shouldn't need any of those.
>>>
>>> All you need to do on the RRAS router is enable IP routing. The
>>> probelm you describe indicates that you have configured it as a NAT
>>> router. This solves the routing problem to the Internet but blocks
>>> access from the physical LAN (because the machines on the physical
>>> LAN are on the "public" side of the NAT).
>>>
>>> To be able to access the virtual network from the physical
>>> network you must use normal IP routing on the RRAS server. To solve
>>> the routing problem you must add routing info to the router at
>>> 192.168.1.1 so that it knows how to reach the virtual network
>>> 192.168.5.0 (via the RRAS router). Here is a diagram of the setup.
>>>
>>> Internet
>>> |
>>> gateway
>>> 192.168.1.1
>>> |
>>> client machines
>>> 192.168.1.x dg 192.168.1.1
>>> |
>>> 192.168.1.24 dg 192.168.1.1
>>> RRAS
>>> 192.168.5.1 dg blank
>>> |
>>> client vms
>>> 192.168.5.x dg 192.168.5.1
>>>
>>> The only route you need to add is to the router at 192.168.1.1 .
>>> The route it needs is
>>>
>>> 192.168.5.0 255.255.255.0 192.168.1.24
>>>
>>> Traffic from the vms goes to the RRAS router by default. Traffic
>>> for the physical LAN is delivered directly, everything else
>>> continues to the router at 192.168.1.1 by default.
>>>
>>> Traffic from the machines on the physical LAN goes to the router
>>> at 192.168.1.1 . Traffic for 192.168.5.0 is bounced to the RRAS
>>> router and delivered directly. The rest continues to the Internet.
>>>
>>> Bob Grabbe wrote:
>>>> I've installed one Guest and gone through the process of installing
>>>> RRAS on the host, setting up routes in RRAS and at this point I am
>>>> able to get from the guest machine to the external network. I can
>>>> contact any machines on my physical network, get to the internet,
>>>> basically everything from the vm outward.
>>>> On the host I can ping the guest vm, and have no trouble there. From
>>>> another machine on the physical network, though, I can't reach the
>>>> guest vm. I set up a local route on my workstation pointing to the
>>>> vm network, but get Request timed out.
>>>> Setup is like so:
>>>>
>>>> Physical network is 192.168.1.0, mask 255.255.255.0, gateway
>>>> 192.168.1.1 Host machine is 192.168.1.24
>>>> VM network is 192.168.5.0, mask 255.255.255.0, gateway is
>>>> 192.168.5.1. VM guest is 192.168.5.2, gateway set to 192.168.5.1
>>>>
>>>> This looks to me like it's a problem with the route on my physical
>>>> network, that my workstation isn't able to find the 192.168.5.0
>>>> network. I'd be grateful for any hints or pointers.
>>>> Thanks
>>>> Bob Grabbe
>>>> (email address - cut out)
>
>