RDP Error 2308 after Update to 7.1

[BenS]

We are getting this RDP Error 2308 (Attachment) after updating to 7.1. When using the RDP Client outside ASG all is fine. Destination server are all behind a VPN. Anyone has an Idea? Thx

[DevOma]

Can you try go back on Patch6? Just install over… We only add a field for load balancing but this field should not be set if it is empty

[BenS]

Can you try go back on Patch6? Just install over… We only add a field for load balancing but this field should not be set if it is empty

I went all the way back to Patch 2 and still have this problem. Like I said bevor if I us the windows mstsc.exe client I do not have this problem. I have the feeling ASG reacts more sensitive to network problem then the mstsc.exe defaults. For some reasons it only started to come up now.

https://social.technet.microsoft.com/wik...ected=true

2308 Error Code:
Your Remote Desktop Services session has ended.  The connection to the remote computer was lost, possibly due to network connectivity problems. Try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support.

[DevOma]

Ok this error is not the one we had with Patch7/7.1 - and yes it could be that mstsc react not in the same way like our app is doing - but it's nearly impossible to get the difference in the available settings.

[BenS]

Ok this error is not the one we had with Patch7/7.1 - and yes it could be that mstsc react not in the same way like our app is doing - but it's nearly impossible to get the difference in the available settings.

Thx for your answer, how can we move forward from here? The Problem is that we have 15 IT/Support technician sitting here and working with most 2016 Server via. ASG is mostly impossible at the Moment.

Shall I start a Support Call via. asgsupport@asg.com?

[DevOma]

Make no sense - they will redirect you to this forum…

Did it work before you upgrade to Patch7/7.1? Then it must work if you override it again with a patch level <= Patch6...

If you google for "RDP 2308" you will find a lot of entries that tries to fix these problems (not regarding to ASGRD) but perhaps something helps - I do not know what we can set in another way to prevent this error - and be sure I invest some time before to find a solution

[BenS]

Make no sense - they will redirect you to this forum…

Did it work before you upgrade to Patch7/7.1? Then it must work if you override it again with a patch level <= Patch6...

If you google for "RDP 2308" you will find a lot of entries that tries to fix these problems (not regarding to ASGRD) but perhaps something helps - I do not know what we can set in another way to prevent this error - and be sure I invest some time before to find a solution

We did some in-house testing the error only occurs on Win 10 machines with ASG. Win 7 machines with ASG 7.1 are fine.

[BenS]

By the way, this Problem is still present in V. 2019 P2.

[BenS]

We still have this Problem. The odd thing is that if you reconnect two to three times the RDP Sessions is stable.

[Michael Scholz]

Hi Ben,

sorry that we don't have a solution from program side. The problem is a pure RDP thing and you can find many articles in the web pointing to different solutions to these kind of connection problems with RDP like changing the RDP Experience settings or adjusting firewall settings and stuff like that. Another problem is that the RDP control sometimes behaves not exactly like mstsc.exe even though it's also used there. So if such problems occur some tweaking might help and also recheck if the problem is related to the OS-version or OS and/or account restrictions.

Best regards,
Michael