Will server provide DHCP ONLY to domain members?

I'm helping a local community radio station transition from a peer-peer
hodgepodge of XP, Win 2000 and Win 98 machines into a Windows 2003 Domain
with all XP clients. This is strictly a low-buck operation, so reall
servers, RAID, etc., are not even a consideration. The entire network is
behind a Linksys firewall/switch, that is currently providing DHCP services.



For redundancy, we're going to take two existing machines, running their
live streaming audio and archiving, respectively, and turn them into a
primary and a backup domain controller. In addition to serving up the
10-workstation domain, the servers will continue to do the streaming audio &
archiving, both of which are pretty nondemanding applications.



To start the process, I installed Windows 2003 Server on a THIRD machine - a
Pentium 266 with 500 Meg of Ram. It seemed to install and run just fine. Our
thought was to use it to make sure that the streaming audio and archiving
software would work in 2003 Server, and then use it as a temp while we
convert the other two machines.



First question: When I put this machine on line, to rebuild the first of the
two permanent servers, is it going to try to respond to DHCP requests even
though the clients are not yet part of the domain? (I.e., am I going to have
contention problems between the server's DHCP and the Linksys?) If so, then
I can turn off the DHCP on the switch, but I want to make sure I'm not
leaving the clients with nothing at all in the interim.



Second question: rather than promoting one of the other servers to a PDC, is
there any reason I shouldn't just run all three, with this admittedly
marginal machine as the PDC? That way, if any 1 of the 3 go down, the
remaining 2 will cover both the domain services and the streaming audio &
archiving.



In addition, we're adding a USB shared drive which will be backed up nightly
to their offsite web server, via FTP.



Yeah, I know it's makeshift, but it's a step in the right direction from
where they are now, which is no data redundancy, no security, no backups,
network resources sporadically available, etc. . .



Thanks,



Joe

Hi,
Answer to your first Question, Yes Your DHCP service will assign ip address
all computers at your network, if the clients are joind to your domain or
not, they will get ip address from your DHCP that is a member of your
domain.
your second question has ne reason or problem, you can promote...

good luck

ILKER SOGUT

"Joe Befumo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm helping a local community radio station transition from a peer-peer
> hodgepodge of XP, Win 2000 and Win 98 machines into a Windows 2003 Domain
> with all XP clients. This is strictly a low-buck operation, so reall
> servers, RAID, etc., are not even a consideration. The entire network is
> behind a Linksys firewall/switch, that is currently providing DHCP
> services.
>
>
>
> For redundancy, we're going to take two existing machines, running their
> live streaming audio and archiving, respectively, and turn them into a
> primary and a backup domain controller. In addition to serving up the
> 10-workstation domain, the servers will continue to do the streaming audio
> & archiving, both of which are pretty nondemanding applications.
>
>
>
> To start the process, I installed Windows 2003 Server on a THIRD machine -
> a Pentium 266 with 500 Meg of Ram. It seemed to install and run just fine.
> Our thought was to use it to make sure that the streaming audio and
> archiving software would work in 2003 Server, and then use it as a temp
> while we convert the other two machines.
>
>
>
> First question: When I put this machine on line, to rebuild the first of
> the two permanent servers, is it going to try to respond to DHCP requests
> even though the clients are not yet part of the domain? (I.e., am I going
> to have contention problems between the server's DHCP and the Linksys?) If
> so, then I can turn off the DHCP on the switch, but I want to make sure
> I'm not leaving the clients with nothing at all in the interim.
>
>
>
> Second question: rather than promoting one of the other servers to a PDC,
> is there any reason I shouldn't just run all three, with this admittedly
> marginal machine as the PDC? That way, if any 1 of the 3 go down, the
> remaining 2 will cover both the domain services and the streaming audio &
> archiving.
>
>
>
> In addition, we're adding a USB shared drive which will be backed up
> nightly to their offsite web server, via FTP.
>
>
>
> Yeah, I know it's makeshift, but it's a step in the right direction from
> where they are now, which is no data redundancy, no security, no backups,
> network resources sporadically available, etc. . .
>
>
>
> Thanks,
>
>
>
> Joe
>
>

You would be well advised to turn off the DHCP service on the Linksys and
run it on one of your servers.

The real problem is going to be DNS. You cannot use the current setup of
relaying DNS requests to an external DNS service. Active Directory requires
that all the domain machines use the local DNS which has the SRV records for
your domain. All local machines (including the servers themselves) need to
use the local DNS only. Set this local DNS server to forward to a public DNS
service so that it can resolve foreign URLs as well as handle the local DNS
calls.

"Joe Befumo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I'm helping a local community radio station transition from a peer-peer
> hodgepodge of XP, Win 2000 and Win 98 machines into a Windows 2003 Domain
> with all XP clients. This is strictly a low-buck operation, so reall
> servers, RAID, etc., are not even a consideration. The entire network is
> behind a Linksys firewall/switch, that is currently providing DHCP
> services.
>
>
>
> For redundancy, we're going to take two existing machines, running their
> live streaming audio and archiving, respectively, and turn them into a
> primary and a backup domain controller. In addition to serving up the
> 10-workstation domain, the servers will continue to do the streaming audio
> & archiving, both of which are pretty nondemanding applications.
>
>
>
> To start the process, I installed Windows 2003 Server on a THIRD machine -
> a Pentium 266 with 500 Meg of Ram. It seemed to install and run just fine.
> Our thought was to use it to make sure that the streaming audio and
> archiving software would work in 2003 Server, and then use it as a temp
> while we convert the other two machines.
>
>
>
> First question: When I put this machine on line, to rebuild the first of
> the two permanent servers, is it going to try to respond to DHCP requests
> even though the clients are not yet part of the domain? (I.e., am I going
> to have contention problems between the server's DHCP and the Linksys?) If
> so, then I can turn off the DHCP on the switch, but I want to make sure
> I'm not leaving the clients with nothing at all in the interim.
>
>
>
> Second question: rather than promoting one of the other servers to a PDC,
> is there any reason I shouldn't just run all three, with this admittedly
> marginal machine as the PDC? That way, if any 1 of the 3 go down, the
> remaining 2 will cover both the domain services and the streaming audio &
> archiving.
>
>
>
> In addition, we're adding a USB shared drive which will be backed up
> nightly to their offsite web server, via FTP.
>
>
>
> Yeah, I know it's makeshift, but it's a step in the right direction from
> where they are now, which is no data redundancy, no security, no backups,
> network resources sporadically available, etc. . .
>
>
>
> Thanks,
>
>
>
> Joe
>
>

Got it, thanks.

Joe

"ILKER SOGUT" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi,
> Answer to your first Question, Yes Your DHCP service will assign ip
> address all computers at your network, if the clients are joind to your
> domain or not, they will get ip address from your DHCP that is a member of
> your domain.
> your second question has ne reason or problem, you can promote...
>
> good luck
>
> ILKER SOGUT
>
> "Joe Befumo" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm helping a local community radio station transition from a peer-peer
>> hodgepodge of XP, Win 2000 and Win 98 machines into a Windows 2003 Domain
>> with all XP clients. This is strictly a low-buck operation, so reall
>> servers, RAID, etc., are not even a consideration. The entire network is
>> behind a Linksys firewall/switch, that is currently providing DHCP
>> services.
>>
>>
>>
>> For redundancy, we're going to take two existing machines, running their
>> live streaming audio and archiving, respectively, and turn them into a
>> primary and a backup domain controller. In addition to serving up the
>> 10-workstation domain, the servers will continue to do the streaming
>> audio & archiving, both of which are pretty nondemanding applications.
>>
>>
>>
>> To start the process, I installed Windows 2003 Server on a THIRD
>> machine - a Pentium 266 with 500 Meg of Ram. It seemed to install and run
>> just fine. Our thought was to use it to make sure that the streaming
>> audio and archiving software would work in 2003 Server, and then use it
>> as a temp while we convert the other two machines.
>>
>>
>>
>> First question: When I put this machine on line, to rebuild the first of
>> the two permanent servers, is it going to try to respond to DHCP requests
>> even though the clients are not yet part of the domain? (I.e., am I going
>> to have contention problems between the server's DHCP and the Linksys?)
>> If so, then I can turn off the DHCP on the switch, but I want to make
>> sure I'm not leaving the clients with nothing at all in the interim.
>>
>>
>>
>> Second question: rather than promoting one of the other servers to a PDC,
>> is there any reason I shouldn't just run all three, with this admittedly
>> marginal machine as the PDC? That way, if any 1 of the 3 go down, the
>> remaining 2 will cover both the domain services and the streaming audio &
>> archiving.
>>
>>
>>
>> In addition, we're adding a USB shared drive which will be backed up
>> nightly to their offsite web server, via FTP.
>>
>>
>>
>> Yeah, I know it's makeshift, but it's a step in the right direction from
>> where they are now, which is no data redundancy, no security, no backups,
>> network resources sporadically available, etc. . .
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Joe
>>
>>
>
>

Got it. Actually, when I installed Active Directory, it appears to have set
up the DNS server correctly, copying the initial DNS addresses I had set up
into the forwarding addresses. I will set up all the clients to use only the
internal (local) DNS servers. Is there anything else I need to do, or should
be aware of? I've actually done this a few times before with no major
problems, but this is the first time I've had to make the transition without
worrying about disrupting a functioning workgroup, so my main concerns are
related to those intermediate cusps between the time I put the server online
and the time I migrate the workgroup members to the new domain.

Thanks again,

Joe


"Bill Grant" <not.available@online> wrote in message
news:eSB5m$(E-Mail Removed)...
> You would be well advised to turn off the DHCP service on the Linksys
> and run it on one of your servers.
>
> The real problem is going to be DNS. You cannot use the current setup
> of relaying DNS requests to an external DNS service. Active Directory
> requires that all the domain machines use the local DNS which has the SRV
> records for your domain. All local machines (including the servers
> themselves) need to use the local DNS only. Set this local DNS server to
> forward to a public DNS service so that it can resolve foreign URLs as
> well as handle the local DNS calls.
>
> "Joe Befumo" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm helping a local community radio station transition from a peer-peer
>> hodgepodge of XP, Win 2000 and Win 98 machines into a Windows 2003 Domain
>> with all XP clients. This is strictly a low-buck operation, so reall
>> servers, RAID, etc., are not even a consideration. The entire network is
>> behind a Linksys firewall/switch, that is currently providing DHCP
>> services.
>>
>>
>>
>> For redundancy, we're going to take two existing machines, running their
>> live streaming audio and archiving, respectively, and turn them into a
>> primary and a backup domain controller. In addition to serving up the
>> 10-workstation domain, the servers will continue to do the streaming
>> audio & archiving, both of which are pretty nondemanding applications.
>>
>>
>>
>> To start the process, I installed Windows 2003 Server on a THIRD
>> machine - a Pentium 266 with 500 Meg of Ram. It seemed to install and run
>> just fine. Our thought was to use it to make sure that the streaming
>> audio and archiving software would work in 2003 Server, and then use it
>> as a temp while we convert the other two machines.
>>
>>
>>
>> First question: When I put this machine on line, to rebuild the first of
>> the two permanent servers, is it going to try to respond to DHCP requests
>> even though the clients are not yet part of the domain? (I.e., am I going
>> to have contention problems between the server's DHCP and the Linksys?)
>> If so, then I can turn off the DHCP on the switch, but I want to make
>> sure I'm not leaving the clients with nothing at all in the interim.
>>
>>
>>
>> Second question: rather than promoting one of the other servers to a PDC,
>> is there any reason I shouldn't just run all three, with this admittedly
>> marginal machine as the PDC? That way, if any 1 of the 3 go down, the
>> remaining 2 will cover both the domain services and the streaming audio &
>> archiving.
>>
>>
>>
>> In addition, we're adding a USB shared drive which will be backed up
>> nightly to their offsite web server, via FTP.
>>
>>
>>
>> Yeah, I know it's makeshift, but it's a step in the right direction from
>> where they are now, which is no data redundancy, no security, no backups,
>> network resources sporadically available, etc. . .
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Joe
>>
>>
>
>

Is there a good online resource you might recommend for learning the basics
of Active Directory? (Specifically from a system management perspective).

Thanks again,

Joe


"Bill Grant" <not.available@online> wrote in message
news:eSB5m$(E-Mail Removed)...
> You would be well advised to turn off the DHCP service on the Linksys
> and run it on one of your servers.
>
> The real problem is going to be DNS. You cannot use the current setup
> of relaying DNS requests to an external DNS service. Active Directory
> requires that all the domain machines use the local DNS which has the SRV
> records for your domain. All local machines (including the servers
> themselves) need to use the local DNS only. Set this local DNS server to
> forward to a public DNS service so that it can resolve foreign URLs as
> well as handle the local DNS calls.
>
> "Joe Befumo" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> I'm helping a local community radio station transition from a peer-peer
>> hodgepodge of XP, Win 2000 and Win 98 machines into a Windows 2003 Domain
>> with all XP clients. This is strictly a low-buck operation, so reall
>> servers, RAID, etc., are not even a consideration. The entire network is
>> behind a Linksys firewall/switch, that is currently providing DHCP
>> services.
>>
>>
>>
>> For redundancy, we're going to take two existing machines, running their
>> live streaming audio and archiving, respectively, and turn them into a
>> primary and a backup domain controller. In addition to serving up the
>> 10-workstation domain, the servers will continue to do the streaming
>> audio & archiving, both of which are pretty nondemanding applications.
>>
>>
>>
>> To start the process, I installed Windows 2003 Server on a THIRD
>> machine - a Pentium 266 with 500 Meg of Ram. It seemed to install and run
>> just fine. Our thought was to use it to make sure that the streaming
>> audio and archiving software would work in 2003 Server, and then use it
>> as a temp while we convert the other two machines.
>>
>>
>>
>> First question: When I put this machine on line, to rebuild the first of
>> the two permanent servers, is it going to try to respond to DHCP requests
>> even though the clients are not yet part of the domain? (I.e., am I going
>> to have contention problems between the server's DHCP and the Linksys?)
>> If so, then I can turn off the DHCP on the switch, but I want to make
>> sure I'm not leaving the clients with nothing at all in the interim.
>>
>>
>>
>> Second question: rather than promoting one of the other servers to a PDC,
>> is there any reason I shouldn't just run all three, with this admittedly
>> marginal machine as the PDC? That way, if any 1 of the 3 go down, the
>> remaining 2 will cover both the domain services and the streaming audio &
>> archiving.
>>
>>
>>
>> In addition, we're adding a USB shared drive which will be backed up
>> nightly to their offsite web server, via FTP.
>>
>>
>>
>> Yeah, I know it's makeshift, but it's a step in the right direction from
>> where they are now, which is no data redundancy, no security, no backups,
>> network resources sporadically available, etc. . .
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Joe
>>
>>
>
>

you will fing everything at www.microsoft.com

ILKER SOGUT

"Joe Befumo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Is there a good online resource you might recommend for learning the
> basics of Active Directory? (Specifically from a system management
> perspective).
>
> Thanks again,
>
> Joe
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:eSB5m$(E-Mail Removed)...
>> You would be well advised to turn off the DHCP service on the Linksys
>> and run it on one of your servers.
>>
>> The real problem is going to be DNS. You cannot use the current setup
>> of relaying DNS requests to an external DNS service. Active Directory
>> requires that all the domain machines use the local DNS which has the SRV
>> records for your domain. All local machines (including the servers
>> themselves) need to use the local DNS only. Set this local DNS server to
>> forward to a public DNS service so that it can resolve foreign URLs as
>> well as handle the local DNS calls.
>>
>> "Joe Befumo" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>> I'm helping a local community radio station transition from a peer-peer
>>> hodgepodge of XP, Win 2000 and Win 98 machines into a Windows 2003
>>> Domain with all XP clients. This is strictly a low-buck operation, so
>>> reall servers, RAID, etc., are not even a consideration. The entire
>>> network is behind a Linksys firewall/switch, that is currently providing
>>> DHCP services.
>>>
>>>
>>>
>>> For redundancy, we're going to take two existing machines, running their
>>> live streaming audio and archiving, respectively, and turn them into a
>>> primary and a backup domain controller. In addition to serving up the
>>> 10-workstation domain, the servers will continue to do the streaming
>>> audio & archiving, both of which are pretty nondemanding applications.
>>>
>>>
>>>
>>> To start the process, I installed Windows 2003 Server on a THIRD
>>> machine - a Pentium 266 with 500 Meg of Ram. It seemed to install and
>>> run just fine. Our thought was to use it to make sure that the streaming
>>> audio and archiving software would work in 2003 Server, and then use it
>>> as a temp while we convert the other two machines.
>>>
>>>
>>>
>>> First question: When I put this machine on line, to rebuild the first of
>>> the two permanent servers, is it going to try to respond to DHCP
>>> requests even though the clients are not yet part of the domain? (I.e.,
>>> am I going to have contention problems between the server's DHCP and the
>>> Linksys?) If so, then I can turn off the DHCP on the switch, but I want
>>> to make sure I'm not leaving the clients with nothing at all in the
>>> interim.
>>>
>>>
>>>
>>> Second question: rather than promoting one of the other servers to a
>>> PDC, is there any reason I shouldn't just run all three, with this
>>> admittedly marginal machine as the PDC? That way, if any 1 of the 3 go
>>> down, the remaining 2 will cover both the domain services and the
>>> streaming audio & archiving.
>>>
>>>
>>>
>>> In addition, we're adding a USB shared drive which will be backed up
>>> nightly to their offsite web server, via FTP.
>>>
>>>
>>>
>>> Yeah, I know it's makeshift, but it's a step in the right direction from
>>> where they are now, which is no data redundancy, no security, no
>>> backups, network resources sporadically available, etc. . .
>>>
>>>
>>>
>>> Thanks,
>>>
>>>
>>>
>>> Joe
>>>
>>>
>>
>>
>
>