2 DHCP Servers - When one starts the other stops

I have a network (over 40 subnets) that hosts ~7,000 users that are spread
across three Windows NT 4.0 domains. I have been asked to migrate them to
Windows Server 2003 and Active Directory. I have built the infrastructure
and migrated the users. In the process I was also going to deploy new WINS
and DHCP servers and retire the old Windows Server 2000 WINS and DHCP
server.

Here is my issue. I have exported the scopes and when I started the new
Windows Server 2003 DHCP server to import it went well. This server is
properly part of the new forest and has ben authorized. The problem is that
whenever I start the new server the old Windows 2000 DHCP that is part of
the NT 4.0 domain has its service stop.

Any thoughts? I need both to function for a period of time together. The
reason for this that the office are being migrated in stages and if the
office has not been migrated it needs the old DNS and WINS info so I will
keep the scope on the old DHCP server active and deactive the corresponding
scope on hte new DHCP server deactive as it wilr l have the scope options
that point DNS and WINS to the new servers.

When a windows 2000/2003 DHCP server is not authorized and "sees"
another DHCP server on the network it stops itself.

To get it to not stop you have to authorize it and I dont think you can
do that in an NT4 domain.

Also if they have the same scopes its no good idea to have them both on
simultaniously.

What you have to do is bring the Win2k DHCP down and just run the new
Win2k3 DHCP.

/daniel heimburg

Robert Tichelman skrev:
> I have a network (over 40 subnets) that hosts ~7,000 users that are spread
> across three Windows NT 4.0 domains. I have been asked to migrate them to
> Windows Server 2003 and Active Directory. I have built the infrastructure
> and migrated the users. In the process I was also going to deploy new WINS
> and DHCP servers and retire the old Windows Server 2000 WINS and DHCP
> server.
>
> Here is my issue. I have exported the scopes and when I started the new
> Windows Server 2003 DHCP server to import it went well. This server is
> properly part of the new forest and has ben authorized. The problem is that
> whenever I start the new server the old Windows 2000 DHCP that is part of
> the NT 4.0 domain has its service stop.
>
> Any thoughts? I need both to function for a period of time together. The
> reason for this that the office are being migrated in stages and if the
> office has not been migrated it needs the old DNS and WINS info so I will
> keep the scope on the old DHCP server active and deactive the corresponding
> scope on hte new DHCP server deactive as it wilr l have the scope options
> that point DNS and WINS to the new servers.
>
>

could you not authorize the old nt 4 server on the new 2K3?? I know in 2k
there is an option to authorize a second DHCP server.

Jon
"Daniel Heimburg" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> When a windows 2000/2003 DHCP server is not authorized and "sees" another
> DHCP server on the network it stops itself.
>
> To get it to not stop you have to authorize it and I dont think you can do
> that in an NT4 domain.
>
> Also if they have the same scopes its no good idea to have them both on
> simultaniously.
>
> What you have to do is bring the Win2k DHCP down and just run the new
> Win2k3 DHCP.
>
> /daniel heimburg
>
> Robert Tichelman skrev:
>> I have a network (over 40 subnets) that hosts ~7,000 users that are
>> spread
>> across three Windows NT 4.0 domains. I have been asked to migrate them
>> to
>> Windows Server 2003 and Active Directory. I have built the
>> infrastructure
>> and migrated the users. In the process I was also going to deploy new
>> WINS
>> and DHCP servers and retire the old Windows Server 2000 WINS and DHCP
>> server.
>>
>> Here is my issue. I have exported the scopes and when I started the new
>> Windows Server 2003 DHCP server to import it went well. This server is
>> properly part of the new forest and has ben authorized. The problem is
>> that
>> whenever I start the new server the old Windows 2000 DHCP that is part of
>> the NT 4.0 domain has its service stop.
>>
>> Any thoughts? I need both to function for a period of time together.
>> The
>> reason for this that the office are being migrated in stages and if the
>> office has not been migrated it needs the old DNS and WINS info so I will
>> keep the scope on the old DHCP server active and deactive the
>> corresponding
>> scope on hte new DHCP server deactive as it wilr l have the scope options
>> that point DNS and WINS to the new servers.
>>

This will probably work if he puts the win2k3 server in the existing
domain however I got the feeling he was setting up a new separate domain
to migrate into.

/daniel heimburg

Jon Phipps skrev:
> could you not authorize the old nt 4 server on the new 2K3?? I know in 2k
> there is an option to authorize a second DHCP server.
>
> Jon
> "Daniel Heimburg" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> When a windows 2000/2003 DHCP server is not authorized and "sees" another
>> DHCP server on the network it stops itself.
>>
>> To get it to not stop you have to authorize it and I dont think you can do
>> that in an NT4 domain.
>>
>> Also if they have the same scopes its no good idea to have them both on
>> simultaniously.
>>
>> What you have to do is bring the Win2k DHCP down and just run the new
>> Win2k3 DHCP.
>>
>> /daniel heimburg
>>
>> Robert Tichelman skrev:
>>> I have a network (over 40 subnets) that hosts ~7,000 users that are
>>> spread
>>> across three Windows NT 4.0 domains. I have been asked to migrate them
>>> to
>>> Windows Server 2003 and Active Directory. I have built the
>>> infrastructure
>>> and migrated the users. In the process I was also going to deploy new
>>> WINS
>>> and DHCP servers and retire the old Windows Server 2000 WINS and DHCP
>>> server.
>>>
>>> Here is my issue. I have exported the scopes and when I started the new
>>> Windows Server 2003 DHCP server to import it went well. This server is
>>> properly part of the new forest and has ben authorized. The problem is
>>> that
>>> whenever I start the new server the old Windows 2000 DHCP that is part of
>>> the NT 4.0 domain has its service stop.
>>>
>>> Any thoughts? I need both to function for a period of time together.
>>> The
>>> reason for this that the office are being migrated in stages and if the
>>> office has not been migrated it needs the old DNS and WINS info so I will
>>> keep the scope on the old DHCP server active and deactive the
>>> corresponding
>>> scope on hte new DHCP server deactive as it wilr l have the scope options
>>> that point DNS and WINS to the new servers.
>>>
>

that was my feeling, I thought he maybe able to authorize the NT4 one on the
2k3.
"Daniel Heimburg" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> This will probably work if he puts the win2k3 server in the existing
> domain however I got the feeling he was setting up a new separate domain
> to migrate into.
>
> /daniel heimburg
>
> Jon Phipps skrev:
>> could you not authorize the old nt 4 server on the new 2K3?? I know in 2k
>> there is an option to authorize a second DHCP server.
>>
>> Jon
>> "Daniel Heimburg" <(E-Mail Removed)> wrote in message
>> news:%(E-Mail Removed)...
>>> When a windows 2000/2003 DHCP server is not authorized and "sees"
>>> another DHCP server on the network it stops itself.
>>>
>>> To get it to not stop you have to authorize it and I dont think you can
>>> do that in an NT4 domain.
>>>
>>> Also if they have the same scopes its no good idea to have them both on
>>> simultaniously.
>>>
>>> What you have to do is bring the Win2k DHCP down and just run the new
>>> Win2k3 DHCP.
>>>
>>> /daniel heimburg
>>>
>>> Robert Tichelman skrev:
>>>> I have a network (over 40 subnets) that hosts ~7,000 users that are
>>>> spread
>>>> across three Windows NT 4.0 domains. I have been asked to migrate them
>>>> to
>>>> Windows Server 2003 and Active Directory. I have built the
>>>> infrastructure
>>>> and migrated the users. In the process I was also going to deploy new
>>>> WINS
>>>> and DHCP servers and retire the old Windows Server 2000 WINS and DHCP
>>>> server.
>>>>
>>>> Here is my issue. I have exported the scopes and when I started the
>>>> new
>>>> Windows Server 2003 DHCP server to import it went well. This server is
>>>> properly part of the new forest and has ben authorized. The problem is
>>>> that
>>>> whenever I start the new server the old Windows 2000 DHCP that is part
>>>> of
>>>> the NT 4.0 domain has its service stop.
>>>>
>>>> Any thoughts? I need both to function for a period of time together.
>>>> The
>>>> reason for this that the office are being migrated in stages and if the
>>>> office has not been migrated it needs the old DNS and WINS info so I
>>>> will
>>>> keep the scope on the old DHCP server active and deactive the
>>>> corresponding
>>>> scope on hte new DHCP server deactive as it wilr l have the scope
>>>> options
>>>> that point DNS and WINS to the new servers.
>>>>
>>