Frustrating workgroups/computers lag

[Rob]

I'm haveing a strange and frustrating problem on my pc. Instead of having a
network places icon on my desktop I just created a shortcut for
workgroups/computers to save myself an extra click. Previously double
clicking the icon would load up the window and show all the network pcs
pretty quickly. However the shortcut doesn't work instantly anymore.Double
clicking it gives me a brief hourglass icon and then about 30 seconds (or
more) later it finally comes up.

If I have to access a document from another pc it will take just as long
through the open dialogue. If I've already opened the file recently (today
for example) then I can reopen it instantly, but if I try to navigate via
workgroup etc it takes a while.

When I first noticed this I hadn't isntalled anything new.

 

[Chuck]

I'm haveing a strange and frustrating problem on my pc. Instead of having a
network places icon on my desktop I just created a shortcut for
workgroups/computers to save myself an extra click. Previously double
clicking the icon would load up the window and show all the network pcs
pretty quickly. However the shortcut doesn't work instantly anymore.Double
clicking it gives me a brief hourglass icon and then about 30 seconds (or
more) later it finally comes up.

If I have to access a document from another pc it will take just as long
through the open dialogue. If I've already opened the file recently (today
for example) then I can reopen it instantly, but if I try to navigate via
workgroup etc it takes a while.

When I first noticed this I hadn't isntalled anything new.

Rob,

I'd start by looking at the network stack on the computer.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

And name resolution for each computer.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

And finally, an LSP / Winsock problem, on either computer, could cause this
symptom.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html