Testing environment question

[Guest JohnB]

I am in the process of studying for a MCP, and have run into a problem. I

have the following setup:

 

- I have setup a PC with a 180-day eval copy of Windows Server 2003.

- It's a home network with a NetGear router. The router is setup for DHCP.

- There are 4 computers on the network, counting the 2003 server.

- On one of the PC's I have install Microsoft's Virtual PC. The VPC has

been joined to the domain.

 

My problem is I can't use any of the 2003 Administrative MMC's from the VPC.

It says it can't find the domain, even though the VPC was joined to the

domain without a problem. I'm guessing it's a DNS issue. The reason I say

that is, the VPC doesn't show up in DNS on the server. I do not have DHCP

setup on the server.

 

I thought about configuring DHCP on the server, thinking the VPC would then

show up in DNS. But my problem is, I already have DHCP running on the

router and, I don't want to turn that off because the "home" computers rely

on that.

 

What's the best solution for this situation? Should I just set the VPC to

static IP, and then add it in DNS on the server? I'd rather not, because

then I miss out on the opportunity to test this as if it was a corporate

network. But then I don't know of any other way, while still keeping DHCP

on the router. (I guess I have the option of putting static IP addresses on

the other home computers, and then disabling DHCP on the router).

 

Thanks in advance for your help.

[Guest Bill Grant]

Re: Testing environment question

 

You can't run a domain on a network like that without making a few

changes.

 

For your domain members to function properly they must use the local DNS

server. That is how they find domain resources, including the logon server.

It makes no difference whether they are hard metal or virtual machines.

 

Turn off the DHCP function on the router. You can set up DHCP on the DC

or you can just configure the machines manually to use the router for

default gateway but use the DC for DNS.

 

Modify the DNS on the DC to forward to a public DNS (such as the one at

your ISP). Your local DNScan now supply the local needs of AD and resolve

foreign URLs.

 

"JohnB" <jbrigan@yahoo.com> wrote in message

news:u%23cQa21mIHA.1768@TK2MSFTNGP05.phx.gbl...

>I am in the process of studying for a MCP, and have run into a problem. I

>have the following setup:

>

> - I have setup a PC with a 180-day eval copy of Windows Server 2003.

> - It's a home network with a NetGear router. The router is setup for

> DHCP.

> - There are 4 computers on the network, counting the 2003 server.

> - On one of the PC's I have install Microsoft's Virtual PC. The VPC has

> been joined to the domain.

>

> My problem is I can't use any of the 2003 Administrative MMC's from the

> VPC. It says it can't find the domain, even though the VPC was joined to

> the domain without a problem. I'm guessing it's a DNS issue. The reason

> I say that is, the VPC doesn't show up in DNS on the server. I do not

> have DHCP setup on the server.

>

> I thought about configuring DHCP on the server, thinking the VPC would

> then show up in DNS. But my problem is, I already have DHCP running on

> the router and, I don't want to turn that off because the "home" computers

> rely on that.

>

> What's the best solution for this situation? Should I just set the VPC to

> static IP, and then add it in DNS on the server? I'd rather not, because

> then I miss out on the opportunity to test this as if it was a corporate

> network. But then I don't know of any other way, while still keeping DHCP

> on the router. (I guess I have the option of putting static IP addresses

> on the other home computers, and then disabling DHCP on the router).

>

> Thanks in advance for your help.

>

>

[Guest JohnB]

Re: Testing environment question

 

The problem with that, that I forgot to mention is; the server isn't always

on. But the router is.

 

 

"Bill Grant" <not.available@online> wrote in message

news:%23xFtZB2mIHA.5956@TK2MSFTNGP03.phx.gbl...

> You can't run a domain on a network like that without making a few

> changes.

>

> For your domain members to function properly they must use the local

> DNS server. That is how they find domain resources, including the logon

> server. It makes no difference whether they are hard metal or virtual

> machines.

>

> Turn off the DHCP function on the router. You can set up DHCP on the DC

> or you can just configure the machines manually to use the router for

> default gateway but use the DC for DNS.

>

> Modify the DNS on the DC to forward to a public DNS (such as the one at

> your ISP). Your local DNScan now supply the local needs of AD and resolve

> foreign URLs.

>

> "JohnB" <jbrigan@yahoo.com> wrote in message

> news:u%23cQa21mIHA.1768@TK2MSFTNGP05.phx.gbl...

>>I am in the process of studying for a MCP, and have run into a problem. I

>>have the following setup:

>>

>> - I have setup a PC with a 180-day eval copy of Windows Server 2003.

>> - It's a home network with a NetGear router. The router is setup for

>> DHCP.

>> - There are 4 computers on the network, counting the 2003 server.

>> - On one of the PC's I have install Microsoft's Virtual PC. The VPC has

>> been joined to the domain.

>>

>> My problem is I can't use any of the 2003 Administrative MMC's from the

>> VPC. It says it can't find the domain, even though the VPC was joined to

>> the domain without a problem. I'm guessing it's a DNS issue. The reason

>> I say that is, the VPC doesn't show up in DNS on the server. I do not

>> have DHCP setup on the server.

>>

>> I thought about configuring DHCP on the server, thinking the VPC would

>> then show up in DNS. But my problem is, I already have DHCP running on

>> the router and, I don't want to turn that off because the "home"

>> computers rely on that.

>>

>> What's the best solution for this situation? Should I just set the VPC

>> to static IP, and then add it in DNS on the server? I'd rather not,

>> because then I miss out on the opportunity to test this as if it was a

>> corporate network. But then I don't know of any other way, while still

>> keeping DHCP on the router. (I guess I have the option of putting static

>> IP addresses on the other home computers, and then disabling DHCP on the

>> router).

>>

>> Thanks in advance for your help.

>>

>>

>

[Guest Bill Grant]

Re: Testing environment question

 

Then you had better leave it on! If you are running a domain, the DC

needs to be available at all times that anyone might need it .

 

"JohnB" <jbrigan@yahoo.com> wrote in message

news:u$VRqH2mIHA.5956@TK2MSFTNGP03.phx.gbl...

> The problem with that, that I forgot to mention is; the server isn't

> always on. But the router is.

>

>

> "Bill Grant" <not.available@online> wrote in message

> news:%23xFtZB2mIHA.5956@TK2MSFTNGP03.phx.gbl...

>> You can't run a domain on a network like that without making a few

>> changes.

>>

>> For your domain members to function properly they must use the local

>> DNS server. That is how they find domain resources, including the logon

>> server. It makes no difference whether they are hard metal or virtual

>> machines.

>>

>> Turn off the DHCP function on the router. You can set up DHCP on the

>> DC or you can just configure the machines manually to use the router for

>> default gateway but use the DC for DNS.

>>

>> Modify the DNS on the DC to forward to a public DNS (such as the one

>> at your ISP). Your local DNScan now supply the local needs of AD and

>> resolve foreign URLs.

>>

>> "JohnB" <jbrigan@yahoo.com> wrote in message

>> news:u%23cQa21mIHA.1768@TK2MSFTNGP05.phx.gbl...

>>>I am in the process of studying for a MCP, and have run into a problem.

>>>I have the following setup:

>>>

>>> - I have setup a PC with a 180-day eval copy of Windows Server 2003.

>>> - It's a home network with a NetGear router. The router is setup for

>>> DHCP.

>>> - There are 4 computers on the network, counting the 2003 server.

>>> - On one of the PC's I have install Microsoft's Virtual PC. The VPC

>>> has been joined to the domain.

>>>

>>> My problem is I can't use any of the 2003 Administrative MMC's from the

>>> VPC. It says it can't find the domain, even though the VPC was joined to

>>> the domain without a problem. I'm guessing it's a DNS issue. The

>>> reason I say that is, the VPC doesn't show up in DNS on the server. I

>>> do not have DHCP setup on the server.

>>>

>>> I thought about configuring DHCP on the server, thinking the VPC would

>>> then show up in DNS. But my problem is, I already have DHCP running on

>>> the router and, I don't want to turn that off because the "home"

>>> computers rely on that.

>>>

>>> What's the best solution for this situation? Should I just set the VPC

>>> to static IP, and then add it in DNS on the server? I'd rather not,

>>> because then I miss out on the opportunity to test this as if it was a

>>> corporate network. But then I don't know of any other way, while still

>>> keeping DHCP on the router. (I guess I have the option of putting

>>> static IP addresses on the other home computers, and then disabling DHCP

>>> on the router).

>>>

>>> Thanks in advance for your help.

>>>

>>>

>>

>

>