Windows Vista Forums
Vista Forums Home Join Vista Forums Windows 7 Forum Vista Tutorials Tags
Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks.

Go Back   Vista Forums > Misc Newsgroups > Virtual Server

Vista - Virtual Networking Problems

Reply
 
Old 08-21-2009   #1 (permalink)
Simon Gronow


 
 

Virtual Networking Problems

Hi


I'm trying to setup a Virtual Network with it's own subnet to free up some
of our main subnet's ip's from Virtual Machines.


I have created a Microsoft Local Loopback (without a default g/w) which I
can ping from a workstations, but I can't ping the VM guest machines.

I have changed the network setup of the guest VM's to Virtual Network.


I don't want to use Nat just want the two subnet's to talk.


The Setup

Main Subnet

192.168.1.x
192.168.1.44 Virtual Server (Host)
192.168.1.100 - 200 workstations
192.168.1.254 - adsl router (Default Gateway for all Pc's on this subnet)

Virtual Subnet
192.168.100.x
192.168.100.1 Loopback Nic on the Virtual Server (aka 192.168.1.44)
192.168.100.10 First Virtual PC with a Gateway of 192.168.100.1



From 192.168.1.100 I can ping 192.168.1.44 & 192.168.100.1 no problems
From 192.168.1.44 I can ping 192.168.1.100 & 192.168.100.10 no problems

From 192.168.1.100 I can NOT ping 192.168.100.10
Form 192.168.100.10 I can NOT ping 192.168.1.100



Tried some routing tables from the router for 192.168.100.x to 192.168.1.44
and on the vm's back the other way - no go.

What I have missed to make this work?


One thought I had was do you need to setup Routing and Remote Access Service
on the VM Host?



Thanks

Rgds
Simon.



My System SpecsSystem Spec
Old 08-21-2009   #2 (permalink)
Bill Grant


 
 

Re: Virtual Networking Problems



"Simon Gronow" <srg@newsgroup> wrote in message
news:#o1aYLlIKHA.1340@newsgroup
Quote:

> Hi
>
>
> I'm trying to setup a Virtual Network with it's own subnet to free up some
> of our main subnet's ip's from Virtual Machines.
>
>
> I have created a Microsoft Local Loopback (without a default g/w) which I
> can ping from a workstations, but I can't ping the VM guest machines.
>
> I have changed the network setup of the guest VM's to Virtual Network.
>
>
> I don't want to use Nat just want the two subnet's to talk.
>
>
> The Setup
>
> Main Subnet
>
> 192.168.1.x
> 192.168.1.44 Virtual Server (Host)
> 192.168.1.100 - 200 workstations
> 192.168.1.254 - adsl router (Default Gateway for all Pc's on this subnet)
>
> Virtual Subnet
> 192.168.100.x
> 192.168.100.1 Loopback Nic on the Virtual Server (aka 192.168.1.44)
> 192.168.100.10 First Virtual PC with a Gateway of 192.168.100.1
>
>
>
> From 192.168.1.100 I can ping 192.168.1.44 & 192.168.100.1 no problems
> From 192.168.1.44 I can ping 192.168.1.100 & 192.168.100.10 no problems
>
> From 192.168.1.100 I can NOT ping 192.168.100.10
> Form 192.168.100.10 I can NOT ping 192.168.1.100
>
>
>
> Tried some routing tables from the router for 192.168.100.x to
> 192.168.1.44 and on the vm's back the other way - no go.
>
> What I have missed to make this work?
>
>
> One thought I had was do you need to setup Routing and Remote Access
> Service on the VM Host?
>
>
>
> Thanks
>
> Rgds
> Simon.
>
>
The problem has nothing to do with virtual machines or virtual networks.
You cannot get from one IP subnet to another without an IP router.

If your vms are in the virtual network linked to the loopback adapter,
you would need to enable IP routing or the host to route between the
physical network and the virtual network. The vms would need to use the
loopback adapter as their default gateway and the physical machines would
need to use the host's physical NIC as their dg.

If the LAN machines use some other router as their dg, you will need some
static routing to make it work. Here is an example of each case.

If both networks can use the router as a default gateway, everything works
without static routes. All you need to do is enable IP routing.

eg 192.168.1 x dg 192.168.1.1
|
192.168.1.1 dg blank
router
192.168.100.1 dg blank
|
192.168.100.x dg 192.168.100.1

If the 192.168.1 subnet uses some other gateway, you need extra
routing to get the traffic to the new router. This route needs to be on your
Internet router, not the new one.

Internet
|
ADSL
192.168.1.254
|
192.168.1.x dg 192.168.1.254
|
192.168.1.n dg 192.168.1.254 host
host router
192.168.100.1 dg blank (loopback adapter)
|
192.168.100.x dg 192.168.100.1

If you configure it as a NAT router, it will work without static
routes. If you configure it as a LAN router, you need the extra routing on
the adsl router to get the traffic to the second router. eg 192.168.100.0
255.255.255.0 192.168.1.n

Personally I would not do it that way. I like to keep the host out of the
routing setup. I would put the vms in a private network and use a vm as the
router. The routing is essentially the same but you install RRAS in a vm,
not on the host.



My System SpecsSystem Spec
Old 08-24-2009   #3 (permalink)
Simon Gronow


 
 

Re: Virtual Networking Problems

Hi Bill,

All sorted thanks for your help.




"Bill Grant" <not.available@newsgroup> wrote in message
news:%23EetnNtIKHA.1488@newsgroup
Quote:

>
>
> "Simon Gronow" <srg@newsgroup> wrote in message
> news:#o1aYLlIKHA.1340@newsgroup
Quote:

>> Hi
>>
>>
>> I'm trying to setup a Virtual Network with it's own subnet to free up
>> some of our main subnet's ip's from Virtual Machines.
>>
>>
>> I have created a Microsoft Local Loopback (without a default g/w) which I
>> can ping from a workstations, but I can't ping the VM guest machines.
>>
>> I have changed the network setup of the guest VM's to Virtual Network.
>>
>>
>> I don't want to use Nat just want the two subnet's to talk.
>>
>>
>> The Setup
>>
>> Main Subnet
>>
>> 192.168.1.x
>> 192.168.1.44 Virtual Server (Host)
>> 192.168.1.100 - 200 workstations
>> 192.168.1.254 - adsl router (Default Gateway for all Pc's on this subnet)
>>
>> Virtual Subnet
>> 192.168.100.x
>> 192.168.100.1 Loopback Nic on the Virtual Server (aka 192.168.1.44)
>> 192.168.100.10 First Virtual PC with a Gateway of 192.168.100.1
>>
>>
>>
>> From 192.168.1.100 I can ping 192.168.1.44 & 192.168.100.1 no problems
>> From 192.168.1.44 I can ping 192.168.1.100 & 192.168.100.10 no problems
>>
>> From 192.168.1.100 I can NOT ping 192.168.100.10
>> Form 192.168.100.10 I can NOT ping 192.168.1.100
>>
>>
>>
>> Tried some routing tables from the router for 192.168.100.x to
>> 192.168.1.44 and on the vm's back the other way - no go.
>>
>> What I have missed to make this work?
>>
>>
>> One thought I had was do you need to setup Routing and Remote Access
>> Service on the VM Host?
>>
>>
>>
>> Thanks
>>
>> Rgds
>> Simon.
>>
>>
>
> The problem has nothing to do with virtual machines or virtual networks.
> You cannot get from one IP subnet to another without an IP router.
>
> If your vms are in the virtual network linked to the loopback adapter,
> you would need to enable IP routing or the host to route between the
> physical network and the virtual network. The vms would need to use the
> loopback adapter as their default gateway and the physical machines would
> need to use the host's physical NIC as their dg.
>
> If the LAN machines use some other router as their dg, you will need
> some static routing to make it work. Here is an example of each case.
>
> If both networks can use the router as a default gateway, everything
> works without static routes. All you need to do is enable IP routing.
>
> eg 192.168.1 x dg 192.168.1.1
> |
> 192.168.1.1 dg blank
> router
> 192.168.100.1 dg blank
> |
> 192.168.100.x dg 192.168.100.1
>
> If the 192.168.1 subnet uses some other gateway, you need extra
> routing to get the traffic to the new router. This route needs to be on
> your Internet router, not the new one.
>
> Internet
> |
> ADSL
> 192.168.1.254
> |
> 192.168.1.x dg 192.168.1.254
> |
> 192.168.1.n dg 192.168.1.254 host
> host router
> 192.168.100.1 dg blank (loopback adapter)
> |
> 192.168.100.x dg 192.168.100.1
>
> If you configure it as a NAT router, it will work without static
> routes. If you configure it as a LAN router, you need the extra routing on
> the adsl router to get the traffic to the second router. eg
> 192.168.100.0 255.255.255.0 192.168.1.n
>
> Personally I would not do it that way. I like to keep the host out of the
> routing setup. I would put the vms in a private network and use a vm as
> the router. The routing is essentially the same but you install RRAS in a
> vm, not on the host.
>
>
>

My System SpecsSystem Spec
Old 08-24-2009   #4 (permalink)
Bill Grant


 
 

Re: Virtual Networking Problems

Fine. Didn't realise that you were another Aussie!

"Simon Gronow" <srg@newsgroup> wrote in message
news:uNwZ3KJJKHA.3928@newsgroup
Quote:

> Hi Bill,
>
> All sorted thanks for your help.
>
>
>
>
> "Bill Grant" <not.available@newsgroup> wrote in message
> news:%23EetnNtIKHA.1488@newsgroup
Quote:

>>
>>
>> "Simon Gronow" <srg@newsgroup> wrote in message
>> news:#o1aYLlIKHA.1340@newsgroup
Quote:

>>> Hi
>>>
>>>
>>> I'm trying to setup a Virtual Network with it's own subnet to free up
>>> some of our main subnet's ip's from Virtual Machines.
>>>
>>>
>>> I have created a Microsoft Local Loopback (without a default g/w) which
>>> I can ping from a workstations, but I can't ping the VM guest machines.
>>>
>>> I have changed the network setup of the guest VM's to Virtual Network.
>>>
>>>
>>> I don't want to use Nat just want the two subnet's to talk.
>>>
>>>
>>> The Setup
>>>
>>> Main Subnet
>>>
>>> 192.168.1.x
>>> 192.168.1.44 Virtual Server (Host)
>>> 192.168.1.100 - 200 workstations
>>> 192.168.1.254 - adsl router (Default Gateway for all Pc's on this
>>> subnet)
>>>
>>> Virtual Subnet
>>> 192.168.100.x
>>> 192.168.100.1 Loopback Nic on the Virtual Server (aka 192.168.1.44)
>>> 192.168.100.10 First Virtual PC with a Gateway of 192.168.100.1
>>>
>>>
>>>
>>> From 192.168.1.100 I can ping 192.168.1.44 & 192.168.100.1 no problems
>>> From 192.168.1.44 I can ping 192.168.1.100 & 192.168.100.10 no problems
>>>
>>> From 192.168.1.100 I can NOT ping 192.168.100.10
>>> Form 192.168.100.10 I can NOT ping 192.168.1.100
>>>
>>>
>>>
>>> Tried some routing tables from the router for 192.168.100.x to
>>> 192.168.1.44 and on the vm's back the other way - no go.
>>>
>>> What I have missed to make this work?
>>>
>>>
>>> One thought I had was do you need to setup Routing and Remote Access
>>> Service on the VM Host?
>>>
>>>
>>>
>>> Thanks
>>>
>>> Rgds
>>> Simon.
>>>
>>>
>>
>> The problem has nothing to do with virtual machines or virtual
>> networks. You cannot get from one IP subnet to another without an IP
>> router.
>>
>> If your vms are in the virtual network linked to the loopback adapter,
>> you would need to enable IP routing or the host to route between the
>> physical network and the virtual network. The vms would need to use the
>> loopback adapter as their default gateway and the physical machines would
>> need to use the host's physical NIC as their dg.
>>
>> If the LAN machines use some other router as their dg, you will need
>> some static routing to make it work. Here is an example of each case.
>>
>> If both networks can use the router as a default gateway, everything
>> works without static routes. All you need to do is enable IP routing.
>>
>> eg 192.168.1 x dg 192.168.1.1
>> |
>> 192.168.1.1 dg blank
>> router
>> 192.168.100.1 dg blank
>> |
>> 192.168.100.x dg 192.168.100.1
>>
>> If the 192.168.1 subnet uses some other gateway, you need extra
>> routing to get the traffic to the new router. This route needs to be on
>> your Internet router, not the new one.
>>
>> Internet
>> |
>> ADSL
>> 192.168.1.254
>> |
>> 192.168.1.x dg 192.168.1.254
>> |
>> 192.168.1.n dg 192.168.1.254 host
>> host router
>> 192.168.100.1 dg blank (loopback adapter)
>> |
>> 192.168.100.x dg 192.168.100.1
>>
>> If you configure it as a NAT router, it will work without static
>> routes. If you configure it as a LAN router, you need the extra routing
>> on the adsl router to get the traffic to the second router. eg
>> 192.168.100.0 255.255.255.0 192.168.1.n
>>
>> Personally I would not do it that way. I like to keep the host out of
>> the routing setup. I would put the vms in a private network and use a vm
>> as the router. The routing is essentially the same but you install RRAS
>> in a vm, not on the host.
>>
>>
>>
>
>
My System SpecsSystem Spec
Reply

Thread Tools


Similar Threads
Thread Forum
Perplexed about networking 2 Virtual Machines in VPC2007 Virtual PC
Virtual Server Networking Virtual PC
Virtual PC networking questions Virtual Server
Networking in Virtual PC Virtual PC
Vista Ultimate and Virtual PC 2007 networking Vista General


Vista Forums is an independent web site and has not been authorized,
sponsored, or otherwise approved by Microsoft Corporation.
"Windows Vista", the Start Orb, and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46