Hi,
We have had several instances, whereby some of our remote users are unable to connect to our remote desktop infrastructure remotely, even though others in the same remote office are unaffected.
Our environment is all 2012 R2, with 2 gateway servers, 2 web access servers, 1 connection broker, and 6 session hosts. Remote clients all connect from our remote offices via the internet, using the web access URL. All our users are using HP t510 thin clients, which run windows embedded standard 7. They are all built off the same image, and connect in the same way.
The last occurrence we had of this, was last night. We had to restart several servers, and when some users tried to log back in, they were unable to do so. The error they receive from the remote desktop client is "Could not log you on to the remote server, as an error occurred on the remote server.". Another user in the same office (connected to the internet via a small ZyXel router, with only 1 external IP address) was able to log in first time no problem.
I have checked the event viewer on each stage of the process (web access, gateway, connection broker, session host), and this is what I have found:
On the gateway server:
16.43.41 - TerminalServicesGateway - "The user XXX\james.edmonds, on client computer "remote_ip", met connection authorisation policy requirements and was therefore authorised to access the RD gateway server. The authentication method used was: "NTLM" and connection protocol used: "HTTP".
16.43.41 - TerminalServicesGateway - "The user XXX\james.edmonds, on client computer "remote_ip", met authorisation policy requirements and was therefore authorised to connect to resource "FLX-RDLS-V001.domain.local".
16.43.41 - TerminalServicesGateway - "The user XXX\james.edmonds, on client computer "remote_ip", connected resource "FLX-RDLS-V001.domain.local". Connection protocol used "HTTP"
On the connection broker:
16.43.42 - TerminalServices-RemoteConnectionManager - "Listener RDP-Tcp received a connection"
16.43.46 - TerminalServices-RemoteConnectionManager - "Remote desktop services: User authentication succeeded: User: james.edmonds, domain: , Source network address: 10.0.0.105"
16.43.46 - TerminalServices-SessionBroker-Client - "Remote desktop connection broker client received request for redirection. User: XXX\james.edmonds, RDP Client Version: 5"
16.43.46 - TerminalServices-SessionBroker - RD Connection broker received connection request for user XXX\james.edmonds. Hints in the rdp file (TSV URL) = tsv://MS Terminal Services Plugin.1.All_Users. Initial Application = NULL, Call came from redirector server = FLX-RDLS-V001. Redirector is configured as virtual machine redirector.
16.43.46 - TerminalServices-SessionBroker - RD connection broker successfully processed the connection request for user XXX\james.edmonds. Redirection info: , target name = FLX-RDSH-V007, Target IP = 10.0.0.113, target netbios = FLX-RDSH-V007, target FQDN = FLX-RDSH-V007.domain.local, disconnected session found = 0x0
16.43.46 - TerminalServices-SessionBrokerClient - Remote desktop connection broker client successfully redirected the user XXX\james.edmonds to the endpoint FLX-RDSH-V007.domain.local. IP address of the endpoint = 10.0.0.113
There are also a couple of events here at 16.43.50 that say: TerminalServices-SessionBroker - This connection request has timed out. User could not log on to the end point within the alloted time. Remote desktop connection broker will stop monitoring this connection request"
The problem here is that we had upwards of 20 users trying to log back in at the same time, so I have no idea if one of these is linked to the above events or not. I don't think they are linked asI then get these events on the SH server:
16.43.47 - TerminalServices-RemoteConnectionManager - Listener RDP-Tcp received a connection.
16.43.51 - TerminalServices-RemoteConnectionManager - Remote desktop services: user authentication suceeded: User: james.edmonds, Domain: XXX, Source network address = 10.0.0.105
16.43.56 - TerminalServices-LocalSessionManager - Begin session arbitration: User: XXX\james.edmonds, Session ID: 3
16.43.56 - TerminalServices-RemoteConnectionManager - Remote desktop services has taken too long to load the user configuration from server \\domain_controller.domain.local for user james.edmonds
16.43.56 - TerminalServices-LocalSessionManager - End session arbitration: user: XXX\james.edmonds, Session ID: 3
16.44.02 - TerminalServices-RemoteConnectionManager - Remote desktop services network fair share was enabled for the user account XXX\james.edmonds with a weight of 1
16.44.02 - TerminalServices-LocalSessionManager - Remote desktop services session logon succeeded. User: XXX\james.edmonds, Session ID: 3, Source network address: 10.0.0.105
16.44.03 - TerminalServices-LocalSessionManager - Remote desktop services shell start notification received: User: XXX\james.edmonds, Session ID: 3, Source network address: 10.0.0.105
I have searched multiple forum posts to try and determine what is causing this, and why it only affects some user's thin clients and not others. In some cases, I don't even see any events on the session host after the connection broker has said it has redirected the connection. Other internal and remote connections to the same session host are ok.
Can anyone offer insight into what might be happening?
Many thanks
Eds