>I installed a server and 5 workstations to replace an old peer to peer
>network running ME. I made files available offline thiking it was a good
>idea in case I needed to reboot the server while they were working. But so
>far the first complaint was this it was slower opening documents than the
>old way. That could be... also I noticed it takes a while to log in..
Usually coming from a Workgroup or an NT 4.0 domain, and complaints about
long login times is due to improper DNS setup.
AD must have a DNS server setup for the AD domain. Using your ISP's DNS
server on AD clients is the most common mistake users make and this causes
long login times and slow file access.
Basic AD DNS setup
Install DNS on the DC. Point the DC to itself for DNS in the properties of
TCP/IP. Use the actual DC's IP address not 127.0.0.1.
See:
http://support.microsoft.com/kb/814591/en-us
AD clients (servers are AD clients also) MUST point to the DNS server set up
for the AD domain ONLY.
See:
http://support.microsoft.com/kb/825036/en-us
For Internet access, setup your AD DNS server to forward requests and list
your ISP's DNS server as the forwarder. This is the only place on an AD
domain where your ISP's DNS server should be listed.
See:
http://support.microsoft.com/kb/323380/en-us
hth
DDS
"MrMulti" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I installed a server and 5 workstations to replace an old peer to peer
>network running ME. I made files available offline thiking it was a good
>idea in case I needed to reboot the server while they were working. But so
>far the first complaint was this it was slower opening documents than the
>old way. That could be... also I noticed it takes a while to log in..
>should I upgrade to a gigabit network? What else can I do to increase the
>speed? Or should I just explain that some of the slowness is due to the
>fact that it is running software that protects the documents - like
>offline viewing and eventually shadow copies.