Dec 12 2023 12:07 AM - edited Dec 12 2023 12:09 AM
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:
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?
Dec 13 2023 10:30 PM
Does anyone have an idea? Already verified few more things:
Still, connections stop with "The specified network name is no longer available" after a while or after reboot. Then unmapping/mapping, or restarting workstation service bring it back. Reboot usually does NOT with the drive persistently mapped. Rebooting without the drive mapped, and then mapping it after reboot does usually work.