AnsweredAssumed Answered

HNAS Oplocks in current_dblog.txt

Question asked by Miran Kreuzer on Nov 18, 2015

Hello,

 

we have a lot of Oplock Break Timeout Messages within current_dblog.txt File. I have also found some Oplock Break Messages which have to be false Messages. For example there is a Client IP shown which couldn't be able to Access specific Files because the User who is working with this Client doesn't have the necessary NTFS Permissions.

 

Client 10.103.2.71 isn't able to Access File C0328A95.tmp but according to dblog.txt the Client had opened the File? Am i missing something on that Logentries?

 

2015-11-17 08:46:49.304+01:00 2 HNAS-3080 File : xxxxxxxxxxxxxx\C0328A95.tmp

2015-11-17 08:46:49.304+01:00 2 HNAS-3080 Opened At : 2015-11-17 08:46:01+01:00 (open for 47.91 s)

2015-11-17 08:48:56.142+01:00 2 HNAS-3080 Oplock Break Timeout at 2015-11-17 08:48:56+01:00

2015-11-17 08:48:56.142+01:00 2 HNAS-3080 Owned by: SMB2 Connection: 57317 evs=1 {peer=10.103.2.71:14219, local=22.102.2.20:445} 5858 requests (SMB:2.0)

2015-11-17 08:48:56.142+01:00 2 HNAS-3080

2015-11-17 08:48:56.142+01:00 2 HNAS-3080 File : xxxxxxxxxxxxxx\Projektmanagment.one

2015-11-17 08:48:56.142+01:00 2 HNAS-3080 Opened At : 2015-11-17 08:48:21+01:00 (open for 35.03 s)

2015-11-17 08:49:38.861+01:00 2 HNAS-3080 Oplock Break Timeout at 2015-11-17 08:49:38+01:00

2015-11-17 08:49:38.861+01:00 2 HNAS-3080 Owned by: SMB2 Connection: 57317 evs=1 {peer=10.103.2.71:14219, local=22.102.2.20:445} 6957 requests (SMB:2.0)

2015-11-17 08:49:38.861+01:00 2 HNAS-3080

 

Thanks!

 

Regards

Outcomes