This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 9%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETF%3C/text%3E%3C/svg%3E)
I am implementing a system that uses a vpnClient type background task for use with the Windows Networking VPN API. I've been encountering some weird behavior where it seems like connecting the VPN profile via ConnectProfileAsync, which then in turn triggers my background task, times out after 15 seconds (I am expecting the connection to take around 30 seconds). In this case, it times out and ConnectProfileAsync returns an error of type "Other". In practice, it seems like I can just call the ConnectProfileAsync function again right after failure, and it will pick back right up where it started, eventually leading to a successfully connected profile?? This makes no sense to me. Questions:
If anyone has any knowledge to share pertaining this, it would be greatly appreciated.
The IVpnPlug Connect call is normally given more than 15 seconds before it times out. Have you looked at the VPN sample on Github?
I have not looked at that example specifically, but upon viewing, it is similar to other references I've been using. I will start to reference this one as well to help see where things may have gone awry.
I think for my scenario it's not quite the IVpnPlug connect call taking longer than 15 seconds. Using function examples from your VPN sample in lieu of my own, I would be having a 15+ second gap in between agent.ConnectProfileAsync and VpnChannel.ProcessEventAsync. I'm not sure if that would make a difference in the behavior you'd be expecting
I've experimented with moving my connection logic inside the IVpnPlug connect call, but agent.ConnectProfileAsync() and VpnChannel.ProcessEventAsync() seems to both return before IVpnPlugIn.Connect() is even finished. I expected those two to be blocked waiting for IVpnPlugIn.Connect to finish?
Edit: Actually, nevermind. They do block successfully-- there was just a bug elsewhere. Moving the bulk of my connection logic inside of the IVpnPlug connect call has solved the issue. It now connects via a single call to agent.ConnectProfileAsync() and succeeds even if it takes longer than 15 seconds.
Thank you!
Glad I could help!
Hello, Welcome to Microsoft Q&A,
Your issue that might be related to VPN and currently there is official code sample that you could refer to.
Thanks
Nico Zhu