I've posted this in the general Sitescope forum and trying my luck here with this in the customer forum. I've already had a few responsed from Kenneth, no solution (yet) ...
I have Sitescope 11.22 running a couple of monitors and find on some of the remote windows nodes being monitored have a few idle sessions which are more than 5 days to 2 weeks old and older.
We've been using the "net sess" command on the windows nodes to check and see how long sessions from sitescope server have been idle. We also use "net sess \\<sitescope_hostname> /delete /Y" to remove all sessions associated with the sitescope server which helps clear all the idle sessions, however we view this as a workaround and is unacceptable as a solution.
We have also tried disabling caching connections in the monitors, (though to my understanding if the monitor is configured to use caching netbios connections then the the netbios connections should be re-used and should really only be a handfull idle sessions running and not filling up the netbios connections from sitescope server on the remote windows node).
The monitors we run are:
HOST23 Disk (C) - Microsoft Windows Resources
HOST23 Disk (D) - Microsoft Windows Resources
HOST23 Memory - Microsoft Windows Resources
I see this has been reported in the past from at least 2 others (searched forums on NETBios connections) though not clear to me if the problem was actually solved from those two other reported instances, they are roughly a year or older now.
I'd like to know the cause and more importantly how to resolve this issue, Sitescope creates too many sessions on the remote windows nodes until no more netbios sessions can be created hence sitescope is eventually denied access from the remote windows nodes - this reflects badly on us as we have monitoring enabled and because of the monitors tie up the session limits and lose the ablitity to monitor the windows nodes.