This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 54%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Hello everyone,
We've build new RDS-Farm:
1) RDCB+RDLS+RDS WebAccess
2) Session-Host
3) Session-Host
4) Session-Host
5) Session-Host
we getting strange issue, users randomly disconnected from session for one second and then they reconnect again
I did deep research and didn't find much information only some related events.
there is no network related issue and firewall also
Does anyone has any idea what it's could be?
Hello @risolis
the "TURN_OFF_UDP" solution that's what i did on standalone workstation for testing purpose.
but I won't apply this solution for all workstation\laptops cause many of them not in domain.
and the our client won't approve this solution.
we need to find a solution on servers side
Have you tried to do it from here???
How Do I Enable A Port?
Right-click the Start button.
Click Search.
Type Windows Firewall.
Click Windows Firewall.
Click Advanced settings.
On the left side, click Inbound Rules.
You will find it in the right part of the window under New Rule…
Click Port.
Looking forward to your response.
Regards,
Hello @Arnold MIshaev
I am wondering if you were able to check the previous post but besides this, I want to bring this other way as well:
$portvalue = 3390
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -name "PortNumber" -Value $portvalue
New-NetFirewallRule -DisplayName 'RDPPORTLatest-TCP-In' -Profile 'Public' -Direction Inbound -Action Allow -Protocol TCP -LocalPort $portvalue
New-NetFirewallRule -DisplayName 'RDPPORTLatest-UDP-In' -Profile 'Public' -Direction Inbound -Action Allow -Protocol UDP -LocalPort $portvalue
Looking forward to your response.
Regards,
Hello @risolis
thanks for your reply.
but I found the cause to our issue.
it's seems like clients use UDP and TCP to connect to our RDS-Farm, I took one workstation in our production and turn off UDP on his workstation by adding next registry key
now the question his how do i turn on UDP on Session-Hosts servers
Hello @Arnold MIshaev
Thank you a lot for your response.
I found this info below:
It's an issue also with Win 10 1809 to Win 10 1809
You can work around this by disabling UDP session used by MSTSC on your affected Win 10 1809 computer (the one where you're running the Remote Desktop client).
Run Group Policy Editor. Navigate to Computer Configuration > Administration Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client. Set the "Turn Off UDP On Client" setting to Enabled.
Try connection again in MSTSC. Should work OK. No reboot required.
Furthermore, I found this info too:
Looking forward to your feedback,
Cheers,
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Hello @Arnold MIshaev
Many thanks for that great info.
I would like to give you this step below and I hope you can confirm the settings or do what is necessary.
When the Remote Desktop client reconnects, the RDSH server reconnects the client to a new session instead of the original session. However, when you check the RDSH server, it says that the original session is still active and didn't enter a disconnected state.
To work around this issue, you can enable the Configure keep-alive connection interval policy in the Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections group policy folder. If you enable this policy, you must enter a keep-alive interval. The keep-alive interval determines how often, in minutes, the server checks the session state.
This issue can also be fixed by reconfiguring your authentication and configuration settings. You can reconfigure these settings at either the server level or by using group policy objects (GPOs). Here's how to reconfigure your settings: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security group policy folder.
On the RD Session Host server, open Remote Desktop Session Host Configuration.
Under Connections, right-click the name of the connection, then select Properties.
In the Properties dialog box for the connection, on the General tab, in Security layer, select a security method.
Go to Encryption level and select the level you want. You can select Low, Client Compatible, High, or FIPS Compliant.
Looking forward to your feedback,
Cheers,
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 40%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBL%3C/text%3E%3C/svg%3E)
I'm very Happy to be able to use Microsoft Edge
Hello @risolis
Thank you for your respond.
1) it's seems like the "Remote Desktop Session Host Configuration" doesn't exist anymore in newest windows server versions.
but if you mean session limits so there is no limit for a session limits
we did packet capturing and you can see that the communication work on protocol TLSv1.2
