Hello Everyone,
I'm getting a Authentication error on all of my Windows 2012 servers connecting through RDP. The weird thing is, this error only pops up using the DNS name. If I use the IP of the server, I connect with no issues or errors.
Does anyone have any ideas?
Please let me know
Thank you
Devon
Hi, after install the webclient and bind certificate to port 3392, I get this error message.
WebSocket connection to 'wss://dc.redecr.intranet:3392/rdp' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT
There is no firewall between the client and the server, the port 3392 is open on RDS Server 2016.
Any ideas?
Thank You
Cesar Ramalheiro Jr
Hi all,
I've been researching this but still non the wiser as the information on various websites is so confusing. Just want to make sure we're compliant.
So we have a Server where the data is stored and some applications installed. We also have 8 members of staff and everyone has 1 desktop PC so 8 PC's in total. PC's are not Domain joined, they are just on a Workgroup.
Every PC/user is accessing the data from the server via Mapped network drive (if they only need to work on basic documents such as Word or Excel). Also each user/PC needs to connect to the Server via Remote Desktop to use a couple of applications that are installed on it (as well as to access the same data mentioned before).
There are only 3 roles installed on the server: AD (to create users for Remote Desktop connections), RD (to allow Remote Desktop connections) and of course File Server.
Up until recently the server was running on 2008 R2 and there were 10 USER CALs installed too. No RDS CALs though. Everything was/is working fine, everyone is able to access the server via Remote Desktop simultaneously, etc.
Now we are upgrading to 2016.
What I am trying to figure out is what licences do we need?
I never came across RDS CALs before (not sure whether this is a new thing or whether I was just completely ignorant).
I am thinking to go with Device CALs instead of User CALs this time (we have 8 users and 8 PC's in the office and nobody ever needs to work from home or other remote locations so I guess there is no difference, but Device CALs are cheaper, LOL). I have already purchased a 10 pack of Device CALs.
But based on the scenario outlined in the beginning of this post - do we need RDS CALs too? Or not?
Also the Device CAL licence paperwork only came with a sticker with Tracking ID on it but no actual 25 character serial number. I have contacted my re-seller (Dell) and they told me that this is how it works these days. Apparently Microsoft has introduced a honor system and that sticker with Tracking ID is all we need in case of an audit.
But then my question is how the server will know how many Remote Desktop connections it should accept/allow simultaneously? Will it accept unlimited number of connections and we're compliant as long as we don't have more than 10 users/PC's?
Thanks in advance and sorry if my questions have already been answered somewhere else.
Hi guys,
On a random base (daily, weekly) we're experiencing major log-in problems on our Windows Server 2012 R2 Remote Desktop Services farm. The VM's are hosted on Hyper-V 2008 hosts and we're not using Citrix techniques etc.
Users are reporting that they cannot log-in, the log-in sessions hangs with a blank screen when loading their user profile (e.g. Please Wait For The User Profile Service).
In the System event log of the server on which the user is logging on the following errors are shown:
Source: Service Control Manager
Date: 23-12-2014 7:28:01
Event ID: 7011
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
…and after 30 (or sometimes 60) seconds, the same error only another service (in random order):
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
…and after exactly 30 seconds, the same error only another service:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UxmSms service.
etcetera, with the following errors:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Netman service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AudioEndPointBuilder service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WPDBusEnum service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
The Portable Device Enumerator Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the TrkWks service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
These errors are logged continuously.
An administrator cannot solve this since he isn't able to login in as well (console or remotely), only a hard reset of the VM is possible to use the affected server again.
I took different steps to solve this problem without any success, like:
- Installing the latest Windows updates
- Removed unnecessary printer drivers, print monitors and print processors (no local printers/drivers are installed, only Remote Desktop Easy Printer driver is used)
- Searched different forum posts, but found only hotfixes for Windows Server 2008 R2.
Can someone please help me with this annoying problem?
Many thanks!!
EDIT:
Of course is increasing the time-out not really an option here... http://social.technet.microsoft.com/wiki/contents/articles/13765.event-id-7011-service-timeout.aspx
Hello,
I have windows10 pro build 1809 with the last updates …. when I try open any remoteapp the authentication not working and askme always for user name and password.
I tried with muilti defernets server but it's not working !
so whats the problem ?
thanks.
Microsoft Lover
hi all,
Win server 2016 connection brokers, 2012 R2 session hosts (due to application requirements), currently 154 session hosts in farm.
if i logon to specific session host, using mstsc.exe /admin, first logon time is approx 8 seconds. Subsequent logons are approx 3 seconds.
if i logon via the farm ()via rdweb, or an rdp file downloaded via RDWweb), the logon times are 18 seconds and 13 seconds respectively.
It seems to me as if the farm negotiation and deciding where to place the client is taking a full 10 seconds - which just ruins the user experience.
i havent been able to find anything by googling this - has anyone got some suggestions as to what to check or what tools i can use to troubleshoot this ?
When I log onto our rds gateway, I see the Remote Dektop Icon from the collection object I created.
But when I click on the icon, the local RDP client starts. It should just give me a login dialog.
Anyone seen/solved this before?
Hi guys,
Currently I work in project to allow all users access que RD Web Access.
In this project I need allow the all users access the web page automatic, I don't know what's the paramenters I need to change in the web.config file.
Could you help me ?
Thank's!
Marcus
Getting to where I HATE certs.
2 node 2016 RDS farm. Generated a SAN cert from my MS CA. It contains common name *.xxx.xxx. The SAN names are the Farm FQDN and the FQDN of both servers.
Imported this into the Server Manager RDS Deployment Properties successfully.
It WORKED properly after I imported those 2 certs that afternoon, several times.
Then, the next day, the 2nd server (not the first) decided it would use the Self-Signed RDS cert it has rather than the SAN cert assigned the previous day.
So, I have 1 server (which is a Gateway and session host) use the SAN cert, but the 2nd (session host only) uses a self-signed.
WHY? Any suggestions on how to fix?
Hi Guys
I am running a 2012R2 RDS environment with 'HA' Connection Brokers with SQL in the background hosting the RDS DB. All working nicely. What I have noticed however is that if I use the 'Active' Broker Server Manager (GUI) to update Collection or RemoteApp settings, I seem to get inconsistent results. Before I give a couple of example, What is the best practice for updating Collection or RemoteApp settings in an HA Broker/SQL enviroment? GUI or Powershell? Or should the both give exactly the same result?
Thanks!
Hello everyone, I am in need of some help with my setup of Remote Desktop Services (RDS).
So for my setup, I have 2 physical machines(Server A & Server B) which are running Windows Server 2016 Standard on them.
Server A have the following features installed - Broker, Web, Gateway, License, Host.
Server B have the following feature installed - Host.
Both of the servers are joined to an Active Directory (AD) and I have created a RDS Farm to house the 2 servers.
Under the collections, I have created a new collection (Collection01) and allowing the access from a certain user group.
My question is that, am I able to fix the user to the Server that he have entered before, so that he won't be swing around between 2 Servers ?
The broker will help to load balance only at the initially login of the user.
is there any way to Restrict the users from access the network resources only allow them to join domain controller.
When connecting to our RDS service, the user can use their credentials and get past the first screen, to the
Remote (Collection) Icon, but when they click on it it, the following appears:
If you offer solutions, please tell me which server any corrective action should be taken on. Still learning.
I've been having a tough time finding a clear answer on this, so I hope someone can shed some light on this for me.
I have a few RDP Windows Server 2016 Datacenter Servers in Azure that I want to enable more than 2 concurrently RDP Sessions on. This I would assume now is called a CAL license Such as mentioned here https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-client-access-license ..... Now I would need per device as we are using these in a workgroup with no active directory and this is for security reasons with an outside company coming into my Point-To-Site VPN connection.
Where do I go to get these licenses and what exactly do I need to setup? From my past experience with AD, I would setup a license server like it describes in the link and I had the company get me licenses to add to the server.
Now I believe I have to setup the same kind of server, but where do I get these licenses from exactly? I am supposed to grab these myself and can't find any easy way to get these. Would like a straight answer on that if possible.
Also why is it so complicated to get these licenses? I find it overly complicated and hard to find information or straight answers to do this. Maybe Microsoft should think of making this easier in such areas like Azure and implement it in Azure itself? Just a thought lol
Any help would be much appreciated to stop me from pulling my hair out on this one
Thanks
Issue: User Logs onto Client Machine remotely, then connects to Corp VPN and does RDP to any Corp machine. In case the VPN disconnects or client machine loses network connectivity momentarily, the RDP session re-establishes the connection. When it re-establishes a connection, it logs a bad password attempt on the users account. If this happens too many times, users are experiencing account lockout.
Upon checing the logs, I see that the Terminal Service is sending the bad password.
Can anyone suggest what could be the possible issue?
hi
for past months , every time we created a new PC we added some users in the Remote desktop users ( including user himself ) , now we have a new security policy that avoid the user to be in RDU list , how can i remove the users and keep others through GP ? i know how to add , but remove its not work for me.
in simple word i need to create policy , and put name in it , then deploy that policy to over wright the current names.
Osma Othman
We are running a 2016 Datacenter server under Azure. The server is primarily an RDS running Office Pro Plus and a couple of SQL backed applications.
Since Monday we've had problems with the user experience, with applications failing to clear down (Chrome was installed, would open once and close but then fail to open again - Chrome process remaining in background.)
The notifications for printing, new emails etc would appear but then fail to close afterwards. Left click on the start button would stop working and user experience was generally poor with noticeable lag on moving items on the screen. This sounds like a Shell type issue.
We have removed Chrome, disabled Skype for Business through GP, dialed down AV. We have run SFC /Scannow which found errors and fixed all except problems with Task Scheduler.lnk
Server is back up and we're waiting for it to happen again. Latest patch KB4489889 is applied, though this came out after the first problem.
What else might I have missed?
Hello,
I've been having an issue connecting to new RDS deployments, either Server 2012R2 or 2016, using the modern client (UWA?).
If I connect to the rdweb site via browser, any browser (Chrome, IE, Edge), I can connect fine w/ the downloaded RDP file, either via the old mstsc client, or the modern client. If I open the modern client and add my deployment as an RDS resource, it adds file, but when I try to connect, it doesn't do anything. Monitoring network traffic, it doesn't even try to connect to the rpcproxy.dll,or even send any packets on the wire to my gateway.
Doing some digging, I see the rdp file is saved in my user profile (C:\Users\#####\AppData\Local\Packages\Microsoft.RemoteDesktop_8wekyb3d8bbwe\LocalState\RADC\{9AFF1AD1-C68D-FC28-FA01-4BD806FA43E4}-Committed\Resource) without an extension. If I copy the file from there, give it a .rdp extension, I can also connect with that file via either client.
I also don't appear to be able to add the remote resources, at all, via the IOS RD Client. I haven't tried Mac or Android yet, waiting to stabilize this config, but perhaps that's a separate issue. I don't see it trying to logon or connect to webfeed.aspx on the RDSWeb page at all.
These would all be the lastest iterations of the clients, I just started this whole setup about a week ago. I've tried a standard deployment in 2016, then a quick deployment in 2016, and finally a quick deployment in 2012 R2. I'm familiar with all the cert requirements, etc, I don't think it is any sort of cert issue. I will say the 2012 R2 quick deployment seemed to work OK initially, until I added 2016 session hosts to the deployment, but now I can't say for sure. If needed, I could do another quick deployment to verify.
Any insights would be great. If we can only use rdweb and have users open RDP files I guess we're OK with that, but not ideal.
Thanks!
-jg
Hi, I've this issue after migration of RDS server from 2012 R2 to 2016 and client have Windows 10 1709 but with Windows 10 1703 no issue.
Any suggestions?