>I have a Windows Server 2003 enterprise edition, trial, and on it I installed
>Virtual PC, with two XP Pro VM's. (I'm teaching an exchange 2003 class at a
>local tech college). I'm running the host as a domain controller, dns, and
>exchange server.
>
>What I wanted to do was connect both vm's to the host's domain, and test
>exchange with outlook on one of the vm's. I can't get the vm's connected to
>the domain though. The vm's can ping the host, but not vice versa, and when
>trying to connect them to the domain I get a DNS server not available error.
>I have everything set up with static ips; originally I thought it was a DNS
>problem, but it worked fine when I used two XP boxes I have in my lab.
>
>The computer's we're using in the lab are dells, 2 gig ram, decent
>processors, broadcom nics.
>
>The vm's and host are on the same subnet. I've tried all the different
>virtual pc settings possible. This worked fine on a Windows Server 2003 std
>edition. Has anyone else come across this, and either discovered you can't
>use virtual pc with 2003 enterprise, or found a fix?
>
>Thanks for the help.

> On Wed, 28 Oct 2009 11:48:07 -0700, dbere
> <(email address - cut out)> wrote:
>
> >I have a Windows Server 2003 enterprise edition, trial, and on it I installed
> >Virtual PC, with two XP Pro VM's. (I'm teaching an exchange 2003 class at a
> >local tech college). I'm running the host as a domain controller, dns, and
> >exchange server.
> >
> >What I wanted to do was connect both vm's to the host's domain, and test
> >exchange with outlook on one of the vm's. I can't get the vm's connected to
> >the domain though. The vm's can ping the host, but not vice versa, and when
> >trying to connect them to the domain I get a DNS server not available error.
> >I have everything set up with static ips; originally I thought it was a DNS
> >problem, but it worked fine when I used two XP boxes I have in my lab.
>
> Is the domain controller the DNS provider?
>
> >
> >The computer's we're using in the lab are dells, 2 gig ram, decent
> >processors, broadcom nics.
>
> Do you have NIC teaming or TCP offloading enabled on the broadcoms?
> Have you updated to the latest drivers? Broadcom NICs can be
> notorious with VMs.
>
> >
> >The vm's and host are on the same subnet. I've tried all the different
> >virtual pc settings possible. This worked fine on a Windows Server 2003 std
> >edition. Has anyone else come across this, and either discovered you can't
> >use virtual pc with 2003 enterprise, or found a fix?
> >
> >Thanks for the help.
>
> Have you checked the firewall on the XP VMs? By default this will
> prevent pings.
>
> --
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
> http://smudj.wordpress.com/
> .
>

>Thanks for the reply,
>
>The domain controller does provide the dns, and all firewalls are off. One
>of the first things I tried, I'm not sure what the fact that I can only ping
>one way means.
>

>>Thanks for the reply,
>>
>>The domain controller does provide the dns, and all firewalls are off. One
>>of the first things I tried, I'm not sure what the fact that I can only ping
>>one way means.
>>
>
>Have you selected the host NIC or Shared Networking for the VMs
>network options?
>
>>
>>I tried both, neither works. There are two other settings, local and
>>something I can't think of at the moment, that didn't do the trick either.
>>Host NIC works for the std edition.

> .
>

>Thanks again.
>
>I can ping by ip address, but not the name. This means its a DNS problem?
>I removed and redid DNS, it appeared to be working, but probably not. After
>that though I installed exchange on the server too. I was avoiding doing
>DNS, because the last time I played with DNS on an exchange server, the
>exchange got all screwed up.
>
>Well, I guess that's what a lab is for, right? :)
>

> On Sat, 31 Oct 2009 12:46:02 -0700, dbere
> <(email address - cut out)> wrote:
>
> >Thanks again.
> >
> >I can ping by ip address, but not the name. This means its a DNS problem?
> >I removed and redid DNS, it appeared to be working, but probably not. After
> >that though I installed exchange on the server too. I was avoiding doing
> >DNS, because the last time I played with DNS on an exchange server, the
> >exchange got all screwed up.
> >
> >Well, I guess that's what a lab is for, right? :)
> >
>
> In an Active Directory Domain Controller I believe DNS is one of the
> main things thta must be set up...
> And the domain members must use this DNS server as their DNS source,
> otherwise it won't work.
> --
>
> Bo Berglund (Sweden)
> .
>