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 PC

Recent Virtual PC posts

* Virtual PC 2004 compared to VMWare?
* Need to use USB devices, What are my options?
* VPC 2004 and Win Update runs forever
* Virtual PC on extended Desktop Question
* 2005 virtual Server R2
* Multiple domains
* using diff
* cuestion for windows 3.11 on virtual PC
* Great Addition
* Logging into Windows NT 4.0
* virtual pc with duplicate system
* Creating Virtual PC Domain for MCSE
* Modem dropouts
* Three Questions - Installing MS-DOS, Mouse Problems, WinImage Problems
* Blank Screen using VPC and XP Pro
* dual Network card
* VPC alt gr
* DNS dynamic update & registration on Virtual PC 2004 SP1 - known issue?
* DOS 6.2.2 & VM Additions
* SuSE 10"s latest kernel

Add Solution

Router config with Vmachine and host

Source: microsoft.public.virtualpc
Sent: 09/21/2006
From: Amsps
Message:

Hi!
I need some help.
I have 2 VM with XP SP2.

VMachine 1: Network:
Local
Settings: 192.168.0.1 MASK 255.255.255.0 Default Gateway 192.168.0.2

VMachine 2: Network:
Local
Settings: 192.168.0.2 MASK 255.255.255.0 Default Gateway 192.168.0.2
Loopback Adapter
Settings: 192.168.1.4 MASK 255.255.255.0 Default Gateway 192.168.1.4

Real machine (host):
Loopback Adapter
Settings: 192.168.1.3 MASK 255.255.255.0 Default Gateway 192.168.1.4

Now, i can ping from host (192.168.1.3) to machine 2 (192.168.1.4).
I can ping from machine 1 (192.168.0.1) to machine 2 local (192.168.0.2)
I can ping from machine 1 (192.168.0.1) to machine 2 loopback (192.168.1.4)
I can ping from machine 2 to host (192.168.1.3).

So, why can't I ping from machine 1 (192.168.0.1) to host
(192.168.1.3)????????

Machine 2's Route table
Rotas activas:
Destino de rede Mask Gateway Interface MÃ©trica
0.0.0.0 0.0.0.0 192.168.0.2 192.168.0.2 20
0.0.0.0 0.0.0.0 192.168.1.4 192.168.1.4 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 20
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 20
192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4 20
192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4 20
224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 20
224.0.0.0 240.0.0.0 192.168.1.4 192.168.1.4 20
255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1
255.255.255.255 255.255.255.255 192.168.1.4 192.168.1.4 1
Gateway predef.: 192.168.1.4
===========================================================================

And i have enabled IP routing on machine 2:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"IPEnableRouter"=dword:00000001

Thanks, ManÃ©

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Router config with Vmachine and host

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

The main problem is your default gateway settings. But just about
everything about the setup is wrong.

You do not need loopback adapters in vms. The virtual NIC links to the
loopback adpater in the host.

Are you trying to configure one vm as a router? Or do you want the host
to route between its NIC and the vms in the loopback network?

To use the host as a router, put the vms in the loopback network. Give
them IP addresses in the same IP subnet as the loopback and with the
loopback adapter as their default gateway.

To use a vm as a router, put one of its NICs in a virtual network
(Local Only) and one in a network connected to the host (loopback adapter).
Put the other vm's NIC in local only.

Host
192.168.1.3 dg blank (loopback adapter)
|
192.168.1.4 dg 192.168.1.3 (link to loopback)
routing vm
192.168.0.2 dg blank (virtual network)
|
other vm
192.168.0.1 dg 192.168.0.2 (virtual network)

On the host, add a static route to send traffic for 192.168.0.0 to the
vm router.

192.168.0.1 255.255.255.0 192.168.1.4 .

The vms will now be able to ping each other and the host.

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

Show quoted text

> Hi!
> I need some help.
> I have 2 VM with XP SP2.
>
> VMachine 1: Network:
> Local
> Settings: 192.168.0.1 MASK 255.255.255.0 Default Gateway 192.168.0.2
>
> VMachine 2: Network:
> Local
> Settings: 192.168.0.2 MASK 255.255.255.0 Default Gateway 192.168.0.2
> Loopback Adapter
> Settings: 192.168.1.4 MASK 255.255.255.0 Default Gateway 192.168.1.4
>
> Real machine (host):
> Loopback Adapter
> Settings: 192.168.1.3 MASK 255.255.255.0 Default Gateway 192.168.1.4
>
> Now, i can ping from host (192.168.1.3) to machine 2 (192.168.1.4).
> I can ping from machine 1 (192.168.0.1) to machine 2 local (192.168.0.2)
> I can ping from machine 1 (192.168.0.1) to machine 2 loopback
> (192.168.1.4)
> I can ping from machine 2 to host (192.168.1.3).
>
> So, why can't I ping from machine 1 (192.168.0.1) to host
> (192.168.1.3)????????
>
>
> Machine 2's Route table
> Rotas activas:
> Destino de rede Mask Gateway Interface Métrica
> 0.0.0.0 0.0.0.0 192.168.0.2 192.168.0.2
> 20
> 0.0.0.0 0.0.0.0 192.168.1.4 192.168.1.4
> 20
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2
> 20
> 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1
> 20
> 192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2
> 20
> 192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4
> 20
> 192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1
> 20
> 192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4
> 20
> 224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2
> 20
> 224.0.0.0 240.0.0.0 192.168.1.4 192.168.1.4
> 20
> 255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1
> 255.255.255.255 255.255.255.255 192.168.1.4 192.168.1.4 1
> Gateway predef.: 192.168.1.4
> ===========================================================================
>
> And i have enabled IP routing on machine 2:
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
> "IPEnableRouter"=dword:00000001
>
> Thanks, Mané

Re: Router config with Vmachine and host

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

If you only want the virtual machines to see each other and the host
(and not other machines on the host's network), you can simplify things and
you do not need the added static route. You make the vm router the default
gateway for the loopback adapter.

192.168.1.3 dg 192.168.1.4
|
192.168.1.4 dg blank
router vm
192.168.0.2 dg blank
|
192.168.0.1 dg 192.168.0.2

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

Show quoted text

> The main problem is your default gateway settings. But just about
> everything about the setup is wrong.
>
> You do not need loopback adapters in vms. The virtual NIC links to the
> loopback adpater in the host.
>
> Are you trying to configure one vm as a router? Or do you want the host
> to route between its NIC and the vms in the loopback network?
>
> To use the host as a router, put the vms in the loopback network. Give
> them IP addresses in the same IP subnet as the loopback and with the
> loopback adapter as their default gateway.
>
> To use a vm as a router, put one of its NICs in a virtual network
> (Local Only) and one in a network connected to the host (loopback
> adapter). Put the other vm's NIC in local only.
>
> Host
> 192.168.1.3 dg blank (loopback adapter)
> |
> 192.168.1.4 dg 192.168.1.3 (link to loopback)
> routing vm
> 192.168.0.2 dg blank (virtual network)
> |
> other vm
> 192.168.0.1 dg 192.168.0.2 (virtual network)
>
> On the host, add a static route to send traffic for 192.168.0.0 to the
> vm router.
>
> 192.168.0.1 255.255.255.0 192.168.1.4 .
>
> The vms will now be able to ping each other and the host.
>
> "Amsps" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Hi!
>> I need some help.
>> I have 2 VM with XP SP2.
>>
>> VMachine 1: Network:
>> Local
>> Settings: 192.168.0.1 MASK 255.255.255.0 Default Gateway 192.168.0.2
>>
>> VMachine 2: Network:
>> Local
>> Settings: 192.168.0.2 MASK 255.255.255.0 Default Gateway 192.168.0.2
>> Loopback Adapter
>> Settings: 192.168.1.4 MASK 255.255.255.0 Default Gateway 192.168.1.4
>>
>> Real machine (host):
>> Loopback Adapter
>> Settings: 192.168.1.3 MASK 255.255.255.0 Default Gateway 192.168.1.4
>>
>> Now, i can ping from host (192.168.1.3) to machine 2 (192.168.1.4).
>> I can ping from machine 1 (192.168.0.1) to machine 2 local (192.168.0.2)
>> I can ping from machine 1 (192.168.0.1) to machine 2 loopback
>> (192.168.1.4)
>> I can ping from machine 2 to host (192.168.1.3).
>>
>> So, why can't I ping from machine 1 (192.168.0.1) to host
>> (192.168.1.3)????????
>>
>>
>> Machine 2's Route table
>> Rotas activas:
>> Destino de rede Mask Gateway Interface
>> Métrica
>> 0.0.0.0 0.0.0.0 192.168.0.2 192.168.0.2 20
>> 0.0.0.0 0.0.0.0 192.168.1.4 192.168.1.4 20
>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>> 1
>> 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 20
>> 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20
>> 192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 20
>> 192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4 20
>> 192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1 20
>> 192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4 20
>> 224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 20
>> 224.0.0.0 240.0.0.0 192.168.1.4 192.168.1.4 20
>> 255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2
>> 1
>> 255.255.255.255 255.255.255.255 192.168.1.4 192.168.1.4
>> 1
>> Gateway predef.: 192.168.1.4
>> ===========================================================================
>>
>> And i have enabled IP routing on machine 2:
>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
>> "IPEnableRouter"=dword:00000001
>>
>> Thanks, Mané
>
>

Re: Router config with Vmachine and host

Sent: 09/24/2006
From: Amsps
Message:

Hi.
Talking about this setup:
Host
192.168.1.3 dg blank (loopback adapter)
192.168.1.4 dg 192.168.1.3 (link to loopback)
routing vm
192.168.0.2 dg blank (virtual network)
other vm
192.168.0.1 dg 192.168.0.2 (virtual network)
On the host, add a static route to send traffic for 192.168.0.0 to the
vm router.
192.168.0.1 255.255.255.0 192.168.1.4 .

I've configured like you said (portuguese):

Host setup:
Real network
Sufixo DNS especÃfico da ligaÃ§Ã£o. :
AutoconfiguracÃ£o de endereÃ§o IP . : 192.168.1.4
MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
Gateway predefinido . . . . . . . : 192.168.1.3

Loopback:
Sufixo DNS especÃfico da ligaÃ§Ã£o. :
EndereÃ§o IP . . . . . . . . . . . : 192.168.1.3
MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
Gateway predefinido . . . . . . . :

VM Router (Local Network)
Adaptador ethernet Virtual Intel1:
Sufixo DNS especÃfico da ligaÃ§Ã£o. :
EndereÃ§o IP . . . . . . . . . . . : 192.168.0.2
MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
Gateway predefinido . . . . . . . :

Other VM (Local Network)
Adaptador ethernet LigaÃ§Ã£o de Ã¡rea local:
Sufixo DNS especÃfico da ligaÃ§Ã£o. :
EndereÃ§o IP . . . . . . . . . . . : 192.168.0.1
MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
Gateway predefinido . . . . . . . : 192.168.0.2

You've said that local network link to loopback on host,
but i don't think so, that's why there are local and loopback networks, IMHO.
And that's why i think that i can't ping from VM router and Other VM, to host.
Please feedback.
Thanks, ManÃ©

"Bill Grant" wrote:

Show quoted text

> If you only want the virtual machines to see each other and the host
> (and not other machines on the host's network), you can simplify things and
> you do not need the added static route. You make the vm router the default
> gateway for the loopback adapter.
>
> 192.168.1.3 dg 192.168.1.4
> |
> 192.168.1.4 dg blank
> router vm
> 192.168.0.2 dg blank
> |
> 192.168.0.1 dg 192.168.0.2
>
> "Bill Grant" <not.available@online> wrote in message
> news:(email address - cut out)...
> > The main problem is your default gateway settings. But just about
> > everything about the setup is wrong.
> >
> > You do not need loopback adapters in vms. The virtual NIC links to the
> > loopback adpater in the host.
> >
> > Are you trying to configure one vm as a router? Or do you want the host
> > to route between its NIC and the vms in the loopback network?
> >
> > To use the host as a router, put the vms in the loopback network. Give
> > them IP addresses in the same IP subnet as the loopback and with the
> > loopback adapter as their default gateway.
> >
> > To use a vm as a router, put one of its NICs in a virtual network
> > (Local Only) and one in a network connected to the host (loopback
> > adapter). Put the other vm's NIC in local only.
> >
> > Host
> > 192.168.1.3 dg blank (loopback adapter)
> > |
> > 192.168.1.4 dg 192.168.1.3 (link to loopback)
> > routing vm
> > 192.168.0.2 dg blank (virtual network)
> > |
> > other vm
> > 192.168.0.1 dg 192.168.0.2 (virtual network)
> >
> > On the host, add a static route to send traffic for 192.168.0.0 to the
> > vm router.
> >
> > 192.168.0.1 255.255.255.0 192.168.1.4 .
> >
> > The vms will now be able to ping each other and the host.
> >
> > "Amsps" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> >> Hi!
> >> I need some help.
> >> I have 2 VM with XP SP2.
> >>
> >> VMachine 1: Network:
> >> Local
> >> Settings: 192.168.0.1 MASK 255.255.255.0 Default Gateway 192.168.0.2
> >>
> >> VMachine 2: Network:
> >> Local
> >> Settings: 192.168.0.2 MASK 255.255.255.0 Default Gateway 192.168.0.2
> >> Loopback Adapter
> >> Settings: 192.168.1.4 MASK 255.255.255.0 Default Gateway 192.168.1.4
> >>
> >> Real machine (host):
> >> Loopback Adapter
> >> Settings: 192.168.1.3 MASK 255.255.255.0 Default Gateway 192.168.1.4
> >>
> >> Now, i can ping from host (192.168.1.3) to machine 2 (192.168.1.4).
> >> I can ping from machine 1 (192.168.0.1) to machine 2 local (192.168.0.2)
> >> I can ping from machine 1 (192.168.0.1) to machine 2 loopback
> >> (192.168.1.4)
> >> I can ping from machine 2 to host (192.168.1.3).
> >>
> >> So, why can't I ping from machine 1 (192.168.0.1) to host
> >> (192.168.1.3)????????
> >>
> >>
> >> Machine 2's Route table
> >> Rotas activas:
> >> Destino de rede Mask Gateway Interface
> >> MÃ©trica
> >> 0.0.0.0 0.0.0.0 192.168.0.2 192.168.0.2 20
> >> 0.0.0.0 0.0.0.0 192.168.1.4 192.168.1.4 20
> >> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
> >> 1
> >> 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 20
> >> 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20
> >> 192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 20
> >> 192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4 20
> >> 192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1 20
> >> 192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4 20
> >> 224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 20
> >> 224.0.0.0 240.0.0.0 192.168.1.4 192.168.1.4 20
> >> 255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2
> >> 1
> >> 255.255.255.255 255.255.255.255 192.168.1.4 192.168.1.4
> >> 1
> >> Gateway predef.: 192.168.1.4
> >> ===========================================================================
> >>
> >> And i have enabled IP routing on machine 2:
> >> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
> >> "IPEnableRouter"=dword:00000001
> >>
> >> Thanks, ManÃ©
> >
> >
>
>
>

Re: Router config with Vmachine and host

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

The network configuration on the host does not make any sense at all.
Why would you set up a loopback adapter and put it in the same IP subnet as
the real NIC? Why not just use the real NIC? Virtual Machine Network
Services allows a vm to access a network through the host's physical NIC.
You only need a loopback adapter if you don't have a NIC, or if you need two
interfaces on the host. If you have two interfaces on the host, you usually
want them to be in different IP subnets. In that case, you would normally
use the host as the router, not a virtual machine.

Your virtual router could work without any loopback adapters at all. You
would link the "host" side of the vm router to the physical NIC of the host
machine (the default setting). This interface of the virtual router would be
in the same IP subnet as the host NIC. You would put the NIC on the "guest"
side in Local Only. This NIC would be in the same IP subnet as the second XP
guest machine.

I think that you are trying to make this more complicated than it needs
to be. Could you tell us exactly what you are trying to achieve? How you
configure the router depends on how you want the network to perform.

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

Show quoted text

> Hi.
> Talking about this setup:
> Host
> 192.168.1.3 dg blank (loopback adapter)
> 192.168.1.4 dg 192.168.1.3 (link to loopback)
> routing vm
> 192.168.0.2 dg blank (virtual network)
> other vm
> 192.168.0.1 dg 192.168.0.2 (virtual network)
> On the host, add a static route to send traffic for 192.168.0.0 to the
> vm router.
> 192.168.0.1 255.255.255.0 192.168.1.4 .
>
> I've configured like you said (portuguese):
>
> Host setup:
> Real network
> Sufixo DNS específico da ligação. :
> Autoconfiguracão de endereço IP . : 192.168.1.4
> Máscara de sub-rede . . . . . . . : 255.255.255.0
> Gateway predefinido . . . . . . . : 192.168.1.3
>
> Loopback:
> Sufixo DNS específico da ligação. :
> Endereço IP . . . . . . . . . . . : 192.168.1.3
> Máscara de sub-rede . . . . . . . : 255.255.255.0
> Gateway predefinido . . . . . . . :
>
> VM Router (Local Network)
> Adaptador ethernet Virtual Intel1:
> Sufixo DNS específico da ligação. :
> Endereço IP . . . . . . . . . . . : 192.168.0.2
> Máscara de sub-rede . . . . . . . : 255.255.255.0
> Gateway predefinido . . . . . . . :
>
> Other VM (Local Network)
> Adaptador ethernet Ligação de área local:
> Sufixo DNS específico da ligação. :
> Endereço IP . . . . . . . . . . . : 192.168.0.1
> Máscara de sub-rede . . . . . . . : 255.255.255.0
> Gateway predefinido . . . . . . . : 192.168.0.2
>
> You've said that local network link to loopback on host,
> but i don't think so, that's why there are local and loopback networks,
> IMHO.
> And that's why i think that i can't ping from VM router and Other VM, to
> host.
> Please feedback.
> Thanks, Mané
>
>
> "Bill Grant" wrote:
>
>> If you only want the virtual machines to see each other and the host
>> (and not other machines on the host's network), you can simplify things
>> and
>> you do not need the added static route. You make the vm router the
>> default
>> gateway for the loopback adapter.
>>
>> 192.168.1.3 dg 192.168.1.4
>> |
>> 192.168.1.4 dg blank
>> router vm
>> 192.168.0.2 dg blank
>> |
>> 192.168.0.1 dg 192.168.0.2
>>
>> "Bill Grant" <not.available@online> wrote in message
>> news:(email address - cut out)...
>> > The main problem is your default gateway settings. But just about
>> > everything about the setup is wrong.
>> >
>> > You do not need loopback adapters in vms. The virtual NIC links to
>> > the
>> > loopback adpater in the host.
>> >
>> > Are you trying to configure one vm as a router? Or do you want the
>> > host
>> > to route between its NIC and the vms in the loopback network?
>> >
>> > To use the host as a router, put the vms in the loopback network.
>> > Give
>> > them IP addresses in the same IP subnet as the loopback and with the
>> > loopback adapter as their default gateway.
>> >
>> > To use a vm as a router, put one of its NICs in a virtual network
>> > (Local Only) and one in a network connected to the host (loopback
>> > adapter). Put the other vm's NIC in local only.
>> >
>> > Host
>> > 192.168.1.3 dg blank (loopback adapter)
>> > |
>> > 192.168.1.4 dg 192.168.1.3 (link to loopback)
>> > routing vm
>> > 192.168.0.2 dg blank (virtual network)
>> > |
>> > other vm
>> > 192.168.0.1 dg 192.168.0.2 (virtual network)
>> >
>> > On the host, add a static route to send traffic for 192.168.0.0 to
>> > the
>> > vm router.
>> >
>> > 192.168.0.1 255.255.255.0 192.168.1.4 .
>> >
>> > The vms will now be able to ping each other and the host.
>> >
>> > "Amsps" <(email address - cut out)> wrote in message
>> > news:(email address - cut out)...
>> >> Hi!
>> >> I need some help.
>> >> I have 2 VM with XP SP2.
>> >>
>> >> VMachine 1: Network:
>> >> Local
>> >> Settings: 192.168.0.1 MASK 255.255.255.0 Default Gateway 192.168.0.2
>> >>
>> >> VMachine 2: Network:
>> >> Local
>> >> Settings: 192.168.0.2 MASK 255.255.255.0 Default Gateway 192.168.0.2
>> >> Loopback Adapter
>> >> Settings: 192.168.1.4 MASK 255.255.255.0 Default Gateway 192.168.1.4
>> >>
>> >> Real machine (host):
>> >> Loopback Adapter
>> >> Settings: 192.168.1.3 MASK 255.255.255.0 Default Gateway 192.168.1.4
>> >>
>> >> Now, i can ping from host (192.168.1.3) to machine 2 (192.168.1.4).
>> >> I can ping from machine 1 (192.168.0.1) to machine 2 local
>> >> (192.168.0.2)
>> >> I can ping from machine 1 (192.168.0.1) to machine 2 loopback
>> >> (192.168.1.4)
>> >> I can ping from machine 2 to host (192.168.1.3).
>> >>
>> >> So, why can't I ping from machine 1 (192.168.0.1) to host
>> >> (192.168.1.3)????????
>> >>
>> >>
>> >> Machine 2's Route table
>> >> Rotas activas:
>> >> Destino de rede Mask Gateway Interface
>> >> Métrica
>> >> 0.0.0.0 0.0.0.0 192.168.0.2 192.168.0.2 20
>> >> 0.0.0.0 0.0.0.0 192.168.1.4 192.168.1.4 20
>> >> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>> >> 1
>> >> 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 20
>> >> 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20
>> >> 192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 20
>> >> 192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4 20
>> >> 192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1 20
>> >> 192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4 20
>> >> 224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 20
>> >> 224.0.0.0 240.0.0.0 192.168.1.4 192.168.1.4 20
>> >> 255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2
>> >> 1
>> >> 255.255.255.255 255.255.255.255 192.168.1.4 192.168.1.4
>> >> 1
>> >> Gateway predef.: 192.168.1.4
>> >> ===========================================================================
>> >>
>> >> And i have enabled IP routing on machine 2:
>> >> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
>> >> "IPEnableRouter"=dword:00000001
>> >>
>> >> Thanks, Mané
>> >
>> >
>>
>>
>>

Re: Router config with Vmachine and host

Sent: 09/26/2006
From: Amsps
Message:

Hi!
I was trying to implement this
http://www.windowsdevcenter.com/pub/a/windows/2006/07/11/build-a-virtual-routed-network.html
but with connection from local network (VPC) to the real machine without
afecting its parameters, that's why I want loopback.
Then I've made a route (or IPEnableRouter=1) from loopback to the real
adapter.
Well I've made it but with ping problems (although with all machines with
echo ping enabled but firewall enabled). I've had to disable the firewall to
make ping. And do you know how, with firewall enabled, can I ping to
machine's NetBIOS names? I can't resolve NetBIOS names with firewall enabled!
Thanks, ManÃ©

"Bill Grant" wrote:

Show quoted text

> The network configuration on the host does not make any sense at all.
> Why would you set up a loopback adapter and put it in the same IP subnet as
> the real NIC? Why not just use the real NIC? Virtual Machine Network
> Services allows a vm to access a network through the host's physical NIC.
> You only need a loopback adapter if you don't have a NIC, or if you need two
> interfaces on the host. If you have two interfaces on the host, you usually
> want them to be in different IP subnets. In that case, you would normally
> use the host as the router, not a virtual machine.
>
> Your virtual router could work without any loopback adapters at all. You
> would link the "host" side of the vm router to the physical NIC of the host
> machine (the default setting). This interface of the virtual router would be
> in the same IP subnet as the host NIC. You would put the NIC on the "guest"
> side in Local Only. This NIC would be in the same IP subnet as the second XP
> guest machine.
>
> I think that you are trying to make this more complicated than it needs
> to be. Could you tell us exactly what you are trying to achieve? How you
> configure the router depends on how you want the network to perform.
>
> "Amsps" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hi.
> > Talking about this setup:
> > Host
> > 192.168.1.3 dg blank (loopback adapter)
> > 192.168.1.4 dg 192.168.1.3 (link to loopback)
> > routing vm
> > 192.168.0.2 dg blank (virtual network)
> > other vm
> > 192.168.0.1 dg 192.168.0.2 (virtual network)
> > On the host, add a static route to send traffic for 192.168.0.0 to the
> > vm router.
> > 192.168.0.1 255.255.255.0 192.168.1.4 .
> >
> > I've configured like you said (portuguese):
> >
> > Host setup:
> > Real network
> > Sufixo DNS especÃfico da ligaÃ§Ã£o. :
> > AutoconfiguracÃ£o de endereÃ§o IP . : 192.168.1.4
> > MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
> > Gateway predefinido . . . . . . . : 192.168.1.3
> >
> > Loopback:
> > Sufixo DNS especÃfico da ligaÃ§Ã£o. :
> > EndereÃ§o IP . . . . . . . . . . . : 192.168.1.3
> > MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
> > Gateway predefinido . . . . . . . :
> >
> > VM Router (Local Network)
> > Adaptador ethernet Virtual Intel1:
> > Sufixo DNS especÃfico da ligaÃ§Ã£o. :
> > EndereÃ§o IP . . . . . . . . . . . : 192.168.0.2
> > MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
> > Gateway predefinido . . . . . . . :
> >
> > Other VM (Local Network)
> > Adaptador ethernet LigaÃ§Ã£o de Ã¡rea local:
> > Sufixo DNS especÃfico da ligaÃ§Ã£o. :
> > EndereÃ§o IP . . . . . . . . . . . : 192.168.0.1
> > MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
> > Gateway predefinido . . . . . . . : 192.168.0.2
> >
> > You've said that local network link to loopback on host,
> > but i don't think so, that's why there are local and loopback networks,
> > IMHO.
> > And that's why i think that i can't ping from VM router and Other VM, to
> > host.
> > Please feedback.
> > Thanks, ManÃ©
> >
> >
> > "Bill Grant" wrote:
> >
> >> If you only want the virtual machines to see each other and the host
> >> (and not other machines on the host's network), you can simplify things
> >> and
> >> you do not need the added static route. You make the vm router the
> >> default
> >> gateway for the loopback adapter.
> >>
> >> 192.168.1.3 dg 192.168.1.4
> >> |
> >> 192.168.1.4 dg blank
> >> router vm
> >> 192.168.0.2 dg blank
> >> |
> >> 192.168.0.1 dg 192.168.0.2
> >>
> >> "Bill Grant" <not.available@online> wrote in message
> >> news:(email address - cut out)...
> >> > The main problem is your default gateway settings. But just about
> >> > everything about the setup is wrong.
> >> >
> >> > You do not need loopback adapters in vms. The virtual NIC links to
> >> > the
> >> > loopback adpater in the host.
> >> >
> >> > Are you trying to configure one vm as a router? Or do you want the
> >> > host
> >> > to route between its NIC and the vms in the loopback network?
> >> >
> >> > To use the host as a router, put the vms in the loopback network.
> >> > Give
> >> > them IP addresses in the same IP subnet as the loopback and with the
> >> > loopback adapter as their default gateway.
> >> >
> >> > To use a vm as a router, put one of its NICs in a virtual network
> >> > (Local Only) and one in a network connected to the host (loopback
> >> > adapter). Put the other vm's NIC in local only.
> >> >
> >> > Host
> >> > 192.168.1.3 dg blank (loopback adapter)
> >> > |
> >> > 192.168.1.4 dg 192.168.1.3 (link to loopback)
> >> > routing vm
> >> > 192.168.0.2 dg blank (virtual network)
> >> > |
> >> > other vm
> >> > 192.168.0.1 dg 192.168.0.2 (virtual network)
> >> >
> >> > On the host, add a static route to send traffic for 192.168.0.0 to
> >> > the
> >> > vm router.
> >> >
> >> > 192.168.0.1 255.255.255.0 192.168.1.4 .
> >> >
> >> > The vms will now be able to ping each other and the host.
> >> >
> >> > "Amsps" <(email address - cut out)> wrote in message
> >> > news:(email address - cut out)...
> >> >> Hi!
> >> >> I need some help.
> >> >> I have 2 VM with XP SP2.
> >> >>
> >> >> VMachine 1: Network:
> >> >> Local
> >> >> Settings: 192.168.0.1 MASK 255.255.255.0 Default Gateway 192.168.0.2
> >> >>
> >> >> VMachine 2: Network:
> >> >> Local
> >> >> Settings: 192.168.0.2 MASK 255.255.255.0 Default Gateway 192.168.0.2
> >> >> Loopback Adapter
> >> >> Settings: 192.168.1.4 MASK 255.255.255.0 Default Gateway 192.168.1.4
> >> >>
> >> >> Real machine (host):
> >> >> Loopback Adapter
> >> >> Settings: 192.168.1.3 MASK 255.255.255.0 Default Gateway 192.168.1.4
> >> >>
> >> >> Now, i can ping from host (192.168.1.3) to machine 2 (192.168.1.4).
> >> >> I can ping from machine 1 (192.168.0.1) to machine 2 local
> >> >> (192.168.0.2)
> >> >> I can ping from machine 1 (192.168.0.1) to machine 2 loopback
> >> >> (192.168.1.4)
> >> >> I can ping from machine 2 to host (192.168.1.3).
> >> >>
> >> >> So, why can't I ping from machine 1 (192.168.0.1) to host
> >> >> (192.168.1.3)????????
> >> >>
> >> >>
> >> >> Machine 2's Route table
> >> >> Rotas activas:
> >> >> Destino de rede Mask Gateway Interface
> >> >> MÃ©trica
> >> >> 0.0.0.0 0.0.0.0 192.168.0.2 192.168.0.2 20
> >> >> 0.0.0.0 0.0.0.0 192.168.1.4 192.168.1.4 20
> >> >> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
> >> >> 1
> >> >> 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 20
> >> >> 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20
> >> >> 192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 20
> >> >> 192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4 20
> >> >> 192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1 20
> >> >> 192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4 20
> >> >> 224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 20
> >> >> 224.0.0.0 240.0.0.0 192.168.1.4 192.168.1.4 20
> >> >> 255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2
> >> >> 1
> >> >> 255.255.255.255 255.255.255.255 192.168.1.4 192.168.1.4
> >> >> 1
> >> >> Gateway predef.: 192.168.1.4
> >> >> ===========================================================================
> >> >>
> >> >> And i have enabled IP routing on machine 2:
> >> >> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
> >> >> "IPEnableRouter"=dword:00000001
> >> >>
> >> >> Thanks, ManÃ©
> >> >
> >> >
> >>
> >>
> >>
>
>
>

Re: Router config with Vmachine and host

Sent: 09/27/2006
From: "Bill Grant" <not.available@online>
Message:

I have had a look at Mitch Tulloch's article and I cannot see any
similarities between that and what you appear to be trying to do. The
network in the article uses four virtual machines (running on the same host
machine), two of them configured as routers. Are you trying to configure
something similar using two vms and two "real" machines? I suggest that you
study the diagram in the article carefully, especially the table of default
gateway settings. Also be careful about how Mitch uses the word "host". He
uses it in the networking sense, which is not the same as the general usage
in virtual machine circles. For virtual machines, "host" refers to the
physical machine which runs the VPC or Virtual Server application.

IP routing routes between IP subnets. If you enable IP routing on a host
machine to route between the physical and the loopback networks, the NIC and
the loopack adapter must be in different IP subnets.

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

Show quoted text

> Hi!
> I was trying to implement this
> http://www.windowsdevcenter.com/pub/a/windows/2006/07/11/build-a-virtual-routed-network.html
> but with connection from local network (VPC) to the real machine without
> afecting its parameters, that's why I want loopback.
> Then I've made a route (or IPEnableRouter=1) from loopback to the real
> adapter.
> Well I've made it but with ping problems (although with all machines with
> echo ping enabled but firewall enabled). I've had to disable the firewall
> to
> make ping. And do you know how, with firewall enabled, can I ping to
> machine's NetBIOS names? I can't resolve NetBIOS names with firewall
> enabled!
> Thanks, Mané
>
> "Bill Grant" wrote:
>
>> The network configuration on the host does not make any sense at all.
>> Why would you set up a loopback adapter and put it in the same IP subnet
>> as
>> the real NIC? Why not just use the real NIC? Virtual Machine Network
>> Services allows a vm to access a network through the host's physical NIC.
>> You only need a loopback adapter if you don't have a NIC, or if you need
>> two
>> interfaces on the host. If you have two interfaces on the host, you
>> usually
>> want them to be in different IP subnets. In that case, you would normally
>> use the host as the router, not a virtual machine.
>>
>> Your virtual router could work without any loopback adapters at all.
>> You
>> would link the "host" side of the vm router to the physical NIC of the
>> host
>> machine (the default setting). This interface of the virtual router would
>> be
>> in the same IP subnet as the host NIC. You would put the NIC on the
>> "guest"
>> side in Local Only. This NIC would be in the same IP subnet as the second
>> XP
>> guest machine.
>>
>> I think that you are trying to make this more complicated than it
>> needs
>> to be. Could you tell us exactly what you are trying to achieve? How you
>> configure the router depends on how you want the network to perform.
>>
>> "Amsps" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hi.
>> > Talking about this setup:
>> > Host
>> > 192.168.1.3 dg blank (loopback adapter)
>> > 192.168.1.4 dg 192.168.1.3 (link to loopback)
>> > routing vm
>> > 192.168.0.2 dg blank (virtual network)
>> > other vm
>> > 192.168.0.1 dg 192.168.0.2 (virtual network)
>> > On the host, add a static route to send traffic for 192.168.0.0 to the
>> > vm router.
>> > 192.168.0.1 255.255.255.0 192.168.1.4 .
>> >
>> > I've configured like you said (portuguese):
>> >
>> > Host setup:
>> > Real network
>> > Sufixo DNS específico da ligação. :
>> > Autoconfiguracão de endereço IP . : 192.168.1.4
>> > Máscara de sub-rede . . . . . . . : 255.255.255.0
>> > Gateway predefinido . . . . . . . : 192.168.1.3
>> >
>> > Loopback:
>> > Sufixo DNS específico da ligação. :
>> > Endereço IP . . . . . . . . . . . : 192.168.1.3
>> > Máscara de sub-rede . . . . . . . : 255.255.255.0
>> > Gateway predefinido . . . . . . . :
>> >
>> > VM Router (Local Network)
>> > Adaptador ethernet Virtual Intel1:
>> > Sufixo DNS específico da ligação. :
>> > Endereço IP . . . . . . . . . . . : 192.168.0.2
>> > Máscara de sub-rede . . . . . . . : 255.255.255.0
>> > Gateway predefinido . . . . . . . :
>> >
>> > Other VM (Local Network)
>> > Adaptador ethernet Ligação de área local:
>> > Sufixo DNS específico da ligação. :
>> > Endereço IP . . . . . . . . . . . : 192.168.0.1
>> > Máscara de sub-rede . . . . . . . : 255.255.255.0
>> > Gateway predefinido . . . . . . . : 192.168.0.2
>> >
>> > You've said that local network link to loopback on host,
>> > but i don't think so, that's why there are local and loopback networks,
>> > IMHO.
>> > And that's why i think that i can't ping from VM router and Other VM,
>> > to
>> > host.
>> > Please feedback.
>> > Thanks, Mané
>> >
>> >
>> > "Bill Grant" wrote:
>> >
>> >> If you only want the virtual machines to see each other and the
>> >> host
>> >> (and not other machines on the host's network), you can simplify
>> >> things
>> >> and
>> >> you do not need the added static route. You make the vm router the
>> >> default
>> >> gateway for the loopback adapter.
>> >>
>> >> 192.168.1.3 dg 192.168.1.4
>> >> |
>> >> 192.168.1.4 dg blank
>> >> router vm
>> >> 192.168.0.2 dg blank
>> >> |
>> >> 192.168.0.1 dg 192.168.0.2
>> >>
>> >> "Bill Grant" <not.available@online> wrote in message
>> >> news:(email address - cut out)...
>> >> > The main problem is your default gateway settings. But just about
>> >> > everything about the setup is wrong.
>> >> >
>> >> > You do not need loopback adapters in vms. The virtual NIC links
>> >> > to
>> >> > the
>> >> > loopback adpater in the host.
>> >> >
>> >> > Are you trying to configure one vm as a router? Or do you want
>> >> > the
>> >> > host
>> >> > to route between its NIC and the vms in the loopback network?
>> >> >
>> >> > To use the host as a router, put the vms in the loopback network.
>> >> > Give
>> >> > them IP addresses in the same IP subnet as the loopback and with the
>> >> > loopback adapter as their default gateway.
>> >> >
>> >> > To use a vm as a router, put one of its NICs in a virtual
>> >> > network
>> >> > (Local Only) and one in a network connected to the host (loopback
>> >> > adapter). Put the other vm's NIC in local only.
>> >> >
>> >> > Host
>> >> > 192.168.1.3 dg blank (loopback adapter)
>> >> > |
>> >> > 192.168.1.4 dg 192.168.1.3 (link to loopback)
>> >> > routing vm
>> >> > 192.168.0.2 dg blank (virtual network)
>> >> > |
>> >> > other vm
>> >> > 192.168.0.1 dg 192.168.0.2 (virtual network)
>> >> >
>> >> > On the host, add a static route to send traffic for 192.168.0.0
>> >> > to
>> >> > the
>> >> > vm router.
>> >> >
>> >> > 192.168.0.1 255.255.255.0 192.168.1.4 .
>> >> >
>> >> > The vms will now be able to ping each other and the host.
>> >> >
>> >> > "Amsps" <(email address - cut out)> wrote in message
>> >> > news:(email address - cut out)...
>> >> >> Hi!
>> >> >> I need some help.
>> >> >> I have 2 VM with XP SP2.
>> >> >>
>> >> >> VMachine 1: Network:
>> >> >> Local
>> >> >> Settings: 192.168.0.1 MASK 255.255.255.0 Default Gateway
>> >> >> 192.168.0.2
>> >> >>
>> >> >> VMachine 2: Network:
>> >> >> Local
>> >> >> Settings: 192.168.0.2 MASK 255.255.255.0 Default Gateway
>> >> >> 192.168.0.2
>> >> >> Loopback Adapter
>> >> >> Settings: 192.168.1.4 MASK 255.255.255.0 Default Gateway
>> >> >> 192.168.1.4
>> >> >>
>> >> >> Real machine (host):
>> >> >> Loopback Adapter
>> >> >> Settings: 192.168.1.3 MASK 255.255.255.0 Default Gateway
>> >> >> 192.168.1.4
>> >> >>
>> >> >> Now, i can ping from host (192.168.1.3) to machine 2 (192.168.1.4).
>> >> >> I can ping from machine 1 (192.168.0.1) to machine 2 local
>> >> >> (192.168.0.2)
>> >> >> I can ping from machine 1 (192.168.0.1) to machine 2 loopback
>> >> >> (192.168.1.4)
>> >> >> I can ping from machine 2 to host (192.168.1.3).
>> >> >>
>> >> >> So, why can't I ping from machine 1 (192.168.0.1) to host
>> >> >> (192.168.1.3)????????
>> >> >>
>> >> >>
>> >> >> Machine 2's Route table
>> >> >> Rotas activas:
>> >> >> Destino de rede Mask Gateway Interface
>> >> >> Métrica
>> >> >> 0.0.0.0 0.0.0.0 192.168.0.2 192.168.0.2
>> >> >> 20
>> >> >> 0.0.0.0 0.0.0.0 192.168.1.4 192.168.1.4
>> >> >> 20
>> >> >> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
>> >> >> 1
>> >> >> 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2
>> >> >> 20
>> >> >> 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1
>> >> >> 20
>> >> >> 192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2
>> >> >> 20
>> >> >> 192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4
>> >> >> 20
>> >> >> 192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1
>> >> >> 20
>> >> >> 192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4
>> >> >> 20
>> >> >> 224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2
>> >> >> 20
>> >> >> 224.0.0.0 240.0.0.0 192.168.1.4 192.168.1.4
>> >> >> 20
>> >> >> 255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2
>> >> >> 1
>> >> >> 255.255.255.255 255.255.255.255 192.168.1.4 192.168.1.4
>> >> >> 1
>> >> >> Gateway predef.: 192.168.1.4
>> >> >> ===========================================================================
>> >> >>
>> >> >> And i have enabled IP routing on machine 2:
>> >> >> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
>> >> >> "IPEnableRouter"=dword:00000001
>> >> >>
>> >> >> Thanks, Mané
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>

Re: Router config with Vmachine and host

Sent: 09/27/2006
From: Amsps
Message:

Well, sometimes we post and at the same time we already implementing other
things.
I've made it with no problem, and loopback in another subnet.
Do you know what firewall settings do we have to disable/enable to make:
a ping from the real machine to virtual machine (i've tried to enable echo
requests but it didn't work)
a ping from the real machine to a NetBIOS names (with firewall).
Thanks for the help,
greetings

"Bill Grant" wrote:

Show quoted text

> I have had a look at Mitch Tulloch's article and I cannot see any
> similarities between that and what you appear to be trying to do. The
> network in the article uses four virtual machines (running on the same host
> machine), two of them configured as routers. Are you trying to configure
> something similar using two vms and two "real" machines? I suggest that you
> study the diagram in the article carefully, especially the table of default
> gateway settings. Also be careful about how Mitch uses the word "host". He
> uses it in the networking sense, which is not the same as the general usage
> in virtual machine circles. For virtual machines, "host" refers to the
> physical machine which runs the VPC or Virtual Server application.
>
> IP routing routes between IP subnets. If you enable IP routing on a host
> machine to route between the physical and the loopback networks, the NIC and
> the loopack adapter must be in different IP subnets.
>
>
> "Amsps" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Hi!
> > I was trying to implement this
> > http://www.windowsdevcenter.com/pub/a/windows/2006/07/11/build-a-virtual-routed-network.html
> > but with connection from local network (VPC) to the real machine without
> > afecting its parameters, that's why I want loopback.
> > Then I've made a route (or IPEnableRouter=1) from loopback to the real
> > adapter.
> > Well I've made it but with ping problems (although with all machines with
> > echo ping enabled but firewall enabled). I've had to disable the firewall
> > to
> > make ping. And do you know how, with firewall enabled, can I ping to
> > machine's NetBIOS names? I can't resolve NetBIOS names with firewall
> > enabled!
> > Thanks, ManÃ©
> >
> > "Bill Grant" wrote:
> >
> >> The network configuration on the host does not make any sense at all.
> >> Why would you set up a loopback adapter and put it in the same IP subnet
> >> as
> >> the real NIC? Why not just use the real NIC? Virtual Machine Network
> >> Services allows a vm to access a network through the host's physical NIC.
> >> You only need a loopback adapter if you don't have a NIC, or if you need
> >> two
> >> interfaces on the host. If you have two interfaces on the host, you
> >> usually
> >> want them to be in different IP subnets. In that case, you would normally
> >> use the host as the router, not a virtual machine.
> >>
> >> Your virtual router could work without any loopback adapters at all.
> >> You
> >> would link the "host" side of the vm router to the physical NIC of the
> >> host
> >> machine (the default setting). This interface of the virtual router would
> >> be
> >> in the same IP subnet as the host NIC. You would put the NIC on the
> >> "guest"
> >> side in Local Only. This NIC would be in the same IP subnet as the second
> >> XP
> >> guest machine.
> >>
> >> I think that you are trying to make this more complicated than it
> >> needs
> >> to be. Could you tell us exactly what you are trying to achieve? How you
> >> configure the router depends on how you want the network to perform.
> >>
> >> "Amsps" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> > Hi.
> >> > Talking about this setup:
> >> > Host
> >> > 192.168.1.3 dg blank (loopback adapter)
> >> > 192.168.1.4 dg 192.168.1.3 (link to loopback)
> >> > routing vm
> >> > 192.168.0.2 dg blank (virtual network)
> >> > other vm
> >> > 192.168.0.1 dg 192.168.0.2 (virtual network)
> >> > On the host, add a static route to send traffic for 192.168.0.0 to the
> >> > vm router.
> >> > 192.168.0.1 255.255.255.0 192.168.1.4 .
> >> >
> >> > I've configured like you said (portuguese):
> >> >
> >> > Host setup:
> >> > Real network
> >> > Sufixo DNS especÃfico da ligaÃ§Ã£o. :
> >> > AutoconfiguracÃ£o de endereÃ§o IP . : 192.168.1.4
> >> > MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
> >> > Gateway predefinido . . . . . . . : 192.168.1.3
> >> >
> >> > Loopback:
> >> > Sufixo DNS especÃfico da ligaÃ§Ã£o. :
> >> > EndereÃ§o IP . . . . . . . . . . . : 192.168.1.3
> >> > MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
> >> > Gateway predefinido . . . . . . . :
> >> >
> >> > VM Router (Local Network)
> >> > Adaptador ethernet Virtual Intel1:
> >> > Sufixo DNS especÃfico da ligaÃ§Ã£o. :
> >> > EndereÃ§o IP . . . . . . . . . . . : 192.168.0.2
> >> > MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
> >> > Gateway predefinido . . . . . . . :
> >> >
> >> > Other VM (Local Network)
> >> > Adaptador ethernet LigaÃ§Ã£o de Ã¡rea local:
> >> > Sufixo DNS especÃfico da ligaÃ§Ã£o. :
> >> > EndereÃ§o IP . . . . . . . . . . . : 192.168.0.1
> >> > MÃ¡scara de sub-rede . . . . . . . : 255.255.255.0
> >> > Gateway predefinido . . . . . . . : 192.168.0.2
> >> >
> >> > You've said that local network link to loopback on host,
> >> > but i don't think so, that's why there are local and loopback networks,
> >> > IMHO.
> >> > And that's why i think that i can't ping from VM router and Other VM,
> >> > to
> >> > host.
> >> > Please feedback.
> >> > Thanks, ManÃ©
> >> >
> >> >
> >> > "Bill Grant" wrote:
> >> >
> >> >> If you only want the virtual machines to see each other and the
> >> >> host
> >> >> (and not other machines on the host's network), you can simplify
> >> >> things
> >> >> and
> >> >> you do not need the added static route. You make the vm router the
> >> >> default
> >> >> gateway for the loopback adapter.
> >> >>
> >> >> 192.168.1.3 dg 192.168.1.4
> >> >> |
> >> >> 192.168.1.4 dg blank
> >> >> router vm
> >> >> 192.168.0.2 dg blank
> >> >> |
> >> >> 192.168.0.1 dg 192.168.0.2
> >> >>
> >> >> "Bill Grant" <not.available@online> wrote in message
> >> >> news:(email address - cut out)...
> >> >> > The main problem is your default gateway settings. But just about
> >> >> > everything about the setup is wrong.
> >> >> >
> >> >> > You do not need loopback adapters in vms. The virtual NIC links
> >> >> > to
> >> >> > the
> >> >> > loopback adpater in the host.
> >> >> >
> >> >> > Are you trying to configure one vm as a router? Or do you want
> >> >> > the
> >> >> > host
> >> >> > to route between its NIC and the vms in the loopback network?
> >> >> >
> >> >> > To use the host as a router, put the vms in the loopback network.
> >> >> > Give
> >> >> > them IP addresses in the same IP subnet as the loopback and with the
> >> >> > loopback adapter as their default gateway.
> >> >> >
> >> >> > To use a vm as a router, put one of its NICs in a virtual
> >> >> > network
> >> >> > (Local Only) and one in a network connected to the host (loopback
> >> >> > adapter). Put the other vm's NIC in local only.
> >> >> >
> >> >> > Host
> >> >> > 192.168.1.3 dg blank (loopback adapter)
> >> >> > |
> >> >> > 192.168.1.4 dg 192.168.1.3 (link to loopback)
> >> >> > routing vm
> >> >> > 192.168.0.2 dg blank (virtual network)
> >> >> > |
> >> >> > other vm
> >> >> > 192.168.0.1 dg 192.168.0.2 (virtual network)
> >> >> >
> >> >> > On the host, add a static route to send traffic for 192.168.0.0
> >> >> > to
> >> >> > the
> >> >> > vm router.
> >> >> >
> >> >> > 192.168.0.1 255.255.255.0 192.168.1.4 .
> >> >> >
> >> >> > The vms will now be able to ping each other and the host.
> >> >> >
> >> >> > "Amsps" <(email address - cut out)> wrote in message
> >> >> > news:(email address - cut out)...
> >> >> >> Hi!
> >> >> >> I need some help.
> >> >> >> I have 2 VM with XP SP2.
> >> >> >>
> >> >> >> VMachine 1: Network:
> >> >> >> Local
> >> >> >> Settings: 192.168.0.1 MASK 255.255.255.0 Default Gateway
> >> >> >> 192.168.0.2
> >> >> >>
> >> >> >> VMachine 2: Network:
> >> >> >> Local
> >> >> >> Settings: 192.168.0.2 MASK 255.255.255.0 Default Gateway
> >> >> >> 192.168.0.2
> >> >> >> Loopback Adapter
> >> >> >> Settings: 192.168.1.4 MASK 255.255.255.0 Default Gateway
> >> >> >> 192.168.1.4
> >> >> >>
> >> >> >> Real machine (host):
> >> >> >> Loopback Adapter
> >> >> >> Settings: 192.168.1.3 MASK 255.255.255.0 Default Gateway
> >> >> >> 192.168.1.4
> >> >> >>
> >> >> >> Now, i can ping from host (192.168.1.3) to machine 2 (192.168.1.4).
> >> >> >> I can ping from machine 1 (192.168.0.1) to machine 2 local
> >> >> >> (192.168.0.2)
> >> >> >> I can ping from machine 1 (192.168.0.1) to machine 2 loopback
> >> >> >> (192.168.1.4)
> >> >> >> I can ping from machine 2 to host (192.168.1.3).
> >> >> >>
> >> >> >> So, why can't I ping from machine 1 (192.168.0.1) to host
> >> >> >> (192.168.1.3)????????
> >> >> >>
> >> >> >>
> >> >> >> Machine 2's Route table
> >> >> >> Rotas activas:
> >> >> >> Destino de rede Mask Gateway Interface
> >> >> >> MÃ©trica
> >> >> >> 0.0.0.0 0.0.0.0 192.168.0.2 192.168.0.2
> >> >> >> 20
> >> >> >> 0.0.0.0 0.0.0.0 192.168.1.4 192.168.1.4
> >> >> >> 20
> >> >> >> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
> >> >> >> 1
> >> >> >> 192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2
> >> >> >> 20
> >> >> >> 192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1
> >> >> >> 20
> >> >> >> 192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2
> >> >> >> 20
> >> >> >> 192.168.1.0 255.255.255.0 192.168.1.4 192.168.1.4
> >> >> >> 20
> >> >> >> 192.168.1.4 255.255.255.255 127.0.0.1 127.0.0.1
> >> >> >> 20
> >> >> >> 192.168.1.255 255.255.255.255 192.168.1.4 192.168.1.4
> >> >> >> 20
> >> >> >> 224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2
> >> >> >> 20
> >> >> >> 224.0.0.0 240.0.0.0 192.168.1.4 192.168.1.4
> >> >> >> 20
> >> >> >> 255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2
> >> >> >> 1
> >> >> >> 255.255.255.255 255.255.255.255 192.168.1.4 192.168.1.4
> >> >> >> 1
> >> >> >> Gateway predef.: 192.168.1.4
> >> >> >> ===========================================================================
> >> >> >>
> >> >> >> And i have enabled IP routing on machine 2:
> >> >> >> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
> >> >> >> "IPEnableRouter"=dword:00000001
> >> >> >>
> >> >> >> Thanks, ManÃ©
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

Re: Router config with Vmachine and host

Sent: 09/28/2006
From: "Bill Grant" <not.available@online>
Message:

Echo request is all you should need for ping.

Netbios name resolution on a LAN usually works by LAN broadcast. Because
routers block these, it usually fails across routers. You will need to use
LMHOSTS entries or WINS to get Netbios name resolution across a router.

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

Show quoted text

> Well, sometimes we post and at the same time we already implementing other
> things.
> I've made it with no problem, and loopback in another subnet.
> Do you know what firewall settings do we have to disable/enable to make:
> a ping from the real machine to virtual machine (i've tried to enable echo
> requests but it didn't work)
> a ping from the real machine to a NetBIOS names (with firewall).
> Thanks for the help,
> greetings
>
>
> "Bill Grant" wrote:
>
>> I have had a look at Mitch Tulloch's article and I cannot see any
>> similarities between that and what you appear to be trying to do. The
>> network in the article uses four virtual machines (running on the same
>> host
>> machine), two of them configured as routers. Are you trying to configure
>> something similar using two vms and two "real" machines? I suggest that
>> you
>> study the diagram in the article carefully, especially the table of
>> default
>> gateway settings. Also be careful about how Mitch uses the word "host".
>> He
>> uses it in the networking sense, which is not the same as the general
>> usage
>> in virtual machine circles. For virtual machines, "host" refers to the
>> physical machine which runs the VPC or Virtual Server application.
>>
>> IP routing routes between IP subnets. If you enable IP routing on a
>> host
>> machine to route between the physical and the loopback networks, the NIC
>> and
>> the loopack adapter must be in different IP subnets.
>>
>>
>> "Amsps" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Hi!
>> > I was trying to implement this
>> > http://www.windowsdevcenter.com/pub/a/windows/2006/07/11/build-a-virtual-routed-network.html
>> > but with connection from local network (VPC) to the real machine
>> > without
>> > afecting its parameters, that's why I want loopback.
>> > Then I've made a route (or IPEnableRouter=1) from loopback to the real
>> > adapter.
>> > Well I've made it but with ping problems (although with all machines
>> > with
>> > echo ping enabled but firewall enabled). I've had to disable the
>> > firewall
>> > to
>> > make ping. And do you know how, with firewall enabled, can I ping to
>> > machine's NetBIOS names? I can't resolve NetBIOS names with firewall
>> > enabled!
>> > Thanks, Mané
>> >
>> > "Bill Grant" wrote:
>> >
>> >> The network configuration on the host does not make any sense at
>> >> all.
>> >> Why would you set up a loopback adapter and put it in the same IP
>> >> subnet
>> >> as
>> >> the real NIC? Why not just use the real NIC? Virtual Machine Network
>> >> Services allows a vm to access a network through the host's physical
>> >> NIC.
>> >> You only need a loopback adapter if you don't have a NIC, or if you
>> >> need
>> >> two
>> >> interfaces on the host. If you have two interfaces on the host, you
>> >> usually
>> >> want them to be in different IP subnets. In that case, you would
>> >> normally
>> >> use the host as the router, not a virtual machine.
>> >>
>> >> Your virtual router could work without any loopback adapters at
>> >> all.
>> >> You
>> >> would link the "host" side of the vm router to the physical NIC of the
>> >> host
>> >> machine (the default setting). This interface of the virtual router
>> >> would
>> >> be
>> >> in the same IP subnet as the host NIC. You would put the NIC on the
>> >> "guest"
>> >> side in Local Only. This NIC would be in the same IP subnet as the
>> >> second
>> >> XP
>> >> guest machine.
>> >>
>> >> I think that you are trying to make this more complicated than it
>> >> needs
>> >> to be. Could you tell us exactly what you are trying to achieve? How
>> >> you
>> >> configure the router depends on how you want the network to perform.
>> >>
>> >> "Amsps" <(email address - cut out)> wrote in message
>> >> news:(email address - cut out)...
>> >> > Hi.
>> >> > Talking about this setup:
>> >> > Host
>> >> > 192.168.1.3 dg blank (loopback adapter)
>> >> > 192.168.1.4 dg 192.168.1.3 (link to loopback)
>> >> > routing vm
>> >> > 192.168.0.2 dg blank (virtual network)
>> >> > other vm
>> >> > 192.168.0.1 dg 192.168.0.2 (virtual network)
>> >> > On the host, add a static route to send traffic for 192.168.0.0 to
>> >> > the
>> >> > vm router.
>> >> > 192.168.0.1 255.255.255.0 192.168.1.4 .
>> >> >
>> >> > I've configured like you said (portuguese):
>> >> >
>> >> > Host setup:
>> >> > Real network
>> >> > Sufixo DNS específico da ligação. :
>> >> > Autoconfiguracão de endereço IP . : 192.168.1.4
>> >> > Máscara de sub-rede . . . . . . . : 255.255.255.0
>> >> > Gateway predefinido . . . . . . . : 192.168.1.3
>> >> >
>> >> > Loopback:
>> >> > Sufixo DNS específico da ligação. :
>> >> > Endereço IP . . . . . . . . . . . : 192.168.1.3
>> >> > Máscara de sub-rede . . . . . . . : 255.255.255.0
>> >> > Gateway predefinido . . . . . . . :
>> >> >
>> >> > VM Router (Local Network)
>> >> > Adaptador ethernet Virtual Intel1:
>> >> > Sufixo DNS específico da ligação. :
>> >> > Endereço IP . . . . . . . . . . . : 192.168.0.2
>> >> > Máscara de sub-rede . . . . . . . : 255.255.255.0
>> >> > Gateway predefinido . . . . . . . :
>> >> >
>> >> > Other VM (Local Network)
>> >> > Adaptador ethernet Ligação de área local:
>> >> > Sufixo DNS específico da ligação. :
>> >> > Endereço IP . . . . . . . . . . . : 192.168.0.1
>> >> > Máscara de sub-rede . . . . . . . : 255.255.255.0
>> >> > Gateway predefinido . . . . . . . : 192.168.0.2
>> >> >
>> >> > You've said that local network link to loopback on host,
>> >> > but i don't think so, that's why there are local and loopback
>> >> > networks,
>> >> > IMHO.
>> >> > And that's why i think that i can't ping from VM router and Other
>> >> > VM,
>> >> > to
>> >> > host.
>> >> > Please feedback.
>> >> > Thanks, Mané
>> >> >
>> >> >
>> >> > "Bill Grant" wrote:
>> >> >
>> >> >> If you only want the virtual machines to see each other and the
>> >> >> host
>> >> >> (and not other machines on the host's network), you can simplify
>> >> >> things
>> >> >> and
>> >> >> you do not need the added static route. You make the vm router the
>> >> >> default
>> >> >> gateway for the loopback adapter.
>> >> >>
>> >> >> 192.168.1.3 dg 192.168.1.4
>> >> >> |
>> >> >> 192.168.1.4 dg blank
>> >> >> router vm
>> >> >> 192.168.0.2 dg blank
>> >> >> |
>> >> >> 192.168.0.1 dg 192.168.0.2
>> >> >>
>> >> >> "Bill Grant" <not.available@online> wrote in message
>> >> >> news:(email address - cut out)...
>> >> >> > The main problem is your default gateway settings. But just
>> >> >> > about
>> >> >> > everything about the setup is wrong.
>> >> >> >
>> >> >> > You do not need loopback adapters in vms. The virtual NIC
>> >> >> > links
>> >> >> > to
>> >> >> > the
>> >> >> > loopback adpater in the host.
>> >> >> >
>> >> >> > Are you trying to configure one vm as a router? Or do you want
>> >> >> > the
>> >> >> > host
>> >> >> > to route between its NIC and the vms in the loopback network?
>> >> >> >
>> >> >> > To use the host as a router, put the vms in the loopback
>> >> >> > network.
>> >> >> > Give
>> >> >> > them IP addresses in the same IP subnet as the loopback and with
>> >> >> > the
>> >> >> > loopback adapter as their default gateway.
>> >> >> >
>> >> >> > To use a vm as a router, put one of its NICs in a virtual
>> >> >> > network
>> >> >> > (Local Only) and one in a network connected to the host (loopback
>> >> >> > adapter). Put the other vm's NIC in local only.
>> >> >> >
>> >> >> > Host
>> >> >> > 192.168.1.3 dg blank (loopback adapter)
>> >> >> > |
>> >> >> > 192.168.1.4 dg 192.168.1.3 (link to loopback)
>> >> >> > routing vm
>> >> >> > 192.168.0.2 dg blank (virtual network)
>> >> >> > |
>> >> >> > other vm
>> >> >> > 192.168.0.1 dg 192.168.0.2 (virtual network)
>> >> >> >
>> >> >> > On the host, add a static route to send traffic for
>> >> >> > 192.168.0.0
>> >> >> > to
>> >> >> > the
>> >> >> > vm router.
>> >> >> >
>> >> >> > 192.168.0.1 255.255.255.0 192.168.1.4 .
>> >> >> >
>> >> >> > The vms will now be able to ping each other and the host.
>> >> >> >
>> >> >> > "Amsps" <(email address - cut out)> wrote in message
>> >> >> > news:(email address - cut out)...
>> >> >> >> Hi!
>> >> >> >> I need some help.
>> >> >> >> I have 2 VM with XP SP2.
>> >> >> >>
>> >> >> >> VMachine 1: Network:
>> >> >> >> Local
>> >> >> >> Settings: 192.168.0.1 MASK 255.255.255.0 Default Gateway
>> >> >> >> 192.168.0.2
>> >> >> >>
>> >> >> >> VMachine 2: Network:
>> >> >> >> Local
>> >> >> >> Settings: 192.168.0.2 MASK 255.255.255.0 Default Gateway
>> >> >> >> 192.168.0.2
>> >> >> >> Loopback Adapter
>> >> >> >> Settings: 192.168.1.4 MASK 255.255.255.0 Default Gateway
>> >> >> >> 192.168.1.4
>> >> >> >>
>> >> >> >> Real machine (host):
>> >> >> >> Loopback Adapter
>> >> >> >> Settings: 192.168.1.3 MASK 255.255.255.0 Default Gateway
>> >> >> >> 192.168.1.4
>> >> >> >>
>> >> >> >> Now, i can ping from host (192.168.1.3) to machine 2
>> >> >> >> (192.168.1.4).
>> >> >> >> I can ping from machine 1 (192.168.0.1) to machine 2 local
>> >> >> >> (192.168.0.2)
>> >> >> >> I can ping from machine 1 (192.168.0.1) to machine 2 loopback
>> >> >> >> (192.168.1.4)
>> >> >> >> I can ping from machine 2 to host (192.168.1.3).
>> >> >> >>
>> >> >> >> So, why can't I ping from machine 1 (192.168.0.1) to host
>> >> >> >> (192.168.1.3)????????
>> >> >> >>
>> >> >> >>
>> >> >> >> Machine 2's Route table
>> >> >> >> Rotas activas:
>> >> >> >> Destino de rede Mask Gateway
>> >> >> >> Interface
>> >> >> >> Métrica
>> >> >> >> 0.0.0.0 0.0.0.0 192.168.0.2
>> >> >> >> 192.168.0.2
>> >> >> >> 20
>> >> >> >> 0.0.0.0 0.0.0.0 192.168.1.4
>> >> >> >> 192.168.1.4
>> >> >> >> 20
>> >> >> >> 127.0.0.0 255.0.0.0 127.0.0.1
>> >> >> >> 127.0.0.1
>> >> >> >> 1
>> >> >> >> 192.168.0.0 255.255.255.0 192.168.0.2
>> >> >> >> 192.168.0.2
>> >> >> >> 20
>> >> >> >> 192.168.0.2 255.255.255.255 127.0.0.1
>> >> >> >> 127.0.0.1
>> >> >> >> 20
>> >> >> >> 192.168.0.255 255.255.255.255 192.168.0.2
>> >> >> >> 192.168.0.2
>> >> >> >> 20
>> >> >> >> 192.168.1.0 255.255.255.0 192.168.1.4
>> >> >> >> 192.168.1.4
>> >> >> >> 20
>> >> >> >> 192.168.1.4 255.255.255.255 127.0.0.1
>> >> >> >> 127.0.0.1
>> >> >> >> 20
>> >> >> >> 192.168.1.255 255.255.255.255 192.168.1.4
>> >> >> >> 192.168.1.4
>> >> >> >> 20
>> >> >> >> 224.0.0.0 240.0.0.0 192.168.0.2
>> >> >> >> 192.168.0.2
>> >> >> >> 20
>> >> >> >> 224.0.0.0 240.0.0.0 192.168.1.4
>> >> >> >> 192.168.1.4
>> >> >> >> 20
>> >> >> >> 255.255.255.255 255.255.255.255 192.168.0.2
>> >> >> >> 192.168.0.2
>> >> >> >> 1
>> >> >> >> 255.255.255.255 255.255.255.255 192.168.1.4
>> >> >> >> 192.168.1.4
>> >> >> >> 1
>> >> >> >> Gateway predef.: 192.168.1.4
>> >> >> >> ===========================================================================
>> >> >> >>
>> >> >> >> And i have enabled IP routing on machine 2:
>> >> >> >> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
>> >> >> >> "IPEnableRouter"=dword:00000001
>> >> >> >>
>> >> >> >> Thanks, Mané
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

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: