Checking lists for troubleshooting slow issue
1. Check the DNS, WINS, DHCP and Master Browser.
2. Check any mapping problems, for example network disconnected with red x.
3. Check hardware settings and make sure switches and hubs can handle NIC settings. Many hubs don't support full duplex.
4. Check anti-virus software, especially real-time protection.
5. Check any spyware and adware.
Copy Files to a 2000 Domain Controller Slowly
Symptoms: 1) When copying some small files from a w2k/xp computer to a network share on a 2000 domain controller, network performance is slower than if you copy the same files to a member server. However, you may not have this issue when copying a few large files. 2) This problem only occurs if you either use Windows Explorer to copy the files or if a Windows Explorer window is open and connected to the target server. However, if you use Xcopy.exe to copy the files and all of the Explorer windows are closed, you do not experience this issue.
Resolutions: 1) On the domain controller, you can edit the TcpDelAckTicks registry value to adjust the TCP delayed ACK timer. 2) Apply latset SP. Or Re: MS Q270926, Q321098 and 321169
Slow Computer Browsing Issue
SYMPTOMS: If you have a multihomed or multiple-transport computer, the browse process can be slow. This behavior can occur because of the following scenario: If the browser client is trying to locate a browser server on each network card or transport, it waits until it either one receives valid information or times out on each endpoint before returning.
RESOLUTIONS:
1) Use fewer protocols or network cards on a computer.
2) Disable NetBIOS on the interfaces that client will not use.
3) Having a browser server available on all endpoints will speed up the process.
4) Stop Master browser on W2K/XP clients by using net stop browser.
5) Ensure that WINS is available for TCP\IP networks or enable NetBIOS over TCP/IP.
Slow backup - it takes a 5MB/min to backup remote computer
Always check the NIC settings when you are experiencing backup slowness. Specifically, make sure that your switch or hub can handle NIC full duplex settings.
Slow file write from win2k to NT 4 server
Cause: Win2k uses Large File support while Windows NT 4.0 use Large File Read support only, but not Large File Write support.
Slow logon to windows domain
Possible solutions:
1) check DNS settings.
2) It is better to use its using the same DNS as the server i.e. local DNS not internet DNS.
3) Check for logon scripts for any errors.
4) Check Event Viewer for any errors, especially GPO's errors that could be causing the delay.
5) Check any errors on event viewer.
Slow accessing the network database
1. The Antivirus real time protection may may slow opening the data.
2. If it slows because the system is in the idle mode, you may want to change the NIC power Management settings by going to the properties of the NIC>Configuration>Power Management, clear Allow the computer to turn off this device to save power.
Symptoms: you have small network connecting 2 computers through a hub. The network works fine but it is slower. If you use crossover cable to connect these computers, the speed is normal.
Resolution: configure all of the computers' network cards for half duplex. Most Hubs don't support full duplex.
Q: When I logon my laptop with domain account at home and open windows explorer, it runs ever slow. Why?
A: When logging on this laptop at work, the Windows Explorer may map the network drives persistently. Now, since you are logging on the domain user without domain, the Windows Explorer will take long time to open. The resolution is that disable persistent mapping.
Slow while opening "Look In" and "Save As" boxes
SYMPTOMS: when using a program such as Notepad that uses common dialog boxes and clicking Open on the File menu and then click the drop-down arrow on the Look In box or the Save In drop-down box in the Save or Save As dialog boxes, you may experience a problem that takes several minutes before the lists actually drops down.
That are some reasons for that delay: 1) if you have persistent connections to network drives (for example, to drive Z) that are inaccessible for some reasons, 2) if you are working offline with no network connection.
RESOLUTIONS:
1) If opening windows explorer take a long time also, make sure all network connections are active. If not, disconnect no accessible network drives.
2) To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix.
3) Instead of connecting a persistent network drive to a network location, add the network location to My Network Places.
4) Instead of connecting a persistent network drive to a network location, use logon script to map the network drive with /persistent:no option. Refer to MS Q321126.
Symptoms and resolutions of spyware and adware
Symptoms: 1. Poor performance.
2. Unwanted browser behavior.
3. Pop-ups when you aren’t on the Internet.
4. Problems using secure Web sites.
5. Task Manager lists some strange programs like regpd.exe and vgmc.exe. and you can't delete them or they will come back after you delete them.
Resolutions: 1. Delete all temp files.
2. Use spyware and adware remover tools.
3. Use regedit and msconfig to clean them.
4. Enable firewall and pop-up blockers.
Symptom: in a mixed OS, win98, MW and W2K/XP, if win98 and Me client have a password-protected file share; all computers are part of a workgroup; you are using the "Save this password" feature on your XP client computer, you may experience slow browsing Win98 and ME from the XP.
Resolution: XP always saves the password in the Credential Manager. When you browse a Win98 or Me client in a peer-to-peer network, Credential Manager tries to contact a domain controller to validate the password. Because the computers are in a workgroup environment, there is no domain controller, and you must wait until the requests timeout. Install SP1 should fix this problem.
Why is XP running slower while logon 1
When I login into a Windows 2000 active directory from a new xp pro machine the login in is extremely slow. After logged on, everything works fine. But other windows versions don't have this problem.
A: This is almost like name resolution issue. Comparing with previous versions, XP is heavily dependent on DNS to find DC. If the DNS is configured incorrectly, XP will take longer time waiting for it to timeout before it tries using NetBIOS. Make sure
1) The DNS setup correct and have the server information.
2) XP clients can find the DNS server.
3) XP machine's DNS server is pointed to your internal DNS server rather than your ISP's DNS server.
4) Make sure no errors on logon scripts or GPO's that could be causing the delay.
5) Check any errors on event viewer.
6) Disable NetBIOS on the interfaces that client will not use.
If the resolution of "Why is XP running slower while logon 1" doesn't fix the slower issue. and if other Operation Systems including w2k don't have the same issue, you may check the hardware settings, for example, configure all of the computers' network cards for half duplex. Most Hubs don't support full duplex.