Winbox legacy version get disconnected issue

Once ppp service over 300 VPN connections , winbox 3.43 get disconnected issue again and again.

“Router x.x.x.x has been disconnected, will retry in 5 seconds.”

But winbox 4.0 everything is fine.

My server works as VPN server run with 7.20.7 long term CHR mode with P1 license.

Winbox 3.43 64bit and 32bit.

Insufficient, incomplete, and unexplained data.

I have a PPPeE server with thousands of users and have never encountered this problem.

WinBox 3.43 is the current version of WinBox; it's certainly not legacy.

Winbox 4 is fully in beta.

My server as VPN server, 300 vpn connections, not PPPOE server.

And - even if it was - just in case:
https://jdebp.uk/FGA/legacy-is-not-a-pejorative.html

Particularly useful, the definition by Peter Langston:

legacy (adj ) — A pejorative term used in the computer industry meaning "it works"

Now also circle where your problem is.

Exactly.

That's what the good Mikrotik guys (the same people that weren't capable of making a fully functional v 4.x version in over 16 months) like to call the 3.x version.

Right, it was just an example that doesn't depend on load, if you use the right machines.

Lots of text and circles, but nothing useful, like the RouterOS version or the hardware used...

So sorry, forgot routeros version.

My server works as VPN server run with 7.20.7 long term CHR mode with P1 license.

Winbox 3.43 64bit and 32bit.

When I remove some connections(total less than 300), the problem still exists. Except reboot routeros, I have no idea for this issue now.

Try contacting support. I have no experience with combining VPN and CHR...
I use an RB1100AHx2 with various VPN types and haven't had this problem so far.

I’ve figured it out this issue, when sever’s bandwidth full loaded and ping timeout intermittently, winbox 3.43 will encounte disconnection problem.