From: PorBar on
We are setting up a network that currently uses WindowsNT Server (yes,
you read that correctly). We are going to use Windows 2008 R2
Standard. This network only has 6 clients. Should we use the router as
the DHCP server or should we use the Server for both DNS and DHCP?

The clients are XP Pro and WIndows7

Thanks
From: Danny Sanders on
Use Windows for DHCP and DNS.


hth
DDS

"PorBar" <compsosinc(a)gmail.com> wrote in message
news:c583023f-c48e-4aeb-8b02-2c3d037fa1c3(a)h9g2000yqm.googlegroups.com...
> We are setting up a network that currently uses WindowsNT Server (yes,
> you read that correctly). We are going to use Windows 2008 R2
> Standard. This network only has 6 clients. Should we use the router as
> the DHCP server or should we use the Server for both DNS and DHCP?
>
> The clients are XP Pro and WIndows7
>
> Thanks


From: PorBar on
On May 12, 4:33 pm, "Danny Sanders" <dsand...(a)NOSPAMbrakesplus.com>
wrote:
> Use Windows for DHCP and DNS.
>
> hth
> DDS
>
> "PorBar" <compsos...(a)gmail.com> wrote in message
>
> news:c583023f-c48e-4aeb-8b02-2c3d037fa1c3(a)h9g2000yqm.googlegroups.com...
>
> > We are setting up a network that currently uses WindowsNT Server (yes,
> > you read that correctly). We are going to use Windows 2008 R2
> > Standard. This network only has 6 clients. Should we use the router as
> > the DHCP server or should we use the Server for both DNS and DHCP?
>
> > The clients are XP Pro and WIndows7
>
> > Thanks

I thought if the Server is a Domain Controller with Active Directory &
DNS, it is best to use the router for DHCP?
From: Leythos on
In article <c583023f-c48e-4aeb-8b02-2c3d037fa1c3
@h9g2000yqm.googlegroups.com>, compsosinc(a)gmail.com says...
> We are setting up a network that currently uses WindowsNT Server (yes,
> you read that correctly). We are going to use Windows 2008 R2
> Standard. This network only has 6 clients. Should we use the router as
> the DHCP server or should we use the Server for both DNS and DHCP?
>

Consider SBS 2008 instead of Windows server if it's for a small shop,
they get Exchange, File/AD, internal Company website for document
management, etc...

The DNS and DHCP should be provide by the server if you're joining
computers to the server as part of a domain.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free(a)rrohio.com (remove 999 for proper email address)
From: Leythos on
In article <80b49491-44e5-4aad-bd37-e82602216175
@e1g2000yqe.googlegroups.com>, compsosinc(a)gmail.com says...
>
> On May 12, 4:33 pm, "Danny Sanders" <dsand...(a)NOSPAMbrakesplus.com>
> wrote:
> > Use Windows for DHCP and DNS.
> >
> > hth
> > DDS
> >
> > "PorBar" <compsos...(a)gmail.com> wrote in message
> >
> > news:c583023f-c48e-4aeb-8b02-2c3d037fa1c3(a)h9g2000yqm.googlegroups.com....
> >
> > > We are setting up a network that currently uses WindowsNT Server (yes,
> > > you read that correctly). We are going to use Windows 2008 R2
> > > Standard. This network only has 6 clients. Should we use the router as
> > > the DHCP server or should we use the Server for both DNS and DHCP?
> >
> > > The clients are XP Pro and WIndows7
> >
> > > Thanks
>
> I thought if the Server is a Domain Controller with Active Directory &
> DNS, it is best to use the router for DHCP?

NEVER, the DHCP, if properly configured on the server, will provide data
that your router won't provide to the workstations.

Since you're doing a domain, it's not too late to consider SBS 2008
instead of Server 2008 standard.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam999free(a)rrohio.com (remove 999 for proper email address)