SSTP Win10 | The reason code returned on termination is 829.

Some user’s connect to ROS v6.42.2 via SSTP and after 0-120 second Win10 disconnect connection with error:

The user DESKTOP-xxxx\yyyy dialed a connection named VPN NAME (SSTP) which has terminated. The reason code returned on termination is 829.

ROS see connection and new one are not possible because I allow only to one connection.
ROS on some time do timeout and disconnect connection, last time after ~3h40m.

Maybe you know something about this or you sure that upgrade fix this and in witch version of ROS?
Maintenance with 1mt ahead.
Other types of VPN works and are a WorkARound.

I’m having the same problem as well.

Well looking at the version of firmware on the MT, I would say an upgrade is in order.

Mine has latest long-term. 6.48.6?

This issue still exists in Windows 11 (with latest updates to this day) and with RouterOS 7.16: SSTP VPN dialed to MikroTik always crashes after some time with the following message:

The user dialed a connection named <connection_name> which has terminated. The reason code returned on termination is 829.

Log on MikroTik says only “: terminating… - terminated by remote peer”

According to MS documentation this means “disconnected due to link failure” which does not make any sense, since the same thing happens when I connect to the MikroTik router directly by the cable. Tried this with also different hardware configs (including Windows VM as a client). Result is always the same.

The crash trigger is usually the amount of outbound connections established via VPN from client Windows machine eg. by repeatedly launching the connection speed test on webpages that does also multi threaded upload against multiple servers.

Unfortunately, this looks like a bug in Windows SSTP client :frowning:

After further testing, I think this is actually a bug in RouterOS :frowning: the same client with the same config connecting to MS RAS server does not disconnect unexpectedly under the same conditions (tested also with Microsoft support). On the other hand, MikroTik device with minimal configuration connected directly by cable to the client disconnect the client with a " disconnected due to link failure".

Tested with multiple RouterBoard types and result was still the same: Just open many outbound connections via the dialed SSTP VPN and this dialed VPN disconnects. It’s frustrating.

Opened a ticket to MikroTik, now we can just wait if this will come to any conclusion.