Stumper - running a Windows Server 2003 DC on the same subnet as w

[Guest Don Murphy]

Hello,

 

I am attempting to replace an older server running windows server 2000

standard edition configured with WIN2000DOMAIN (domain name) and W2000D

(netbios name).

 

I am replacing that with a Windows Server 2003 R2 domain controller running

SP2 configured with WIN2000DOMAIN (domain name) and W2000D (netbios name).

 

Note the netbios name is the same. When the win2003 DCboots it does not

start AD correctly because of an error with the netbios name (other computer

is preventing it) I have shut the DHCP service down on the windows 2003 DC.

This is a temporiary condition untill migration is complete (1 month)

 

How can I get these two DCs to coexist? Can I change the netbios name? Any

other ideas?

[Guest Chris M]

Re: Stumper - running a Windows Server 2003 DC on the same subnetas w

 

Re: Stumper - running a Windows Server 2003 DC on the same subnetas w

 

Don Murphy wrote:

> Hello,

>

> I am attempting to replace an older server running windows server 2000

> standard edition configured with WIN2000DOMAIN (domain name) and W2000D

> (netbios name).

>

> I am replacing that with a Windows Server 2003 R2 domain controller running

> SP2 configured with WIN2000DOMAIN (domain name) and W2000D (netbios name).

>

> Note the netbios name is the same. When the win2003 DCboots it does not

> start AD correctly because of an error with the netbios name (other computer

> is preventing it) I have shut the DHCP service down on the windows 2003 DC.

> This is a temporiary condition untill migration is complete (1 month)

>

> How can I get these two DCs to coexist? Can I change the netbios name? Any

> other ideas?

 

What are you trying to do? Build a completely new domain or just replace

the old domain controller with a new one?

 

If it's the latter, all you needed to do was add the new server to the

existing WIN2000DOMAIN domain and then promote it to be a domain

controller. Then you can migrate any necessary FSMO roles from the old

server, move any fileshares etc and then decommission it.

 

It sounds to me as if you've configured the new server as a domain

controller for a brand new domain with the same name as your existing

one, and now you're trying to plug it into your existing network

expecting it to 'take over'. This won't work.

 

--

Chris.

[Guest Don Murphy]

Re: Stumper - running a Windows Server 2003 DC on the same subnet

 

Re: Stumper - running a Windows Server 2003 DC on the same subnet

 

I wanted a new server a new domain etc. The old server will be retired. I

want them both up working independantly. My problem is they both have the

same netbios name and that is preventing ad from starting on one of them.

 

Don Murphy

 

 

"Chris M" wrote:

> Don Murphy wrote:

> > Hello,

> >

> > I am attempting to replace an older server running windows server 2000

> > standard edition configured with WIN2000DOMAIN (domain name) and W2000D

> > (netbios name).

> >

> > I am replacing that with a Windows Server 2003 R2 domain controller running

> > SP2 configured with WIN2000DOMAIN (domain name) and W2000D (netbios name).

> >

> > Note the netbios name is the same. When the win2003 DCboots it does not

> > start AD correctly because of an error with the netbios name (other computer

> > is preventing it) I have shut the DHCP service down on the windows 2003 DC.

> > This is a temporiary condition untill migration is complete (1 month)

> >

> > How can I get these two DCs to coexist? Can I change the netbios name? Any

> > other ideas?

>

> What are you trying to do? Build a completely new domain or just replace

> the old domain controller with a new one?

>

> If it's the latter, all you needed to do was add the new server to the

> existing WIN2000DOMAIN domain and then promote it to be a domain

> controller. Then you can migrate any necessary FSMO roles from the old

> server, move any fileshares etc and then decommission it.

>

> It sounds to me as if you've configured the new server as a domain

> controller for a brand new domain with the same name as your existing

> one, and now you're trying to plug it into your existing network

> expecting it to 'take over'. This won't work.

>

> --

> Chris.

>