> I am running windows server 2003 R2 with Virtual server 2005 SP1. On this
> server we are running one instance of a virtual server that is running a
> windows 2003 R2 domain controller. When the host operating system is
> restarted an error is logged saying "<server> could not initialize the
> emulated Ethernet controller.". After that the network card on the virtual
> server doesn't show up any longer. Through trial and error I've discovered
> that if I change the MAC address the virtual server will restart just fine
> however if I reuse any of the MAC addresses that have failed in the past I
> have the same problem. I've checked throughout the network and these MAC
> addresses aren't being used by any other devices and I have other servers
> that are set up similar to this one with no issues so I don't understand why
> I'm having this problem.
>
> Does anyone have insight to what might be causing the problem?
>
> Thanks

> On 14 Apr, 23:28, Paul <(email address - cut out)> wrote:
> > I am running windows server 2003 R2 with Virtual server 2005 SP1. On this
> > server we are running one instance of a virtual server that is running a
> > windows 2003 R2 domain controller. When the host operating system is
> > restarted an error is logged saying "<server> could not initialize the
> > emulated Ethernet controller.". After that the network card on the virtual
> > server doesn't show up any longer. Through trial and error I've discovered
> > that if I change the MAC address the virtual server will restart just fine
> > however if I reuse any of the MAC addresses that have failed in the past I
> > have the same problem. I've checked throughout the network and these MAC
> > addresses aren't being used by any other devices and I have other servers
> > that are set up similar to this one with no issues so I don't understand why
> > I'm having this problem.
> >
> > Does anyone have insight to what might be causing the problem?
> >
> > Thanks
>
> Hello Paul,
> you can check my recent messages about a very similar (same symptom,
> indeed) issue.
> Try what I've tried (reinstall the NIC drivers, disable other NICs if
> you have more than one, check Microsoft KB555629, disable a few
> settings on the NIC): nothing worked for me, maybe you'll be more
> lucky!
> Let us know...
>
> k
>

> My network card is an intel(R) PRO/1000 MT Network Connection in a Dell
> 1600SC. This is kind of an old system so maybe that is the problem but I'm
> also seeing this in a "newer" Dell 1750 with a Broadcom NetXtreme Gigabit
> Ethernet network card in it.
>
> I'll check the knowledge base and see what I can find there.
>
> "karamatic" wrote:
>
> > On 14 Apr, 23:28, Paul <(email address - cut out)> wrote:
> > > I am running windows server 2003 R2 with Virtual server 2005 SP1. On this
> > > server we are running one instance of a virtual server that is running a
> > > windows 2003 R2 domain controller. When the host operating system is
> > > restarted an error is logged saying "<server> could not initialize the
> > > emulated Ethernet controller.". After that the network card on the virtual
> > > server doesn't show up any longer. Through trial and error I've discovered
> > > that if I change the MAC address the virtual server will restart just fine
> > > however if I reuse any of the MAC addresses that have failed in the past I
> > > have the same problem. I've checked throughout the network and these MAC
> > > addresses aren't being used by any other devices and I have other servers
> > > that are set up similar to this one with no issues so I don't understand why
> > > I'm having this problem.
> > >
> > > Does anyone have insight to what might be causing the problem?
> > >
> > > Thanks
> >
> > Hello Paul,
> > you can check my recent messages about a very similar (same symptom,
> > indeed) issue.
> > Try what I've tried (reinstall the NIC drivers, disable other NICs if
> > you have more than one, check Microsoft KB555629, disable a few
> > settings on the NIC): nothing worked for me, maybe you'll be more
> > lucky!
> > Let us know...
> >
> > k
> >

> good news... It looks like I know how to fix the problem that we are havin=
> with some of our virtual servers not restarting on reboot without changing=
> the MAC address. The issue seems to be that the network driver was updated=
> after Virtual Server was installed and configured. To fix the problem I
> uninstalled virtual server, rebooted, deleted everything that had to do wi=
> virtual server under the following directory=94 C:\Document and Settings\A=
> Users\Application Data=94, reinstalled virtual server and finally recreate=
> virtual servers. It takes a little while to do but I=92m glad that there i=
> finally a solution to the problem."Paul" wrote:
> > My network card is an =A0intel(R) PRO/1000 MT Network Connection in a De=
> > 1600SC. This is kind of an old system so maybe that is the problem but I=
> > also seeing this in a "newer" Dell 1750 with a Broadcom NetXtreme Gigabi=
> > Ethernet network card in it.
>
> > I'll check the knowledge base and see what I can find there.
>
> > "karamatic" wrote:
>
> > > On 14 Apr, 23:28, Paul <(email address - cut out)> wrote:
> > > > I am running windows server 2003 R2 with Virtual server 2005 SP1. On=
> > > > server we are running one instance of a virtual server that is runni=
> > > > windows 2003 R2 domain controller. When the host operating system is=
> > > > restarted an error is logged saying "<server> could not initialize t=
> > > > emulated Ethernet controller.". After that the network card on the v=
> > > > server doesn't show up any longer. Through trial and error I've disc=
> > > > that if I change the MAC address the virtual server will restart jus=
> > > > however if I reuse any of the MAC addresses that have failed in the =
> > > > have the same problem. I've checked throughout the network and these=
> > > > addresses aren't being used by any other devices and I have other se=
> > > > that are set up similar to this one with no issues so I don't unders=
> > > > I'm having this problem.
>
> > > > Does anyone have insight to what might be causing the problem?
>
> > > > Thanks
>
> > > Hello Paul,
> > > you can check my recent messages about a very similar (same symptom,
> > > indeed) issue.
> > > Try what I've tried (reinstall the NIC drivers, disable other NICs if
> > > you have more than one, check Microsoft KB555629, disable a few
> > > settings on the NIC): nothing worked for me, maybe you'll be more
> > > lucky!
> > > Let us know...
>
> > > k