Every time I setup a Windows XP Pro Guest under Server 2008 the network
fails on the guest PC with a "failed to start" error listed under the device
manager. I can get it to work by setting the network to NAT mode then
switching it after the machine boots up, however this is not a good solution
as I must manually add the IP information everytime I reboot the machine
(physical or guest)



Is there any solution for this?

On Fri, 26 Dec 2008 13:36:01 -0800, Cold_Realms
<Cold_Realms@xxxxxx> wrote:

> Every time I setup a Windows XP Pro Guest under Server 2008 the network
>fails on the guest PC with a "failed to start" error listed under the device
>manager. I can get it to work by setting the network to NAT mode then
>switching it after the machine boots up, however this is not a good solution
>as I must manually add the IP information everytime I reboot the machine
>(physical or guest)
>
>Is there any solution for this?

What virtualization software are you using?
-VirtualPC 2007?
-VirtualServer 2005?
-Hyper-V?
-Some other brand?

Things like this matter when trying to answer...

(This is the newsgroup for VirtualPC (2007 nowadays) but questions
concerning the other systems have been popping up now and then so it
is best to always describe what you are running)

--

Bo Berglund (Sweden)

Sorry , that's what I get for assuming.

Yes I am running Virtual PC 2007 Sp1.

On Fri, 26 Dec 2008 22:52:33 +0100, Bo Berglund <boberglund@xxxxxx>
wrote:

>On Fri, 26 Dec 2008 13:36:01 -0800, Cold_Realms
><Cold_Realms@xxxxxx> wrote:
>

>>> Every time I setup a Windows XP Pro Guest under Server 2008 the network
>>>fails on the guest PC with a "failed to start" error listed under the device
>>>manager. I can get it to work by setting the network to NAT mode then
>>>switching it after the machine boots up, however this is not a good solution
>>>as I must manually add the IP information everytime I reboot the machine
>>>(physical or guest)
>>>
>>>Is there any solution for this?

>>
>>What virtualization software are you using?
>>-VirtualPC 2007?
>>-VirtualServer 2005?
>>-Hyper-V?
>>-Some other brand?
>>
>>Things like this matter when trying to answer...
>>
>>(This is the newsgroup for VirtualPC (2007 nowadays) but questions
>>concerning the other systems have been popping up now and then so it
>>is best to always describe what you are running)

>Sorry , that's what I get for assuming.
>Yes I am running Virtual PC 2007 Sp1.

All right, then in the VPC console, Settings for the virtual machine,
what did you have as the networking option before you changed to NAT?

I am assuming you used the default, which is to use the NIC on the
host system. In that case what brand/model of NIC do you use on the
host?

Another question: your Windows Sever 2008, is it the 32 or 64 bit
version?

And: Do you have the very latest NIC drivers on your host?

--

Bo Berglund (Sweden)

Yes the setting i need and the one that causes the issue is to use the
default which is use the nic on the host.

The drivers are up to date as of last week. It is a realtek RTL 8139.

I am using the 32 bit version of both host and guest.