Long story short, I tracked this (lack of) behavior to our update, some three years ago, to JCIFS 1.3.14. The major item in that JCIFS release's changelog reads "JCIFS will no longer do a NetBIOS Node Status to determine the server hostname because it seems some servers no longer respond to it".
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Sandy Skipper September 1, 2020 at 3:55 PM
It was suggest that this issue be included in project Snow Leopard.
Jeff Gehlbach March 21, 2016 at 2:58 PM
NB the JCifsMonitor can replace SmbMonitor for many (all?) use cases.
Jeff Gehlbach June 1, 2013 at 7:21 AM
Thanks for the hint, Antonio. I looked at the detector and tried to fix the problem there, but I don't understand the detector framework well enough so I'll have to get help from somebody who knows it better.
Jeff Gehlbach June 1, 2013 at 7:20 AM
Antonio pointed out that the detector needs fixing too (as does the Capsd plugin)
Antonio Russo June 1, 2013 at 3:17 AM
The same problem is in SMB Detector, you should fix this there too!
While investigating commercial support ticket https://mynms.opennms.com/Ticket/Display.html?id=1608 I discovered that the SmbMonitor does not create any actual traffic on the network.
Long story short, I tracked this (lack of) behavior to our update, some three years ago, to JCIFS 1.3.14. The major item in that JCIFS release's changelog reads "JCIFS will no longer do a NetBIOS Node Status to determine the server hostname because it seems some servers no longer respond to it".