Network Connectivity issue

[DarthMuppet]

Installed VPC 2007 SP1, first time i've used any of the VPC tools. I have an
unattended build based on a DOS boot disk which cannot connect to the server
to start the process - I get an error 53, path not found (so the driver stack
is OK), the virtual NIC in the VM is set to Shared netowrking (NAT), which I
would have expected to work, but it doesn't. I know I have an IP address, as
i'd not get as far as error 53 otherwise.

I think the problem is WINS related - if the network client (MSDOS client
v3.0, basic redirector) does not get the correct WINS servers (the host has
them correctly, and the host can see the build server). If anyone can shed
any light on that, i'd be grateful.

Now to my real question. During this exercise, i read the help file, and it
describes the VM NIC config named "Network adapter on the physical computer",
which would certainly resolve my issue, as my regular DHCP server would be
used, thus guaranteeing everything being correct. Unfortunately, I don't have
that option available in the drop-down - I have Shared, Local Only and Not
Connected. Can anyone explain why "Network adapter on the physical computer"
is not in my list? Any ideas how to get it in there? Host is XP SP2 in a
domain environment.

TIA

DM

[Bo Berglund]

On Thu, 22 Jan 2009 02:40:01 -0800, DarthMuppet
<Darth...@discussions.microsoft.com> wrote:

>Now to my real question. During this exercise, i read the help file, and it
>describes the VM NIC config named "Network adapter on the physical computer",
>which would certainly resolve my issue, as my regular DHCP server would be
>used, thus guaranteeing everything being correct. Unfortunately, I don't have
>that option available in the drop-down - I have Shared, Local Only and Not
>Connected. Can anyone explain why "Network adapter on the physical computer"
>is not in my list? Any ideas how to get it in there? Host is XP SP2 in a
>domain environment.
>

On the host open the propereties of the network card.
THen in the list of services locate the item "Virtual Machine Network
Services". If the checkbox is not checked then check it. THis should
be the solution.

Biut if it is checked and it does not show up anyway in your combobox
in VPC2007 then you might have to update the driver for your network
card (on the host). Probably it is not compatible with the VMNS and so
it cannot use this card.

--

Bo Berglund (Sweden)

[DarthMuppet]

Updating the NIC driver seems to have done the trick - well, at least the NIC
appears in that list, but the other problem remains. Having checked with
Wireshark, I can see that the DHCP offer comes with WINS / NBNS servers, but
when the DOS client tries to resolve my server name, it only broadcasts to
the local subnet, and fails. I know the client is set up correctly, as i can
build physical hardware on the same subnet with the same image (in fact, i
can build a VMware guest on the same host PC with the same image), so i
conclude that the VPC is not passing the WINS configuration to the guest OS.
I'll try it on a clean machine.

Cheers!

DM