Posts: 11
Threads: 2
Joined: Dec 2018
Reputation:
0
Hello,
We have the following situation ASG Connects to Server via. RDP but the session terminates after about 10 Sek. With Return code: 4. Please see the attachmen. The funny thing is, that if I manual reconnect for three times in a row the session will stay open.
We tried to change all the possible setting in ASG for RDP but no luck yet. Anybody got an idea?
ASG = ASG-RD 2019 - Patch3 (Build 12.0.6342.1)
Thanks
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
Return Code 4: The remote session ended because the total logon time limit was reached. This limit is set by the server administrator or by network policies.
Must be any setting on the remote machine?!?
Regards/Gruss
Oliver
Posts: 11
Threads: 2
Joined: Dec 2018
Reputation:
0
Posts: 11
Threads: 2
Joined: Dec 2018
Reputation:
0
18-06-2019, 01:24 PM
(This post was last modified: 18-06-2019, 01:26 PM by BenS.)
I did some further testing today. We have about 160 server from 2008 R2 to 2016 in ASG located in different branches. All are connect via. VPN and we are using WatchGuard Firewalls as VPN devices.
The Problem only occurs with 2016 Server behind two VPN Connections. I really tripled checked all firewalls and the devices are everywhere the same and they are all configure identical.
The problem with Remote Desktop (Return code: 4 and sometimes Return code: 2308) only occurs if I us Remote Desktop within ASG. If I us mstsc outside ASG I never have this issues.
To me it feels like the terminal service of 2016 uses a higher encryption method with makes the RDP session in general more sensitive for any network delays or whatsoever. Nevertheless, mstsc outside ASG seems to use some different settings which make the session more robust. I know ASG uses the windows mstsc client but there must be a difference.
We have an active service contract and pay yearly 924 € for support und updates. We would kindly appreciate if someone from ASG would help us to look in to this. Thank you
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
It's always difficult to find issues that we can't reproduce - I know that doesn't help you because you have the problem...
We will have a look into some settings - check if there are new ones - but believe me, only mstsc-group from Microsoft knows everything about the ActiveX - I had this in the past, there are some undocumented properties that are used by mstsc.exe that nobody else knows... not easy to get these information...
Regards/Gruss
Oliver
Posts: 11
Threads: 2
Joined: Dec 2018
Reputation:
0
19-06-2019, 10:52 AM
(This post was last modified: 19-06-2019, 10:53 AM by BenS.)
Dear Oliver,
Thank you for your reply. I can reproduce the issue here and I am happy to provide you with a test client via. TeamViewer or a different remote tool. You can access the test client for how long and often you want.
Please contact me whenever it suits you. Thank you
Tel.: +49.30.293 98 - 134
Mail: b.dumpf@procado.de
Posts: 11
Threads: 2
Joined: Dec 2018
Reputation:
0
Dear Oliver,
Thank you for your link. I have found this thread myself and examinedet our firewalls after. The issue seems to be a different one. The problem with Remote Desktop (Return code: 4 and sometimes Return code: 2308) only occurs if I us Remote Desktop within ASG. If I use mstsc outside ASG I never have this issues. I do not want to exclude a Firewall/Network issue entirely but since mstsc outside ASG does not have the same behaviour I guess the issue must be within ASG.
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
Yes seems to be that we do not use the ActiveX the same way like MS do - but currently I have no idea how we could check that...
Regards/Gruss
Oliver
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
We never found the reason for that issue...
Regards/Gruss
Oliver
