I'm running into a problem with my Virtual Server. My host is a member
server. I have 5 guest. 1 Linux server, 4 windows 2003 server. One of the
4 guest server is a DC.

I just noticed today that if I'm not on the local network which has a
physical DC I can't get the Virtual services started and I can't start the
Guest. I guess I thought the authentication info would be cache from
previous login and it would start until the DC comes up.

Here is what I've tried so far without any luck.

1. I logged into locally to the host. Still can't start services.
2. I also changed the guest to start with a local account as oppose to a
domain account. That didn't work, so I just unchecked the box.
3. I changed the Virtual server service to start with local logon instead of
Network Services.

Still doesn't work unless I'm connected to the local network with the
physical domain.

This server will eventuall be in its own subnet and needs to start without
being on the current network.

Virtual machines work just like physical ones. When you start a member
server it tries to contact a DC. That is why it is recommended that you
don't make a host a member of a domain which has its DC as a vm running on
that host. The DC can't possibly be running when the host boots up.

"Jeff Viola" <JeffViola@discussions.microsoft.com> wrote in message
news04B258F-E351-4F5F-8945-0C0320B7CC5D@microsoft.com...
> I'm running into a problem with my Virtual Server. My host is a member
> server. I have 5 guest. 1 Linux server, 4 windows 2003 server. One of
> the
> 4 guest server is a DC.
>
> I just noticed today that if I'm not on the local network which has a
> physical DC I can't get the Virtual services started and I can't start the
> Guest. I guess I thought the authentication info would be cache from
> previous login and it would start until the DC comes up.
>
> Here is what I've tried so far without any luck.
>
> 1. I logged into locally to the host. Still can't start services.
> 2. I also changed the guest to start with a local account as oppose to a
> domain account. That didn't work, so I just unchecked the box.
> 3. I changed the Virtual server service to start with local logon instead
> of
> Network Services.
>
> Still doesn't work unless I'm connected to the local network with the
> physical domain.
>
> This server will eventuall be in its own subnet and needs to start without
> being on the current network.
>
>

I agree. Now when I login in locally I still have the same problem. Are
you saying that I should remove this from the domain and then reinstall MS
Virtual R2 SP1 again. Will that resolve it?

Jeff

"Bill Grant" wrote:

> Virtual machines work just like physical ones. When you start a member
> server it tries to contact a DC. That is why it is recommended that you
> don't make a host a member of a domain which has its DC as a vm running on
> that host. The DC can't possibly be running when the host boots up.
>
> "Jeff Viola" <JeffViola@discussions.microsoft.com> wrote in message
> news04B258F-E351-4F5F-8945-0C0320B7CC5D@microsoft.com...
> > I'm running into a problem with my Virtual Server. My host is a member
> > server. I have 5 guest. 1 Linux server, 4 windows 2003 server. One of
> > the
> > 4 guest server is a DC.
> >
> > I just noticed today that if I'm not on the local network which has a
> > physical DC I can't get the Virtual services started and I can't start the
> > Guest. I guess I thought the authentication info would be cache from
> > previous login and it would start until the DC comes up.
> >
> > Here is what I've tried so far without any luck.
> >
> > 1. I logged into locally to the host. Still can't start services.
> > 2. I also changed the guest to start with a local account as oppose to a
> > domain account. That didn't work, so I just unchecked the box.
> > 3. I changed the Virtual server service to start with local logon instead
> > of
> > Network Services.
> >
> > Still doesn't work unless I'm connected to the local network with the
> > physical domain.
> >
> > This server will eventuall be in its own subnet and needs to start without
> > being on the current network.
> >
> >
>
>