My Network Places take over 30 seconds to open

[T. Duprex]

I am running Windows XP SR2 on my laptop. When I click on "My Network
Places" it takes in excess of 30 seconds for the information to appear. As
suggested earlier, I disabled the Registry item:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer
\RemoteComputer\NameSpace\Disable {D6277990-4C6A-11CF-8D87-00AA0060F5BF}

then rebooted and the problem still exists. I have a home network with two
Windows 98 second edition machines and another Windows XP Laptop. The other
laptop running windows XP immediately displays My Network Places
information. For the life of me I cannot find any difference between the
two machines. I do not and never have used passwords nor do any of my
machines have scheduled tasks.

I would appreciate suggestions and help on this.
TIA

 

[Chuck]

I am running Windows XP SR2 on my laptop. When I click on "My Network
Places" it takes in excess of 30 seconds for the information to appear. As
suggested earlier, I disabled the Registry item:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer
\RemoteComputer\NameSpace\Disable {D6277990-4C6A-11CF-8D87-00AA0060F5BF}

then rebooted and the problem still exists. I have a home network with two
Windows 98 second edition machines and another Windows XP Laptop. The other
laptop running windows XP immediately displays My Network Places
information. For the life of me I cannot find any difference between the
two machines. I do not and never have used passwords nor do any of my
machines have scheduled tasks.

I would appreciate suggestions and help on this.
TIA

If the problem isn't the well known scheduler problem, then look for gratuitous
protocols. Having more than one protocol involved in Network Neighborhood will
require waiting for each to time out, for various network operations.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>

If no help yet, let's take a look at "browstat status" and "ipconfig /all" for
the 3 computers. Follow instructions in this article.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

 

[T. Duprex]

Chuck:

Ran through the first two links you provided. The only thing I found was
that the protocol stack showed "Default" for Tcp/ip, I changed that to
Netbios over TCP/IP. However this was set to Default on my other laptop
which is working fine. I found no other discrepancies. What I did notice
and may be of significance is this:

When all my computers (4) are on, I click on MY Network Places on the
machine I'm concerned about, it took 5 -6 seconds for a response. I then
turned off one machine and it then took 9 - 11 seconds for a response to
clicking My Network Places. Then when I turned off the third machine the
time went to 25 plus seconds. Does this lead you to a particular setting
somewhere I could check?


, > On Thu, 29 Sep 2005 13:09:57 -0700, "T. Duprex"

 

[Chuck]

, > On Thu, 29 Sep 2005 13:09:57 -0700, "T. Duprex"

The contents of Network Neighborhood are provided by a service known as the
browser, and more specifically, the Master Browser (please don't confuse this
with Internet Explorer or its competitors). At any time, there can (should) be
one and only one master browser. If you turned off a computer, and it was
acting as the master browser, another master browser takes time to be elected,
in a peer-peer transaction between all computers online.

Depending upon what transports being are run by the various computers online,
the election can take longer. Multiple transports cause more latency.

That's a summary of your scenario. For a longer, and better organised
description, read my articles.
<http://nitecruzr.blogspot.com/2005/04/nt-browser-or-why-cant-i-always-see.html>
<http://nitecruzr.blogspot.com/2005/05/windows-9x-9598me-and-browser.html>
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html>
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.