Is there a need for this?

Hi, I'm an entry level "admin" for a network in my office. Previously
I was a systems admin for a small business and maintained a mixed
Mac/XP setup with a server 2003 machine setup for file sharing and an
internal testing site for the web devs.

Now I'm thrown into an office with a previously configured SBS and
I've noticed on all my workstations, all XP Pro, they're set to
connect to the server which is setup for AD. As best I can tell, it's
completely useless. Everyone logs onto the server but works locally.
The only reason I can see that the server is even in the building is
to host files that everyone accesses and to run an SQL database for an
app we have. Past that I can't see a reason for the AD setup. Just
to see I disconnected a rarely used machine to see if there were any
adverse effects and nothing has come up in about 2 or 3 months. I
have noticed that the machines that are setup to connect to the server
spawn off alot of dnsapi, mrxsmb, lsasrv and win32time errors in the
eventlog. After disconnecting the one machine, those stopped, which
isn't really all that surprising since all the errors whined and
moaned about the problems coming from the domain. I assume it's not
setup right, in addition to having this network configured wrong.

If there is no real reason to have it setup like this, what effects
could I expect when I disconnect the machines? I assume I'll have to
deal with "why's my desktop look different know?" since there are no
local accounts on the machines aside from the admin accounts. I'm
just afraid that I'll have to deal with a host of issues ranging from
the simple account creation to things that are out of the scope of my
knowledge right now.

Thanks in advance for any insight into this issue.
.

Relevant Pages

  • RE: Securing a Local Network
    ... Show the Management of your company the insecurity of the Peer to Peer ... setup and discuss what risks are they willing to accept. ... -Cost of getting the web server and the mail server internally versus having ... -Use an older box for Intrusion Detection on the internal network as well. ...
    (Security-Basics)
  • ksoftirqd causing severe network performance problems
    ... failover setup), with a new one. ... At the end of last week, the new setup had network problems and what we saw on ... the linux router was that the kernel threads ksoftirqd_CPU1 and ksoftirqd_CPU0 ... When the backup is working fine, we can't use the faulty server anymore ...
    (Linux-Kernel)
  • RDP to internal client machine?
    ... Have the router successfully setup to allow VPN to the server, ... to then RDP to other computers within the network, ... machines within the network I ...
    (microsoft.public.windows.server.sbs)
  • ksoftirqd causing severe network performance problems
    ... failover setup), with a new one. ... At the end of last week, the new setup had network problems and what we ... When the backup is working fine, we can't use the faulty server ... switching drivers and switching between kernel versions (2.4.21/2.4.22/ ...
    (comp.os.linux.networking)
  • Re: Best way to connect via wireless in new SBS install?
    ... I have just setup someline very similar for a client of mine. ... and setup DHCP on the server. ... this means that all local internal network traffic ... I've seen so many posts suggesting using SBS ...
    (microsoft.public.windows.server.sbs)
Loading