newbie question

[Fitz]

I am just learning about server 2003, and have a few questions that don't
seem to be addressed in books.

1. When do I need to have the server in a domain and not a workgroup.
I only need to network 5 computers and was told that using a workgroup is
much easier.

2. If I use a workgroup and not a domain or active directory, then do I need
to install DNS.

3. Why or when would I want or need to go more advance and use a domain, AD
and DNS?

Thanks, Fitz

 

[Ryan Hanisco]

Fitz,

By number...
1. You should run a domain when you need to control all your servers and
workstations as a unit and not deal with machine to machine permissions.
This usually comes when you have more than one server/ workstation providing
services to the others. It is also a HUGE security improvement.

2. No, you will rely on broadcasts for naming and resource searches. This
is NOT a reliable technology and it will only work most of the time. It is
not something for a mission critical operation. Network broadcasts are heavy
on the network and cannot traverse subnets or routed boundaries.

3. You need this as soon as you need to rely on the network to do anything.
With a workgroup it is a nice to have convienence.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"Fitz" wrote:

> I am just learning about server 2003, and have a few questions that don't
> seem to be addressed in books.
>
> 1. When do I need to have the server in a domain and not a workgroup.
> I only need to network 5 computers and was told that using a workgroup is
> much easier.
>
> 2. If I use a workgroup and not a domain or active directory, then do I need
> to install DNS.
>
> 3. Why or when would I want or need to go more advance and use a domain, AD
> and DNS?
>
> Thanks, Fitz
>
>
>

 

[Theo Verweij]

The problem mentioned by 2 can be resolved by installing WINS on the
server, and register all machines on it.

Ryan Hanisco wrote:
> Fitz,
>
> By number...
> 1. You should run a domain when you need to control all your servers and
> workstations as a unit and not deal with machine to machine permissions.
> This usually comes when you have more than one server/ workstation providing
> services to the others. It is also a HUGE security improvement.
>
> 2. No, you will rely on broadcasts for naming and resource searches. This
> is NOT a reliable technology and it will only work most of the time. It is
> not something for a mission critical operation. Network broadcasts are heavy
> on the network and cannot traverse subnets or routed boundaries.
>
> 3. You need this as soon as you need to rely on the network to do anything.
> With a workgroup it is a nice to have convienence.

 

[Ryan Hanisco]

Theo,

You are right, but at that point you might as well bring a DC live. I see
that more as an AND rather than an OR.
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL

Remember: Marking helpful answers helps everyone find the info they need
quickly.


"Theo Verweij" wrote:

> The problem mentioned by 2 can be resolved by installing WINS on the
> server, and register all machines on it.
>
> Ryan Hanisco wrote:
> > Fitz,
> >
> > By number...
> > 1. You should run a domain when you need to control all your servers and
> > workstations as a unit and not deal with machine to machine permissions.
> > This usually comes when you have more than one server/ workstation providing
> > services to the others. It is also a HUGE security improvement.
> >
> > 2. No, you will rely on broadcasts for naming and resource searches. This
> > is NOT a reliable technology and it will only work most of the time. It is
> > not something for a mission critical operation. Network broadcasts are heavy
> > on the network and cannot traverse subnets or routed boundaries.
> >
> > 3. You need this as soon as you need to rely on the network to do anything.
> > With a workgroup it is a nice to have convienence.
>

 

[Herb Martin]

"Fitz" <fitz@yahoo.com> wrote in message
news:eQZ4XidvHHA.484@TK2MSFTNGP06.phx.gbl...
>I am just learning about server 2003, and have a few questions that don't
>seem to be addressed in books.
>
> 1. When do I need to have the server in a domain and not a workgroup.
> I only need to network 5 computers and was told that using a workgroup is
> much easier.

Not really (a workgroup easier) -- somewhere between a few and a dozen
you should almost certainly switch to a domain.

Domains are easier the more machines and users you have and not really
any harder for a small number.

Domains WOULD be expensive IF you didn't have a copy of Server OS
already -- it costs more than workstation/XP.

> 2. If I use a workgroup and not a domain or active directory, then do I
> need to install DNS.

Probably a good idea, but not technically required.

For a single subnet, broadcast resolution of NetBIOS names will actually
work.


> 3. Why or when would I want or need to go more advance and use a domain,
> AD and DNS?

See above.


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)

 

[Herb Martin]

"Theo Verweij" <tverweij@xs4all.nl> wrote in message
news:468b9caa$1$338$e4fe514c@news.xs4all.nl...
> The problem mentioned by 2 can be resolved by installing WINS on the
> server, and register all machines on it.

I push people to use WINS a LOT, but there is no significant need for
a WINS server unless you have more than one Subnet.

WINS is a practical necessity for more than one subnet even if you have
DNS -- as long as you want all the features of Windows networking to
be available.

> Ryan Hanisco wrote:
>> Fitz,
>>
>> By number...
>> 1. You should run a domain when you need to control all your servers and
>> workstations as a unit and not deal with machine to machine permissions.
>> This usually comes when you have more than one server/ workstation
>> providing services to the others. It is also a HUGE security
>> improvement.
>>
>> 2. No, you will rely on broadcasts for naming and resource searches.
>> This is NOT a reliable technology and it will only work most of the time.
>> It is not something for a mission critical operation. Network broadcasts
>> are heavy on the network and cannot traverse subnets or routed
>> boundaries.
>>
>> 3. You need this as soon as you need to rely on the network to do
>> anything. With a workgroup it is a nice to have convienence.