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.

Start by reviewing the SQL Server 2022 network packet-size behavior described for Windows Server 2022 and Windows 11 clients, including the TSS.ps1 observation. Reproduce the issue across the stated environments and compare behavior before and after reboot; done means identifying a confirmed cause and fix. No source files or tests are named, and the issue remains tied to an open Microsoft support case.