Hello guys!
I can't get answer on
my local technet forum, because i ask in here.
One user can't connect to RemoteApp. It instead the program displays a black screen.
I have some test:
- Starting RemoteApp Terminal Server №1s under my account, I login undermy account to the client computer - has successfully connected.
- Starting RemoteApp Terminal Server №1 under my account, I was connected with auser account to the client computer - is not successful
- Starting RemoteApp Terminal Server №1 under the user's credentials when I connect with auser account to the client computer - is not successful
- Starting RemoteApp Terminal Server №2 under my account, I login undermy account to the client computer - has successfully connected.
- Starting RemoteApp Terminal Server №2 under my account, I was connected with auser account to the client computer - successful
- Starting RemoteApp Terminal Server №2 under the user's credentials when I connect with auser account to the client computer - successful
TS №1 - Windows Server 2012 TS №2 - Windows Server 2012 R2
After analyzing the situation revealed several types of errors occur when connecting to a RemoteApp everywhere. Several user's have problems. If you connect simply RDP, using the gateway, then it works.
1. Black screen. (The above analysis was given situation)
Error: There is no possibility to get a log, I can throw a little later.
2. When the login and password will not allow - "An attempt to login fails." Under other data connection to RDP works.
Errors:
RDPClient_TCP: An error occurred during the transition from TcpStateFrontAuth in TcpStateFailure in response to the 7. (Error code: 0x0).
RDPClient_TCP: An error occurred during the transition from TcpStateFrontAuth in TcpStateFailure in response to the 7. (Error Code: 0x8009030C).
RDPClient_SSL: An error occurred during the transition from TsSslStateHandshakeStart in TsSslStateDisconnecting in response to the 7. (Error code: 0x80004005).
RDPClient_SSL: An error occurred during the transition from TsSslStateDisconnected in TsSslStateDisconnected in response 25. (Error code: 0x8000FFFF).
Windows 7 Professional VLSC image
3. When you connect to RemoteApp - "RemoteApp programs off - Unable to connect to a remote computer"
Errors:
RDPClient_TCP: An error occurred during the transition from TcpStateConnectingTransport in TcpStateDisconnected in response to 2. (Error code: 0x80004004).
4. Attempts to connect to the RemoteApp 5-60 minutes, but it is impossible. Errors client writes.
Errors:
RDPClient_TCP: An error occurred during the transition from TcpStateConnectingTransport in TcpStateDisconnected in response to 2. (Error code: 0x80004004).
RDPClient_SSL: An error occurred during the transition from TsSslStateHandshakeInProgress in TsSslStateDisconnecting in response to 8. (Error code: 0x80004005)
All the updates are installed. All users have the right to access. Windows 7 Professional.
I feel in the jamb of the RDS.
1. Gateway / Broker
The credentials used to connect to, have not worked.
Connection name:
URL-address connection: https: //domain/rdweb/feed/webfeed.aspx
Error Code: 0x8007052E, 0x0
Client Connection Broker Remote Desktop was unable to redirect the user domain \ Username.
Error: NULL
The user domain \ Username on the client computer "212.19.138.3" meets the requirements of the authorization policy resources and authorized to connect to the resource, but because of the mismatch of the resource "IP TS 2012 №2 Windows Server
R2" resource authorization policy requirements the connection is not authorized. Try to connect to other network resources or reduce the level of safety RD Gateway by modifying the connection authorization policy requirements.
2. TS №1 Windows Server 2012:
Setting the default connection is canceled. Connecting the default can not be used in the system, part of the deployment of Remote Desktop Services.
3. TS 2012 №2 Windows Server R2:
Remote Desktop Services have spent too much time to load the user configuration to the server \\ dc.domain for the username
Setting the default connection is canceled. Connecting the default can not be used in the system, part of the deployment of Remote Desktop Services.