SMB2:30秒超时后发送OpLock确认?

时间:2019-03-15 11:55:49

标签: windows networking smb

我正在调查通过网络访问文件时的延迟。这是网络监视器给我的顺序:

16848   08:42:17 System SERVER  CLIENT  SMB2    SMB2:N   OPLOCK BREAK (0x12)    {SMBOverTCP:49, TCP:48, IPv4:47}
17408   08:42:22 System SERVER  CLIENT  SMB2    SMB2:R   CREATE (0x5)  Interim Response, File=Storage\file@#16844   {SMB2:87, SMBOverTCP:42, TCP:39, IPv4:26}
// some unrelated events
20123   08:42:47 System SERVER  CLIENT  SMB2    SMB2:R   CREATE (0x5), MxAc+RqLs(RH), FID=0x2(Storage\file#16844)   {SMB2:87, SMBOverTCP:42, TCP:39, IPv4:26}
20124   08:42:47 System CLIENT  SERVER  SMB2    SMB2:A   OPLOCK BREAK (0x12)    {SMBOverTCP:42, TCP:39, IPv4:26}
20125   08:42:47 System SERVER  CLIENT  SMB2    SMB2:R   OPLOCK BREAK (0x12)    {SMBOverTCP:42, TCP:39, IPv4:26}   

在OpLock超时(30秒)后立即发送OpLock确认的原因可能是什么?

可以从Windows服务和在同一台计算机上运行的应用程序(客户端)中使用相同的用户帐户访问相同的文件。

0 个答案:

没有答案