Windows Slow Issue                           Help Us!

Slow Computer Browsing Issue
Slow logon to windows domain
Slow accessing the network database
Slow networking through a hub
Slow opening Windows explorer
Slow while opening "Look In" and "Save As" boxes
XP accesses Win9x very slow
Why is W2K running slower while logon

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 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.

Slow networking through a hub

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.

Slow opening Windows explorer

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.

XP accesses Win9x very slow

Symptom: XP access win9x very slow. Resolution: install SP1

Why is XP running slower while logon

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.

Click for help

 Your feedback and contributions to this web site

   Main Menu