We create another scan target (\data\!Public\) and have the same error. In ScanDetail-TemirFS0.log (attached) we can see, that
06.08.2012 7:23:22","INFO","TemirFS 08/06/12 - 9:27 AM","STARTED_SEGMENT","\\172.25.9.21\data\!Public","0","","","",""
"06.08.2012 7:23:22","WARNING","TemirFS 08/06/12 - 9:27 AM","FAILED_ITEM","\\172.25.9.21\data\!Public","0","Access is denied -- ‘Ёб⥬ п ®иЁЎЄ 86. ‘ҐвҐў®© Ї а®«м гЄ § ҐўҐа®.","","",""
(in russian, "System Error 86. Network Password Incorrect")
"06.08.2012 7:23:22","INFO","TemirFS 08/06/12 - 9:27 AM","FAILED_SEGMENT","\\172.25.9.21\data\!Public","0","Access is denied -- ‘Ёб⥬ п ®иЁЎЄ 86. ‘ҐвҐў®© Ї а®«м гЄ § ҐўҐа®.","","",""
(in russian, "System Error 86. Network Password Incorrect")
But we can easy map this network share via Windows Explorer with the same security credentials!
And we have NULL SID error in EventLog on target server when DLP attempts to scan the share (websense2.txt, attached).
What's wrong with DLP settings?
P.S. There is a pound sign character in password, but as i read in admin guide, this is acceptable symbol for passwords in Discovery credentials