Hi Tom, On 03/19, Tom Talpey wrote:
What server is returning this unsigned response? Assuming it's Windows, that is either a doc bug or (arguably) a server bug, and should be reported before deciding how to address it here.
It's a NetApp ONTAP 9.5P13. We've identified it's also setting wrong signatures on READ responses with STATUS_END_OF_FILE. Our tests against Windows Server 2019 showed it to behave ok, so it looks like something on NetApp side. Thanks anyway. Enzo
