Hi
Since about 10 days, our customers using PPTP or L2TP VPN cannot connect to our RDP Win Server 2008 R2 anymore. They get an 'internal error has
occurred' message from their RDP client. The event log of the client shows an id of 1026 (the Connection with RDP ClientActiveX has been interrupted
(reason= 4). This happens on all of our seven clients connected by VPN on WIn7, Win8 and Win10 and it worked for years without problems before.
What we tried so far:
- Turning off printer redirection or any redirection (no change).
- Logging in with a different user (no change).
- RDP to another server (works for a few minutes, then dosn't work again).
- Creating a new local user profile (works for a few hours, then doesn't work again).
- Playing with security settings on the RDP server (sometimes works once, then doesn't work again).
- Completely uninstall and reinstall RRAS on the server (no change).
- As we have the problem since 29-May, we did a restore on the server of 16-May (no change).
- We also did a restore of 16-May to another identical server to exclude NIC hardware problems (no change).
- Using third party RDP client mRemoteNG (works, but printer redirection doesn't work. The RDP connection is always interrupted and rebuilt).
- Microsoft RDP App works, but as far as I know, they don't offer printer redirection.
- RDP Web Access works, as long as we do not click the 'this is a secure computer...' checkbox.
- Any direct access to RDP works (also over fixed 1-1 VPN) as long as we do not use PPTP or L2TP VPN.
- RRAS to another server and then RDP to the affected server works (for now).
- Seldomly even our described problem doesn't happen when we connect over VPN (PPTP or L2TP) to the affected server, perhaps 1 of 200 tries.
- sfc /scannow (no problems found).
- Server certificate valid for another two years.
- System resources on server checked (no problems found).
- Registry on server checked (no problems found).
- All needed services running.
- The clients are not part of our domain.
- Pinging the server works.
- Telnet 3389 to the server works.
- Copying files from and to the server works.
- We have exactly reproduced the situation of one of our customers in our office with a Win 10 computer with the latest updates. We couldn't reproduce the problem for days, then all of a sudden, we also had the same problem, which now persists.
Does anyone have another idea how we could further narrow down the problem?
Many thanks.