forum.excito.org

This is not per se a bubba related issue, but if anyone can help me with this i'd really appreciate it.
In short I found out that, when I turn of my bubba or move my laptop to a different network, the windows explorer hangs literally for minutes searching for network shares. Only issue is that there are no shares mapped or visible in any way (also not in network neighborhood, or run services or anything). So way is this &%#$^@ client hanging forever? WHen I disable the wireless network the windows explorer stops searching within 2 seconds. No it's not a virus.

thanks

Hi Ubi,

There is probably still something waiting for the bubba.
If a host has gone AWOL, the timeouts before a previously connected host fails can be substantial. I think it used to be something like 4 minutes on windows (last time I had an issue like this reported to me, several years ago), on solaris it could be catastrophic - 30 minutes or more.
There are of course ways to tweak the timeouts, but the best way would be to find out why it is happening.

I would recommend a wireshark trace on the windoze machine with a filter that only catches traffic to/from the bubba that's gone off the air, then with the portnumbers and protocols used, you might find out the windows process behind it (RPC service, DNS, WINS crap?).
When you know what it is, you can tweak your windows registry or bubba settings...

My 2 cents.

Cheers,

Cheeseboy

thanks

I think I found out what the issue was, thanks to netstat.
It turns out one of the users mapped his "my documents" to the external machine. And for some bizarre reason, the OS decides to try and map these homedirs even when that user is not logged in and have a timeout of about 2 weeks for it to figure out there is no server present. ANd then retry and timeout every single damn time someone accesses windows explorer. How great is that...

I truly hate windows.