Windows Server 2003 Architecture

Have a server, shared dsl, about ten workstations, no active directory. I
think this network needs a total overhaul. The dsl line comes into one
room, and there is the dsl modem. A line goes from the modem in that room
to another room where there is a router and a switch. The lines go from the
switch and the router to the various workstations and the server, which are
all in other rooms. What would be the best architecture that would allow
for active directory, etc.? Shouldn't the server be used for DHCP, and not
the router? This server just serves one application and that's it. Can't I
implement the active directory and control TCP/IP traffic, and control user
authenitication?

TIA

I'm sorry, I thought this was a win 2003 server group, my apologies...

"Kevin Altizer" <me@mydomain.com> wrote in message
news:6v%_e.6035$QE1.3098@newsread2.news.atl.earthl ink.net...
> Have a server, shared dsl, about ten workstations, no active directory. I
> think this network needs a total overhaul. The dsl line comes into one
> room, and there is the dsl modem. A line goes from the modem in that room
> to another room where there is a router and a switch. The lines go from
> the switch and the router to the various workstations and the server,
> which are all in other rooms. What would be the best architecture that
> would allow for active directory, etc.? Shouldn't the server be used for
> DHCP, and not the router? This server just serves one application and
> that's it. Can't I implement the active directory and control TCP/IP
> traffic, and control user authenitication?
>
> TIA
>