B
bonsaiviking
Guest
On Windows Server 2019 Datacenter, installing any NDIS 6.0 LWF filter driver results in a network interruption. This is noticeable on Azure instances because the RDP connection drops. We have seen this with our own filter driver, but we have also reproduced it with the demo LWF driver from the Windows DDK. Not registering the optional callbacks does not have an impact: the network still drops for a moment.
This doesn't happen with Windows Server 2016, and may be related to the QoS feature. A customer of ours had this observation: "Additional observation is that there is some relation to presence of QoS binding on the network interface. When the QoS binding is disabled, the installer finishes without breaking the RDP connection. This scenario however cannot be used as a workaround, since the RDP connection gets broken anyway when QoS binding is restored (re-enabled) after the filter driver is installed."
Is this intentional, or is there a way to work around this?
Continue reading...
This doesn't happen with Windows Server 2016, and may be related to the QoS feature. A customer of ours had this observation: "Additional observation is that there is some relation to presence of QoS binding on the network interface. When the QoS binding is disabled, the installer finishes without breaking the RDP connection. This scenario however cannot be used as a workaround, since the RDP connection gets broken anyway when QoS binding is restored (re-enabled) after the filter driver is installed."
Is this intentional, or is there a way to work around this?
Continue reading...