quic
4 TopicsIntermittent issues with SMB over QUIC (Server 2022 Datacenter Azure Edition)
Hi, we're trying to implement SMB over QUIC using a Windows 2022 server syncing with an Azure File Share. This seems to work fine in the first place - when we bring up the server and map the drive on a client, we can connect and everything is good. However: After a while, clients lose connection ("the network share is no longer available") When mapping the drive as persistent, in many cases it does not work after reboot (but after disconnecting it and mapping it again) Sometimes it works again after restarting the client's "workstation" service Sometimes it works again after restarting the server's "lanmanserver" service Sometimes it requires server reboot to work again Sometimes it requires client reboot to work again It behaves similarly from both the internal network (using the server's internal IP) as well as the Internet (using the server's public IP). Per WAC everything seems configured correctly: KDC proxy is enabled and configured and known to clients: Regularly (apparently on every connection attempt, but also if nothing is connected), server logs a QUIC error with its own IP: "This event commonly occurs because the server certificate mapping is not created", but the certificate mapping seems fine: Screenshot from the client (services.msc was used to restart the workstation service): Does anybody have an idea what could be wrong, or which logs to check, or which events to collect?1.7KViews0likes1CommentMsQuic is Open Source
Microsoft is open sourcing our QUIC library, MsQuic, on GitHub under an MIT license. MsQuic is a cross-platform, general-purpose library that implements the QUIC transport protocol. QUIC is being standardized by the Internet Engineering Task Force (IETF). MsQuic is a client and server solution optimized for multiple usage patterns and is used by multiple Microsoft products and services. MsQuic is currently in preview and supports Windows and Linux.62KViews5likes0Comments