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

* Micrsolf VM Java problems with Homestead web builder( new computer
* VPC7 For Macintosh Can"t get on Internet anymore
* Virtual Server or Windows Server on Virtual PC
* Virtual PC and Office 2004 for Mac
* Mini newsgroup FAQ for the week of 10/30/2005
* pentium-D dual core
* Installing RedHat Linux 7.1 on Virtual PC
* new version or update?
* 2 network cards
* Problem installing OS from DVD.
* Virtual PC freezes on startup
* Virtual PC Media
* Using Netware Client 3.40 with Windows 98 SE in Virtual PC 2004
* MS Access 97
* VPC screen freezes after restore
* Virtual PC and PAE
* VPC machine to tray?
* Cannot install on new PowerBook G4 15" 1.67 CPU
* Boot Issues
* Unixware 7

Add Solution

Making Guest PCs talk to HOST PC

Source: microsoft.public.virtualpc
Sent: 10/30/2005
From: Ajai Kumaar
Message:

Hi All

I have little experience with Virtual PC 2004 and would appreciate step by
step answers to the following scenario question.

1. I have VPC 2004 running on Windows XP SP2. The HOST machine has a
192.168.1.100 IP Address and connects to a DSL Router. The external interface
of the DSL Router has the Internet Facing IP Address.

2. I have configured four Virtual Machines and they are assigned IP
Addresses 10.0.0.10; 10.0.0.20; 10.0.0.30 and 10.0.0.150.

3. The Guest Machines can all ping each other.. no problems. They are all
configurted to use the HOST MACHINE'S NIC.

4. Each Guest machine is also configured with an MS Loopback Adapter.

5. The HOST machine is also configured with an MS Loopback Adapter.

THis is where the questions comes:

Q1. What IP Addresses can I assign the MS Loopback Adapters on the guest
machines so that they can all ping the host?

Q2. I have tried giving them the 192.168.131.1 to 192.168.1.254 range, but I
am not sure what should be specified in the DEFAULT GATEWAY. This setting
does not work and I am unable to get the host and the guests to PING each
other.

Q3. I am NOT INTERESTED in getting the Guest machines to have Internet
Access. All I want to do is get the guest machines to be able to talk to the
host machine. Any config that get sme to do that will help, as long as it
does not break my host's ability to get to the Internet.

4. Is there a document from Microsoft or others that has a tutorial like
description of what steps one needs to take to get this done? I am willing to
learn if someone can point me to the right links. Sadly, Microsoft does not
have such scenario info on their web site. If they do, I was unable to find
it and would appriate if someone can point me to it.

The following is a reference in the help file, that I used:

====================================================
You can use any TCP/IP address, but it is best to choose one from a reserved
range of private TCP/IP addresses. For example, TCP/IP addresses of the form
192.168.x.y, where x is a value between 0 and 255 and y is a value between 1
and 254, are private. The value you choose for x must be the same on the host
operating system and each guest operating system that is to be part of this
virtual network. If your primary Ethernet connection uses one of these
private addresses, you must choose a different value for x to assign to
Microsoft Loopback Adapter.
====================================================

Thank you and best regards
--
Ajai Kumaar
Consultant

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Making Guest PCs talk to HOST PC

Sent: 10/31/2005
From: Paul Adare <(email address - cut out)>
Message:

In article <(email address - cut out)>, in the
microsoft.public.virtualpc news group, =?Utf-8?B?QWphaSBLdW1hYXI=?=
<(email address - cut out)> says...

You've got two adapters in each guest, the Intel one that is emulated
and the loopback that you've installed.

Reconfigure them to use the loopback in the host.

Remove the loopback adapters from the guests. They won't accomplish
anything.

Configure the host's loopback adapter to use an IP address in the
10.0.0.x range. Make sure that you're using the same subnet mask in the
host as you are in the guests.

None. Remove the loopback from the guests.

If all you need is access to the host you don't need a default gateway.

As above. Assign an appropriate IP address to the host's loopback,
remove the loopback from the guests.

--
Paul Adare
MVP - Windows - Virtual Machine
http://www.identit.ca/blogs/paul/
"The English language, complete with irony, satire, and sarcasm, has
survived for centuries without smileys. Only the new crop of modern
computer geeks finds it impossible to detect a joke that is not clearly
labeled as such."
Ray Shea

Show quoted text

> Hi All
>
> I have little experience with Virtual PC 2004 and would appreciate step by
> step answers to the following scenario question.
>
> 1. I have VPC 2004 running on Windows XP SP2. The HOST machine has a
> 192.168.1.100 IP Address and connects to a DSL Router. The external interface
> of the DSL Router has the Internet Facing IP Address.
>
> 2. I have configured four Virtual Machines and they are assigned IP
> Addresses 10.0.0.10; 10.0.0.20; 10.0.0.30 and 10.0.0.150.
>
> 3. The Guest Machines can all ping each other.. no problems. They are all
> configurted to use the HOST MACHINE'S NIC.
>
> 4. Each Guest machine is also configured with an MS Loopback Adapter.
>
> 5. The HOST machine is also configured with an MS Loopback Adapter.
>
> THis is where the questions comes:
>
> Q1. What IP Addresses can I assign the MS Loopback Adapters on the guest
> machines so that they can all ping the host?
>
> Q2. I have tried giving them the 192.168.131.1 to 192.168.1.254 range, but I
> am not sure what should be specified in the DEFAULT GATEWAY. This setting
> does not work and I am unable to get the host and the guests to PING each
> other.
>
> Q3. I am NOT INTERESTED in getting the Guest machines to have Internet
> Access. All I want to do is get the guest machines to be able to talk to the
> host machine. Any config that get sme to do that will help, as long as it
> does not break my host's ability to get to the Internet.

Re: Making Guest PCs talk to HOST PC

Sent: 10/31/2005
From: Ajai Kumaar
Message:

Hi Paul

Thanks for the reply. Here's what I have now.

The four GUEST VPCs have IP Addreses of 10.0.0.10, 10.0.0.20, 10.0.0.30 and
10.0.0.150.
They ALL have a SUBNET MASK of 255.0.0.0
They ALL have a Default Gateway of 10.0.0.1

I then changed the IP on the HOST MS Loopback to 10.0.0.50, with a SUBNET
MASK of 255.0.0.0 and NO DEFAULT GATEWAY (as you suggested)

I still cannot PING from GUEST to HOST.
I still cannot PING from HOST to GUEST.

The ROUTE PRINT Command from the HOST looks like this:
======================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 56 c0 00 08 ...... VMware Virtual Ethernet Adapter (Network
Address Translation (NAT) for VMnet8)
0x3 ...00 50 56 c0 00 01 ...... VMware Virtual Ethernet Adapter (basic
host-only support for VMnet1)
0x40004 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter - Virtual
Machine Network Services Driver
0x40007 ...00 50 2c 06 4a c6 ...... Realtek RTL8139/810X Family PCI Fast
Ethernet NIC - Packet Scheduler Miniport
======================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.100 20
10.0.0.0 255.0.0.0 10.0.0.50 10.0.0.50 30
10.0.0.50 255.255.255.255 127.0.0.1 127.0.0.1 30
10.255.255.255 255.255.255.255 10.0.0.50 10.0.0.50 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.0.0 255.255.0.0 169.254.25.142 169.254.25.142 30
169.254.0.0 255.255.0.0 169.254.218.201 169.254.218.201 30
169.254.25.142 255.255.255.255 127.0.0.1 127.0.0.1 30
169.254.218.201 255.255.255.255 127.0.0.1 127.0.0.1 30
169.254.255.255 255.255.255.255 169.254.25.142 169.254.25.142 30
169.254.255.255 255.255.255.255 169.254.218.201 169.254.218.201 30
192.168.1.0 255.255.255.0 192.168.1.100 192.168.1.100 20
192.168.1.100 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.1.255 255.255.255.255 192.168.1.100 192.168.1.100 20
224.0.0.0 240.0.0.0 10.0.0.50 10.0.0.50 30
224.0.0.0 240.0.0.0 169.254.25.142 169.254.25.142 30
224.0.0.0 240.0.0.0 169.254.218.201 169.254.218.201 30
224.0.0.0 240.0.0.0 192.168.1.100 192.168.1.100 20
255.255.255.255 255.255.255.255 10.0.0.50 10.0.0.50 1
255.255.255.255 255.255.255.255 169.254.25.142 169.254.25.142 1
255.255.255.255 255.255.255.255 169.254.218.201 169.254.218.201 1
255.255.255.255 255.255.255.255 192.168.1.100 192.168.1.100 1
Default Gateway: 192.168.1.1
===================================
Persistent Routes:
None

Also, the ROUTE PRINT from the GUEST looks like this:

=================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 03 ff 13 4a c6 ...... Intel 21140-Based PCI Fast Ethernet
Adapter
(Generic) - Packet Scheduler Miniport
================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 10.0.0.1 10.0.0.150 20
10.0.0.0 255.0.0.0 10.0.0.150 10.0.0.150 20
10.0.0.150 255.255.255.255 127.0.0.1 127.0.0.1 20
10.255.255.255 255.255.255.255 10.0.0.150 10.0.0.150 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
224.0.0.0 240.0.0.0 10.0.0.150 10.0.0.150 20
255.255.255.255 255.255.255.255 10.0.0.150 10.0.0.150 1
Default Gateway: 10.0.0.1
Persistent Routes:
None
===============================
--
Ajai Kumaar
Consultant

"Paul Adare" wrote:

Show quoted text

> In article <(email address - cut out)>, in the
> microsoft.public.virtualpc news group, =?Utf-8?B?QWphaSBLdW1hYXI=?=
> <(email address - cut out)> says...
>
> > Hi All
> >
> > I have little experience with Virtual PC 2004 and would appreciate step by
> > step answers to the following scenario question.
> >
> > 1. I have VPC 2004 running on Windows XP SP2. The HOST machine has a
> > 192.168.1.100 IP Address and connects to a DSL Router. The external interface
> > of the DSL Router has the Internet Facing IP Address.
> >
> > 2. I have configured four Virtual Machines and they are assigned IP
> > Addresses 10.0.0.10; 10.0.0.20; 10.0.0.30 and 10.0.0.150.
>
> You've got two adapters in each guest, the Intel one that is emulated
> and the loopback that you've installed.
> >
> > 3. The Guest Machines can all ping each other.. no problems. They are all
> > configurted to use the HOST MACHINE'S NIC.
>
> Reconfigure them to use the loopback in the host.
> >
> > 4. Each Guest machine is also configured with an MS Loopback Adapter.
>
> Remove the loopback adapters from the guests. They won't accomplish
> anything.
> >
> > 5. The HOST machine is also configured with an MS Loopback Adapter.
>
> Configure the host's loopback adapter to use an IP address in the
> 10.0.0.x range. Make sure that you're using the same subnet mask in the
> host as you are in the guests.
>
> >
> > THis is where the questions comes:
> >
> > Q1. What IP Addresses can I assign the MS Loopback Adapters on the guest
> > machines so that they can all ping the host?
>
> None. Remove the loopback from the guests.
>
> >
> > Q2. I have tried giving them the 192.168.131.1 to 192.168.1.254 range, but I
> > am not sure what should be specified in the DEFAULT GATEWAY. This setting
> > does not work and I am unable to get the host and the guests to PING each
> > other.
>
> If all you need is access to the host you don't need a default gateway.
>
> >
> > Q3. I am NOT INTERESTED in getting the Guest machines to have Internet
> > Access. All I want to do is get the guest machines to be able to talk to the
> > host machine. Any config that get sme to do that will help, as long as it
> > does not break my host's ability to get to the Internet.
>
> As above. Assign an appropriate IP address to the host's loopback,
> remove the loopback from the guests.
>
>
>
> --
> Paul Adare
> MVP - Windows - Virtual Machine
> http://www.identit.ca/blogs/paul/
> "The English language, complete with irony, satire, and sarcasm, has
> survived for centuries without smileys. Only the new crop of modern
> computer geeks finds it impossible to detect a joke that is not clearly
> labeled as such."
> Ray Shea
>

Re: Making Guest PCs talk to HOST PC

Sent: 11/01/2005
From: Paul Adare <(email address - cut out)>
Message:

In article <(email address - cut out)>, in the
microsoft.public.virtualpc news group, =?Utf-8?B?QWphaSBLdW1hYXI=?=
<(email address - cut out)> says...

Do you even have a router? If not then you don't need the default
gateway set here, though that shouldn't be causing any problems.

As I said in my original response you don't need and should not have a
loopback adapter installed in your guests. What adapter in your guests
are the above IP addresses assigned to?

If you've assigned the IP addresses to the loopback in your guests this
will definitely not work.

Other things to check:

1. Make sure that your guests are actually using the host's loopback
adapter.
2. Firewalls on the host or guests?

--
Paul Adare
MVP - Windows - Virtual Machine
http://www.identit.ca/blogs/paul/
"The English language, complete with irony, satire, and sarcasm, has
survived for centuries without smileys. Only the new crop of modern
computer geeks finds it impossible to detect a joke that is not clearly
labeled as such."
Ray Shea

Show quoted text

> Thanks for the reply. Here's what I have now.
>
> The four GUEST VPCs have IP Addreses of 10.0.0.10, 10.0.0.20, 10.0.0.30 and
> 10.0.0.150.
> They ALL have a SUBNET MASK of 255.0.0.0
> They ALL have a Default Gateway of 10.0.0.1
>
> I then changed the IP on the HOST MS Loopback to 10.0.0.50, with a SUBNET
> MASK of 255.0.0.0 and NO DEFAULT GATEWAY (as you suggested)
>
> I still cannot PING from GUEST to HOST.
> I still cannot PING from HOST to GUEST.

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: