WIN2K DHCP SERVER??? 2

[GSSAssassin]

I have a NT 4.0 PDC server which is running DHCP server.(I.P. scope=172.16.0.0) I simply want to upgrade my 3 BDC's (which are at different locations connected via DSL-VPN)to WIN2K Server. However, each BDC is it's own DHCP server.(I.P. scopes=172.16.1.0, 172.16.2.0, 172.16.3.0) I heard that if there already is a DHCP server on the network that I should not setup my BDC's (which will be running WIN2K Server) into DHCP servers. Is this true? If so, what do I do to keep my current I.P. scopes on each BDC the same without causing a conflict on the network? If this is not possible, then what an I supposed to do? How do I setup my BDC's?(without upgrading my PDC to win2k just yet)

 

[peterve]

First of all, if you want to upgrade your network to Win2K, you will have to start with your PDC first !!
Take a BDC offline (for backup purposes), and upgrade your PDC first.

When using multiple DHCP servers, all you have to take care of is : never run 2 dhcp servers that are hosting the same IP range at the same time !!!
That's all
Peter Van Eeckhoutte
peter.ve@pandora.be

 

[DeanT]

Also, make sure that you "Authorize" your DHCP server's in Active Directory. You'll find the option on the ACTION drop down menu of your DHCP MMC interace. Without authorization your DHCP servers will NOT respond to client requests.

 

[GSSAssassin]

You said that I have to upgrade my PDC to win2k first. however today I upgraded one of my BDC's just for the hell of it and it joined the domain on my NT4.0 PDC just fine. Now I know that I can't setup Active Directory and manage accounts and such on my BDC because my PDC isn't WIN2K. But besides that, if I leave my BDC as a member server for now, will it cause any problems. And will it give any problems joining the domain once I upgrade my PDC?

 

[peterve]

When you upgrade your BDC, you will get problems...
Win2K is multi-master (all DC's can make changes), NT4 is single-master (only the PDC makes all the changes)

I'd suggest upgrading your PDC as soon as possible... Peter Van Eeckhoutte
peter.ve@pandora.be