I have an Azure File Share mapped to a drive letter through net use.
When the Twingate service is logged in, computer restarts in 1m 3s (according to stop watch).
If I “Log out & disconnect” the Twingate client, computer takes 12m 30s to restart, over 12m of which is the shutdown process.
If I lose the network (unplugged cable), the client closes itself and a full shutdown (not restart) took 10m 45s.
Nothing in Event Log seems relevant here.
–
These should be outlier events at the office, but remote users could easily run into WiFi dead zones and need to shutdown / restart.
With the ridiculously-long DNS names provided by Azure Files, and Azure Files not working with aliases, I can’t expect users to access File Shares via UNC paths.
How can I keep the mapped shares without it taking so long to shut down/restart when not connected to Twingate?
It’s… super odd you’re seeing such a pronounced delay in shutdown/reboot. I would normally expect a bit of hangup/latency if the OS is trying to connect to those folders but can’t actually reach the network, but 10+ (even 5+) minutes seems insane.
Is your connection to your AD server also routed over Twingate?
It seems like there could be some form of misconfiguration within your environment that is causing timeouts to occur slower than usual.
Unfortunately, I cannot think of a single reason Twingate would negatively affect your shutdown process when it is not running unless there are a number of AD specific infrastructure items that need to be reached through Twingate.
If you can provide a bit more info we can dig a bit.
I finally found the right set of search terms, and, as you suspected, this has nothing to do with Twingate.
It turns out it’s an issue with explorer.exe that has been a problem since Windows 10 Build 1909.
Apparently Windows Explorer runs ridiculously slow when mapped drives are disconnected. It’s mostly seen when using the File Explorer, but no doubt it’s causing my shutdown/restart delay, as well. My test rig is using Windows 11, so I don’t know yet if the shutdown/restart delay will appear in Windows 10 or not.
From what I’ve read, it’s an issue with any VPN/remote network solution, not just Twingate. This is my first foray into remote access (all my past systems were locked down from external access) so I had assumed it was a Twingate issue.
–
If anyone in the future comes across this question, the only solution seems to be adding UNC paths to Quick Access instead of mapping shares to drive letters.