>I'd like to give my untainted first impression of Virtual PC, and in
>particular, the documentation on computer networking.
>
>First, Virtual PC looks like someone worked very hard to make it make
>sense. I've used VM Ware in the past. Only a few hours experience
>with Virtual PC, and it looks good so far.
>
>However, I do advanced research in computer networking, and I unable
>to get any of the virtual PC's to connect to the Internet. My
>configuration is the typical multiple-PCs-at-home-behind-Linksys-plus-
>cable-modem-with-DHCP.
>
>The documentation is weak. It is often the case when reading
>documentation from Microsoft about computer networking that I get the
>feeling that the person who wrote the documentation either
>
>(1) Doesn't know what s/he is talking about
>(2) Did not place enough effort in choosing terms/phrases that
>accurately reflect the model.
>
>In any case, I have copied the help text below. I might as well be
>talking to a baboon's ass while reading this stuff. It is meaningless
>to me.
>
>-Le Chaud Lapin-
>
>Option Description
>Not connected
> When this option is selected, networking is not available in the
>virtual machine. This option is recommended when the physical computer
>is not on a network, or if you do not plan to access the Internet
>through a virtual machine. This can prevent possible delays if the
>virtual machine software checks the network controller.
>
>Local
> This option provides networking support between virtual machines
>only. This means that the virtual machine will not have access to any
>network resources on the host operating system.
>
>Shared Networking
> The first virtual machine network card can be assigned to Shared
>Network (NAT). When this option is selected, the virtual machine is
>connected to a private network created by Virtual PC. The network
>includes a virtual DHCP server and a virtual network address
>translation server. The virtual machine is then able to access most
>TCP/IP-based resources that the host operating system can access. For
>more information about shared networking, see Managing shared
>networking for virtual machines.
>
>Network adapter on the physical computer
> When this option is selected, the virtual machine is connected
>directly to the currently selected network connection of the host
>operating system. The virtual machine will appear and behave like a
>separate physical computer on the same network. The networking
>configuration of the virtual machine is determined by the
>configuration of the network. For example, the configuration of the
>network will determine how an IP address is assigned to the virtual
>machine. If the network uses a DHCP server, an IP address is assigned
>dynamically to the virtual machine. Similarly, if the network uses
>static IP addresses, you must manually configure the virtual machine
>to use a static IP address, following the procedure specified in the
>documentation for the virtual machine operating system.
>
>Microsoft Loopback Adapter
> If you want to create a more complex network environment on a single
>physical computer, without installing multiple physical network cards,
>you can install multiple instances of Microsoft Loopback Adapter on
>the host operating system. For more information about Microsoft
>Loopback Adapter, see Extending networking capabilities for virtual
>machines.

> Like Steve, I really can't see what you find difficult about it. It does
> not work the same way as VMWare. Perhaps your problem is that you are trying
> to make it work the way VMWare does.
>
> The setup you describe for your home network is almost identical to mine
> (apart from a D-Link rather than Linksys router). When I install a vm it
> works with the default config. The NIC in the VM links to the physical NIC
> in the host machine. When I boot the vm for the first time it gets its
> network config from DHCP on the router.
>

> On Apr 14, 6:35 pm, "Bill Grant" <not.available@online> wrote:
> > Like Steve, I really can't see what you find difficult about it. It does
> > not work the same way as VMWare. Perhaps your problem is that you are trying
> > to make it work the way VMWare does.
> >
> > The setup you describe for your home network is almost identical to mine
> > (apart from a D-Link rather than Linksys router). When I install a vm it
> > works with the default config. The NIC in the VM links to the physical NIC
> > in the host machine. When I boot the vm for the first time it gets its
> > network config from DHCP on the router.
> >
>
> Thanks for both of your replies. It works now. I suspect it was
> because I turned of Zone Alarm on physical PC, but not sure and have
> not checked yet.
>
> However, I stand by what I said. I never learned VM Ware well enough
> to even remember what was done. Now that it works, I can say to
> someone else who tries to use VPC to do what I done.
>
> The problem with the documentation is that, IMO, it's meaningless. I
> have been working with computer networks for about 20 years, doing
> research beyond IPv6, and just finished writing my second NDIS
> driver. None of this experience helped me solve my problem. I had to
> guess, because the documentation is vague.
>
> I would also like to point out that, if I were to spend a couple of
> months working with VPC, the fuzzies would go away, but not because
> the documentation improved.
>
> -Le Chaud Lapin-
>
>

> On 14 Apr 2007 13:10:04 -0700, "Le Chaud Lapin" <(email address - cut out)>
> wrote:
>
>>I'd like to give my untainted first impression of Virtual PC, and in
>>particular, the documentation on computer networking.
>>
>>First, Virtual PC looks like someone worked very hard to make it make
>>sense. I've used VM Ware in the past. Only a few hours experience
>>with Virtual PC, and it looks good so far.
>>
>>However, I do advanced research in computer networking, and I unable
>>to get any of the virtual PC's to connect to the Internet. My
>>configuration is the typical multiple-PCs-at-home-behind-Linksys-plus-
>>cable-modem-with-DHCP.
>>
>>The documentation is weak. It is often the case when reading
>>documentation from Microsoft about computer networking that I get the
>>feeling that the person who wrote the documentation either
>>
>>(1) Doesn't know what s/he is talking about
>>(2) Did not place enough effort in choosing terms/phrases that
>>accurately reflect the model.
>>
>>In any case, I have copied the help text below. I might as well be
>>talking to a baboon's ass while reading this stuff. It is meaningless
>>to me.
>>
>>-Le Chaud Lapin-
>>
>>Option Description
>>Not connected
>> When this option is selected, networking is not available in the
>>virtual machine. This option is recommended when the physical computer
>>is not on a network, or if you do not plan to access the Internet
>>through a virtual machine. This can prevent possible delays if the
>>virtual machine software checks the network controller.
>>
>>Local
>> This option provides networking support between virtual machines
>>only. This means that the virtual machine will not have access to any
>>network resources on the host operating system.
>>
>>Shared Networking
>> The first virtual machine network card can be assigned to Shared
>>Network (NAT). When this option is selected, the virtual machine is
>>connected to a private network created by Virtual PC. The network
>>includes a virtual DHCP server and a virtual network address
>>translation server. The virtual machine is then able to access most
>>TCP/IP-based resources that the host operating system can access. For
>>more information about shared networking, see Managing shared
>>networking for virtual machines.
>>
>>Network adapter on the physical computer
>> When this option is selected, the virtual machine is connected
>>directly to the currently selected network connection of the host
>>operating system. The virtual machine will appear and behave like a
>>separate physical computer on the same network. The networking
>>configuration of the virtual machine is determined by the
>>configuration of the network. For example, the configuration of the
>>network will determine how an IP address is assigned to the virtual
>>machine. If the network uses a DHCP server, an IP address is assigned
>>dynamically to the virtual machine. Similarly, if the network uses
>>static IP addresses, you must manually configure the virtual machine
>>to use a static IP address, following the procedure specified in the
>>documentation for the virtual machine operating system.
>>
>>Microsoft Loopback Adapter
>> If you want to create a more complex network environment on a single
>>physical computer, without installing multiple physical network cards,
>>you can install multiple instances of Microsoft Loopback Adapter on
>>the host operating system. For more information about Microsoft
>>Loopback Adapter, see Extending networking capabilities for virtual
>>machines.
>
> Those are the networking options you have with a VM. I really don't
> see how they could be made more explanatory.
>
> If you have DHCP and you want your VM to be on your network like a
> physical PC, you'd simply select the network adaptor on the PC running
> the VM that is connected to the network...the 4th option.
>
> ----------- ---- --- -- - - - -
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/

> Installed VPC, Installed Guest OS, Installed VM Additions, Turned on DCHP
> everything works.
>
> Guest OS's tested - DOS with packet driver, Win 3.11, Win 98 SE, Win XP MCE,
> Ubuntu 6.06.... all work the same haven't had to do anything to any OS to get
> them to work. The only othe rOS I own that I haven't tried is Win 95 but I'm
> sure it would be the same.

> On 14 Apr 2007 17:46:07 -0700, "Le Chaud Lapin" <(email address - cut out)>
> wrote:
> >However, I stand by what I said. I never learned VM Ware well enough
> >to even remember what was done. Now that it works, I can say to
> >someone else who tries to use VPC to do what I done.
>
> >The problem with the documentation is that, IMO, it's meaningless. I
> >have been working with computer networks for about 20 years, doing
> >research beyond IPv6, and just finished writing my second NDIS
> >driver. None of this experience helped me solve my problem. I had to
> >guess, because the documentation is vague.
>
> How vague can it be when it correctly spells out exactly what will
> happen when you select any of the available optionsin the network
> dialogue?

>
>However, I stand by what I said. I never learned VM Ware well enough
>to even remember what was done. Now that it works, I can say to
>someone else who tries to use VPC to do what I done.
>
>The problem with the documentation is that, IMO, it's meaningless. I
>have been working with computer networks for about 20 years, doing
>research beyond IPv6, and just finished writing my second NDIS
>driver. None of this experience helped me solve my problem. I had to
>guess, because the documentation is vague.
>

> On Apr 15, 3:48 pm, Bo Berglund <(email address - cut out)> wrote:
> > On 14 Apr 2007 17:46:07 -0700, "Le Chaud Lapin" <(email address - cut out)>
> > wrote:
>
> > >However, I stand by what I said. I never learned VM Ware well enough
> > >to even remember what was done. Now that it works, I can say to
> > >someone else who tries to use VPC to do what I done.
> >
> > >The problem with the documentation is that, IMO, it's meaningless. I
> > >have been working with computer networks for about 20 years, doing
> > >research beyond IPv6, and just finished writing my second NDIS
> > >driver. None of this experience helped me solve my problem. I had to
> > >guess, because the documentation is vague.
> >
> > How vague can it be when it correctly spells out exactly what will
> > happen when you select any of the available optionsin the network
> > dialogue?
>
> It's vague because the language it uses is meaningless to an expert.
> It should be more detailed. The reason is simple: if it doesn't work,
> the novice is going to have to ask an expert anyway. Evidence of that
> proliferates throughout this newsgroup. And if the documentation is
> vague, not even an expert in computer networking (like myself) will be
> able to infer what the problem might be, because he does not know what
> is going on.
>
> The best thing to do in these situations is to provide documentation
> is is specific, a little more detailed than it is, and not try to save
> us ignorant people from being overwhelmed. That way, at least some
> of us can infer what is going on and fix the problem.
>
> -Le Chaud Lapin-