what kind of packet sniffing/troubleshooting have you done so far?
make sure you are using the latest nwclient & patches
http://support.novell.com/filefinder,
http://download.novell.com
run through
http://www.ithowto.com/novell/clientspeed.htm
make sure DS is clean & healthy
make sure you have the server updated to the latest patches & oplocks level1
& 2 are set correct -
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10085899.htm youll
want to make sure server & workstation are configured.
SLP is setup properly on the server, & distributed properly to workstations
via dhcp (yes, you do want to set this up) - service location protocol,
useful even in a small 5 person office all the way up to the largest
companies around. (how many users do you have anyways?)
http://www.srvloc.org/,
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10014570.htm,
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10024591.htm. You
set this up, then push the options out via dhcp.
Internal DNS setup properly (yes, you do want to set this up) - you can use
sys
ublic\dnsdhcp console (run the setup from there) or iManager for dns (&
dhcp).
DHCP - you want this setup internally, because you can push out dhcp options
to clients that your WG router cannot, such as SLP.
latest drivers for everything (nic/chipset/controller/etc)
that speed/duplex on *everything* is hardset, & hardset correctly
check cables, make sure everything is cat5e certified, not using flat
cables/cat3/etc (ive seen it in a lot of places)
purge all volumes & turn off compression - there are many utilities out
there that allow you to do automated purges, check out the links section
under
www.abend.org
make sure there is more than 10% free on EVERY volume
make sure bios/firmware to everything (server/raid
cards/switches/workstations/etc) up to date
Microsoft Office slow - Other things that may make it
slow is office itself isnt up to date (you do have enterprise version & roll
it out/update via AIP right?), and drive mappings to slow remote servers or
servers that no longer exist. If you are using nwclient49sp1, make sure you
rolled it out via ACU with nmas disabled (
www.appdeploy.com has ACU info)
