| Posted by: Lemonde - 14 September 2020 12:45:32 |
|---|
| Any idea what is causing this? This user could log in last week but now we cannot get them logged in for toffee or even hard cash!!! Log Name: Microsoft-Windows-TerminalServices-SessionBroker/Admin Source: Microsoft-Windows-TerminalServices-SessionBroker Date: 14/09/2020 12:40:20 Event ID: 802 Task Category: RD Connection Broker processes connection request Level: Error Keywords: User: NETWORK SERVICE Computer: RemoteDesktopHost.domain.local Description: RD Connection Broker failed to process the connection request for user domain\user. Error: Element not found. Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-TerminalServices-SessionBroker" Guid="{D1737620-6A25-4BEF-B07B-AAC3DF44EFC9}" /> <EventID>802</EventID> <Version>0</Version> <Level>2</Level> <Task>101</Task> <Opcode>11</Opcode> <Keywords>0x4000000000000000</Keywords> <TimeCreated SystemTime="2020-09-14T11:40:20.440877500Z" /> <EventRecordID>52</EventRecordID> <Correlation ActivityID="{F42086DC-BDEE-44C2-9DA3-EE625CB50000}" /> <Execution ProcessID="3040" ThreadID="188592" /> <Channel>Microsoft-Windows-TerminalServices-SessionBroker/Admin</Channel> <Computer>Desktop.domain.local</Computer> <Security UserID="S-1-5-20" /> </System> <UserData> <EventXML xmlns="Event_NS"> <param1>domain\user</param1> <param2>Element not found. </param2> <param3>0</param3> </EventXML> </UserData> </Event>[/code] It just refuses saying: This Computer Can't Connect to the Remote Computer. Try Connecting Again. If the problem continues, contact the owner of the remote computer or your network administrator [img=https://www.sircles.net/downloads/rdgerror.png]This Computer Can't Connect to the Remote Computer.[/img] Connecting fine all last week and now an update has ruined me!!! |
| Posted by: Lemonde - 14 September 2020 13:04:00 |
|---|
| So eventually we had to do the following after everything else we could think of failed: Log into a domain controller Find that user in AD Open Properties and go to [i]Remote Desktop Services Profile[/i] Tick [i]Deny this user permissions to log on to Remote Desktop Session Host server[/i] [img=https://www.sircles.net/downloads/denyts.png]Deny this user permissions to log on to Remote Desktop Session Host server[/img] Click Apply Untick Click Apply And it was resolved. It still took a few minutes to get the user logged in afterwards as the profile loaded very slowly the first time. |
| Posted by: drdread - 14 September 2020 14:02:25 |
|---|
| This can also be a maximum connections reached issue - check licensing for RD CALs and RD Gateway CALs |
| Posted by: Lemonde - 15 September 2020 23:18:35 |
|---|
| Yes the licensing can also produce this problem - if you exceed the number of licenses by double then the RDS server will no longer permit connections from clients and you will receive the This Computer Can't Connect to the Remote Computer. Try Connecting Again. If the problem continues, contact the owner of the remote computer or your network administrator Message. |
| Posted by: drdread - 17 September 2020 11:13:52 |
|---|
| There is a limit on Server 2012 of 250 users and I think if you have built your domain from a SBS 2011 server there is a limit of 25 I am not sure where this live in ADSIEdit though. |
| Posted by: Lemonde - 17 September 2020 11:22:02 |
|---|
| Is there a Group Policy that dictates how many concurrent users can log in? |