Question: Usually when you have shared folder or a drive on a network location, it's browsable through Microsoft Windows Network. This is however painfully slow. Often when the computer or network location cannot be found, it takes ages before you get an error message and regain control over windows explorer.
Most of the time when I accidentally click on a location that is not connected (because I clicked a shared folder from a server at work while at home) I can sit and wait till the error message.
Is there a way to make the process faster? Like cutting down a timeout or make it look for the folders/drives/computers in the background in stead of holding up explorer?

**Comment on answers:**
*@bua:  

This option requires me to use a different explorer to browse. Is there something I can do while using normal explorer?*

*@Dani:  

This won't help me to browse between network folder/computers. Only speed up using shortcut folders. But then again, when this folder is not available, the hold of explorer is still there.*

Answer: 
One simplest way is to use [Total commander](http://www.ghisler.com/) or [FreeCommander](http://www.freecommander.com/index.htm) (an open source alternative) to explore Your PC/laptop/NFS or even FTP server.

This will certainly speed-up your work, and wont block your explorer when accidentally clicking on shared folders.
I always setup a WINS server (usually a Linux machine running Samba) and then point all Windows machines to it (manually if the IP address is static, via DHCP if the IP address is dynamic). It speeds up browsing enormously.

```
$ grep "wins support" /etc/samba/smb.conf
   wins support = yes

```

Always make sure one of the participants to the Windows network is a PDC, or a Domain Master or whatever. Setting up WINS in a situation like this is trivial.