ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* PRO ACCESS FLOORS
* Create new volume on Hyper-V Server
* Virtual Disks Trouble
* Hyper-V Server need AV?
* drivers on W2K8 R2 - hyper-v
* Increase dynamic VHD
* Virtual server 2005 or Virtual PC 2007 ?
* Error with VM network adapters.
* Guests OS hang VM Additions 13.820 on VS05 R2 Ent SP1
* Admin Hyper-V Server
* Access VM simultaneously
* cannot access USB devices from Window 2008 VM
* Hyper-V without SAN
* could not see the virtual network adaptor in the Virtual machine
* TFS on Virtual Server 2005 R2
* Virtual Server 2008, need intergrated components?
* Confusing NIC situation
* Hyper-V Network Packet Captures
* Migration from physical host to VM
* Virtual Server 2005 - how to resize (shrink) a fixed vhd file

Add Solution

Virtual Networking Problems

Source: microsoft.public.virtualserver
Sent: 08/21/2009
From: "Simon Gronow" <(email address - cut out)>
Message:

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.

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Virtual Networking Problems

Sent: 08/22/2009
From: "Bill Grant" <not.available@online>
Message:

"Simon Gronow" <(email address - cut out)> wrote in message
news:#(email address - cut out)...

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.

Show quoted text

> 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.
>
>

Re: Virtual Networking Problems

Sent: 08/24/2009
From: "Simon Gronow" <(email address - cut out)>
Message:

Hi Bill,

All sorted thanks for your help.

"Bill Grant" <not.available@online> wrote in message
news:(email address - cut out)...

Show quoted text

>
>
> "Simon Gronow" <(email address - cut out)> wrote in message
> news:#(email address - cut out)...
>> 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.
>
>
>

Re: Virtual Networking Problems

Sent: 08/25/2009
From: "Bill Grant" <not.available@online>
Message:

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

"Simon Gronow" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Hi Bill,
>
> All sorted thanks for your help.
>
>
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:(email address - cut out)...
>>
>>
>> "Simon Gronow" <(email address - cut out)> wrote in message
>> news:#(email address - cut out)...
>>> 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.
>>
>>
>>
>
>

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: