How to deal with computers that are not available on network

[Vocalpoint]

Been running into this a lot lately - and I'm sure there's an optimum setting I am missing.

Usually I will use XY to occasionally browse shares on a computer on is up and appears in the Network tree one day...and then the next day - XY is still showing said computer in it's network tree - even tho the machine is not even on. If I mistakenly hit the icon (like I did today)...XY will grind away for minutes before it finally realizes the machine is not really there.

Best practices? Is there a refresh setting that will ensure the Network tree in XY ONLY shows available machines at startup (or when I manually refresh XY?)

Appreciate some insight on this.

Cheers,

VP

[serendipity]

Been running into this a lot lately - and I'm sure there's an optimum setting I am missing.

Usually I will use XY to occasionally browse shares on a computer on is up and appears in the Network tree one day...and then the next day - XY is still showing said computer in it's network tree - even tho the machine is not even on. If I mistakenly hit the icon (like I did today)...XY will grind away for minutes before it finally realizes the machine is not really there.

Best practices? Is there a refresh setting that will ensure the Network tree in XY ONLY shows available machines at startup (or when I manually refresh XY?)

Appreciate some insight on this.

Cheers,

VP

Hi,
I think you have the "Cache network servers" option checked.
Uncheck it from Tools>Config>Startup & exit

[admin]

If I mistakenly hit the icon (like I did today)...XY will grind away for minutes before it finally realizes the machine is not really there.

It's actually Windows that grinds away. XY just sits there and waits for a function to return. The interesting question is: Why does it take so long at your end? When I do this the grinding only takes about 5 seconds. I cannot answer this question.