I'm using COM port redirection via RDP. If I assign a COM port number smaller than 32, redirection works fine. I log on to the server and access the device that is connected locally. However, if I assign a COM port greater than 32, I can't access the device from RDP. I get an error "The port COM100 does not exist".
So, is there some limit to RDP com port redirectoions?
Hello!
I have a very strange problem with some Windows 2012 R2 servers. I have sysprep'd and cloned a VM to two new VMs. Accessing them over Hyper-V console works without problems, but if I try to connect using RDP, I get the password prompt, a black window opens and then I'm disconnected without an error message.
The servers do have the latest Windows Updates installed. One server seems to work after a few reboots, but on the other I have no success to login using RDP.
In the event log is the following event logged after every try to login:
ID: 36
Source: TerminalServices-LocalSessionManager
Text: An error occurred when transitioning from Disconnected in response to EvConnected. (ErrorCode 0x800708CA)
I can't find anything with this error code on the internet.
At the same time, there is another event logged which seems less specific:
"Session ... was disconnected. Reason code 11"
Any ideas what I can try?
Deployed windows server 2012 (NOT R2) with Remote Desktop services. Users are complaining that if they go idle (not move their mouse or type) for 2 minutes they get disconnected from RDS. In the collection configuration I turned on Enable Automatic Reconnection, and some users are no longer getting disconnected while some are receiving messages that the servers are reconnecting and eventually reconnects, again within the 2minute idle time. In the Gateway logs I am seeing that the user is getting disconnected and reconnected every 2 minutes. This would be OK however with Enable Automatic Reconnection, all session timeouts are ignored because every time a reconnect takes place all counters are reset, so if I have a 30 minute idle session limit set, 8 hour session limit and 2 hours end a disconnected session, the user never gets disconnected, I have a session open for 24 hours that keeps reconnecting. I've tried setting Keep alive interval via group policy. Is there a setting to prevent the 2 minute idle timeout?
Hi all.
We're trying out our applications using RDP to access them. In order for this to work, clients must access the server via RDP. At the same time, using their RDP they are forwarding local COM ports (in order for some serial device to work).
As it is now, there are different local PC's that have the said device assinged to the same local port. Example: PC1 has a device assigned to COM4, PC2 has another device assigned also to COM4.
Both of them are now using RDP to connect to a Windows Server and they are forwarding their ports.
Does Windows have any mechanism to differentiate read requests from those two devices? I know that on a local machine, two devices cannot occupy the same COM port...but I'm not sure how COM redirecting really works, in other words, will the example I gave you
work without the two user PC's colliding.
If there's any additional info you may need, do let me know.
Thanks :)
I have a Windows 10 client and a Server 2012R2 server. The client is set to 1920x1080 at 125%. In the past, whenever I connected via RDP, the session automatically went to 125%, regardless of the resolution (I sometimes use 1024x768, or other resolutions), just like it is supposed to. In the last few weeks, it has suddenly stopped doing this. I've tried different accounts, making sure I logged off the Server session (not just disconnected), changing the resolution and magnification on the client, and trying different Server 2012 R2 servers. Nothing works. I really don't want to do some of the manifest solutions that others talk about.
It is almost as if an update to either the server or the client has broken this.
Is there some way of diagnosing this? Is there a log of the connections, that would tell me what the client says it is, so I can see if the client isn't reporting the scale factor, or the server isn't paying attention?
Does anyone else have a suggestion, or is anyone else noticing this issue?
Thank you.
Jeremy Heymann Market Mentor Online
I'm running a 2016 RDS environment. I have a unique app that requires a antiquated OS. I've provisioned a Remoteapp which is just a .bat file that calls a Powershell script. The Powershell script simply queries a list of OS's to see if a user is logged on. (not sure if this is a Powershell question or not but i'll start here). Now as an admin launching the remoteapp (bat file) the query works fine, it successfully gets a list of who's logged on to these antiquated servers. When launching the app as a regular user it never successfully returns data. I've tried this script from technet which works great as an admin. I've also used the qwinsta tool which also works fine as an admin. For testing, UAC is off as well as Firewall and still no dice. With auditing on i do see a failure on the RDSH in regards to a sensitive privilege use SeTcbPreivilege which is the act as part of the OS user right. Even if i explicitly give the user this right it doesnt execute right and always just returns that no users are logged on. I know its the interesting way in which this solution is being implemented and how its calling powershell, but I'm just not sure on my next steps here. Looking for some input.
Note that i can publish a shortcut file to the script or batch and it exhibits the same behaviorI'm using RDS/Remoteapp on generally windows 10 clients to fully patched server 2016 hosts.
I'm getting Disconnected due to a protocol error and it's sometimes fixed by rebooting the host. Each host has 8GB of ram and max one user at a time. Even after a reboot it'll often stop working a few minutes later.
Google seems to have no results on this platform and issue over RDS
Hello,
Is there any way to add an image to HTML5 version of RDS web portal?
Thanks
Hello,
I encounter following problem - when admin tries to connect/control another session on the terminal server (from the server) - windows opens but has only black screen. The RDS farm is based on Windows Server 2016.
Any ideas?
Thank you!
hi,
we're suffering from session hosts that produce black screen errors in a RDS 2016 farm.
already connected users can mostly work, all new connections end up with a black screen.
to resolve the error the server has to be restarted.
i can say that
- this error appears after error 1534 (Fehler bei der Profilbenachrichtigung des Ereignisses Delete für Komponente {709E2729-F883-441e-A877-ED3CEFC975E6}. Fehlercode: Das System kann die angegebene Datei nicht finden.) starts appearing in the eventviewer.
- upon checking the registry for this SID i end up at "ProfileNotifyHandler Class app id {E10F6C3A-F1AE-4adc-AA9D-2FE65525666E} inprocserver32, C:\Windows\System32\gameux.dll".
- starting explorer.exe per taskmgr does not open an actual explorer window although the process appears in taskmgr
- tskmgr, eventvwr, cmd can be started without problems
- affected users appear as active in RDS management
- no third party security software is installed
- farm is fully patched
- HKLM\Software\Microsoft\WindowsNT\CurrentVersion\ProfileGUID and ProfileList are ok (no old or .bak entries)
looking forward on how to resolve this without rebooting the server or a permanent fix
thank you
best regards
Hi All,
Is there anyone who can help me. We have a customer which is running server2016 RDS. Now a few users will use skype and wants to use a webcam. At my Windows 10 laptop I have a HP HD camera. At the remote desktop client, I checked the webcam for redirection. But is never appear in a session. I have done some local GPedit settings on the RDS server for remote FX. But untill now without result. Can anyone help me?
Best regards,
Willem
Everything is set up ok and used to work with the 1802. I use a non-standard port.
With 1803, it can't connect to the remote computer.
It seems like a service is not running, as was the case with 1803 with not showing all of my networked computers.
Any thoughts?
I used to be able to access Windows 7 computer from windows SBS 2008. For some reasons I can't. If I try to access it using RDC, I will get this message: "Your computer could not connect to another console session on the remote computer because you already have a console session in progress". I can telnet port 3389. What could be the problem?
Hi,
our workstations with Windows 10 pro are in this weekend updated to version 1803. For main system we use RemoteAPP aplications on Windows server 2012R2 (Windows server 2012R2 is full updated). After update on client station are RemoteAPP slower, and right mouse button is unresponsive, or react verly long time...
It is a big problem for us.
PS: after replace mstsc.exe and mstscax.dll from older version Windows 10 is all OK. but this is not a solution.
Thanks.
Hi,
We have just start to add extra capicity, for our RDS enviroments.
Previous we had 2 connection brokers, and 1 server hosting the Gateway / Web access server.
We then added 2 new gateways, to replace the old one, and planned on using HAProxy as the load balancer, in front of the 2 new gateways.
When users are logging into the RDWeb on the old Gateway server, they are presented with the RemoteApps, that they have in the collection, that the user belongs to.
When users are logging into the RDWeb on the new Gateway servers, they are presented with ALL the remoteapps, that is available accross all of the RDS collections.
We are 100% sure, that the new Gateways and the old Gateways, are in the same RDS "environment" - and can see all the servers, when looking at the SQL database for the brokers.
Normally we would look at the Domain groups, since all the RemoteApps are available - but then the user should see all the RemoteApps, when logging into the old Gateway server as well.
The only error code, that ive found so far are these:
Connection Brokers:
RD Gateway Configuration Failed on rdsgw3.domain.local With Error: Failed to create RAP for RD Connection Broker Computers group. Error = 2147749913
RD Gateway Configuration Failed on rdsgw3.domain.local With Error: Failed to create new RD Connection Broker Computers group. Error = 2147749913
RD Gateway Configuration Failed on rdsgw3.domain.local With Error: Failed to create RAP for Domain Computers group. Error = 2147749913
But the policies are being created correctly, and are present when looking.
rdsgw3.domain.local
The connection authorization policy "RDG_CAP_AllUsers" could not be created. The following error occurred: "183".
The resource authorization policy (RAP) "RDG_AllDomainComputers" could not be created. The following error occurred: "183". To resolve this issue, ensure that you have configured RAP settings correctly and set the correct value and permissions for the RAP.xml file and the RAPStore registry key.
The resource group "RDG_RDCBComputers" could not be created. The following error occurred: "183". To resolve this issue, ensure that you have configured resource group settings correctly and set the correct value and permissions for the RAP.xml file and the RAPStore registry key.
The resource authorization policy (RAP) "RDG_RDConnectionBrokers" could not be created. The following error occurred: "183". To resolve this issue, ensure that you have configured RAP settings correctly and set the correct value and permissions for the RAP.xml file and the RAPStore registry key.
The resource group "RDG_DNSRoundRobin" could not be created. The following error occurred: "183". To resolve this issue, ensure that you have configured resource group settings correctly and set the correct value and permissions for the RAP.xml file and the RAPStore registry key.
The resource authorization policy (RAP) "RDG_HighAvailabilityBroker_DNS_RR" could not be created. The following error occurred: "183". To resolve this issue, ensure that you have configured RAP settings correctly and set the correct value and permissions for the RAP.xml file and the RAPStore registry key.
We cant seem to find the answer to this, so any help is much appreciated!
hi I have configured rds gateway on windows 2012 , one server having all rds role ( connection broker, webapp,rdgateway & remote desktop session host ) as per this kb :https://www.lemonbits.com/2014/06/20/installing-standalone-remote-desktop-gateway-on-the-windows-server-2012-r2-without-complete-remote-desktop-services-infrastructure/
after that now i am getting remote desktop services temporary unavailable .
Reviewed all setting :removed port 80
Internally using RDWeb works ok.
I have added the certificate in Gateway Manager
I need to restrict AD user to its thin client physical mac address so user can logon to its thin client only. We are using Windows Server 2012R2 with Oracle Thin Client, user logon through remote desktop services.
Any 3rd party tool, software or script required.
regards
Rox_Star
Hi All,
I want to take remote connection of my windows server2012r2 vm through webbrowser.I have installed everything by following this link https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-admin.
I have configured everything RD-CONNECTION-BROKER RD-WEB-ACCESS RD-LICENSING RD-GATEWAY after that i can able to connect my windows server to browser but the issue is i cant able to access the resource shown in the browser it is showing "Oops, we couldn't
connect to the "resource-name" The connection to the remote PC was lost. This might be because of a network connection problem. If this keeps happening, ask your admin or tech support for help.
Help me on this many thanks
Hello,
I want to report one issue that is easy to reproduce, it occurs with any rdp client that connects to Windows10 Pro with enabled RDP connections, actually used mstsc.exe to connect from one Windows10 pro machine to another Windows10 pro machine with enabled RDP.
After ~100 tries to restore interrupted connection the server refuses future rdp connection tries with internal error occurred message reported by mstsc.exe.
It doesn't matter if you have logged off the session during running, as example did 20 connection restorings then logged off, logged in and did next 80 connection restorings, that was only example, only what matters is that you have only to restore any interrupted
session at least ~100 times to send server to nirvana. As example after WiFi lost connection or during any network problem that requires rdp connection restoring. Only what helps to restore functionality is to restart remote desktop service in services.msc
I highly assume by restoring connection with reconnection cookie the bug counter counts up and by reaching 100 (the counter seems to be not reset by any action) so finally it completely stops to accept any future connections with internal error occurred
message.
Such error doesn't exist on Windows2016 but Windows10 pro is affected.
More over few months ago this bug didn't exist on Windows10 too.
Please forward this issue to your RDP server developers, thank you!
Sincerely yours.
We have a Server 2016 RDS farm with two collections. The connection broker and the gateway were upgraded from 2012R2 to 2016 server. We followed the Microsoft recommended in place upgrade because we are introducing a new Collection of 2016 RDS host. The farms/collections are working as expected and users are logged into both collections. The old/previous collection has all 2012r2 RDS host and the new collection has all 2016 host.
Here is my issue:
In server manager under the connections pane after highlighting the collection of the 2012r2 collection I can see all logged in users with no issue. In the new 2016 collection I can not see any logged in users although users are connected
and successfully log in. We would like to see connected users in the new farm so that we can use tools such as shadow or force a user to log off. I've opened server manager on several servers, including the connection broker and a domain controller
thinking it was maybe my windows 10 RSAT that was having the issue, but none show users for the new 2016 farm.