An interesting connectivity issue or two

It might be worthwhile to check for this decrepancy. It has been discovered due to the Visma Resursstyring application which probably asks for far too much data.

I just noticed that SQL server 2022 on a virtual Windows server 2022 seems to disregard the Network Packet Size setting for the TDS protocol. Note screenshots below. The setting is 4096 bytes and many of the packets that is sendt is well beyond the IP4 packet reassemply buffer on the Windows 11 client. Possibly also an issue for the VMX3net network driver on the server. Windows 10 seems to cope. I'm working to determine if this is really a big probem and then how to fix this.

I have an open case with Microsoft support regarding the issue.

When we run TSS.ps1, the Windows 11 clients works just fine. This lasts until the PC is rebooted, then its back to misery. As I wrote, I'm working to find the fix. We can't run TSS.ps1 every time we want to use that application. This is another case I have open with Microsoft.

I suspect hat the "fix"exists either because of the 2024-11 patch or a newer TSS.ps1. It didn't work that way earlier.

首先，檢視針對 Windows Server 2022 和 Windows 11 用戶端所描述的 SQL Server 2022 網路封包大小行為，包括 TSS.ps1 的觀察結果。在所述環境中重現問題，並比較重新開機前後的行為；完成的標準是確認原因和修正方案。未指定原始檔案或測試，而且該 issue 仍與一個尚未結案的 Microsoft 支援案例相關聯。