This could be a few things, most likely that port 4172 UDP/TCP is not opened in the firewall.
As priously 4172 TCp are opend. and now i open both UDP/TCP.
Not configured the PCoIP Tunnel correctly, have a look at the config options for the connection broker.
I am directly connection to connection server i dont’ have install «Security Server» so i don’t enable «PCoIp Secure Gateway»option .
Further ,
I would strongly recommend not to use IP:s, use proper FQDN:s instead, you will never be able to secure it or loadbalance properly if using IP:s.
Still for testing we use Ips, for production we may use FQDN.
As i clear priviously , Many of time i connected to Pool as.
Vmware view Error is
«User»,»Severity»,»Time»,»Module»,»Message»,»Objects»
«compnay\my.name»,»Audit success»,»3/4/2013 2:11 PM»,»Connection Server»,»User compnay\my.name has logged out»,
«compnay\my.name»,»Info»,»3/4/2013 2:10 PM»,»Connection Server»,»User compnay\my.name requested Pool View7Regional02, allocated machine vm-view7r2001″,»POOL:View7Regional02 DESKTOP:vm-view7r2001 «
«compnay\my.name»,»Info»,»3/4/2013 2:10 PM»,»Connection Server»,»User compnay\my.name requested Pool View7Regional02″,»POOL:View7Regional02 «
«compnay\my.name»,»Info»,»3/4/2013 2:10 PM»,»Agent»,»The agent running on machine VM-VIEW7R2001 has accepted an allocated session for user compnay\my.name»,»POOL:view7regional02 DESKTOP:VM-VIEW7R2001 «
«compnay\my.name»,»Audit success»,»3/4/2013 2:10 PM»,»Connection Server»,»User compnay\my.name has logged in»,
«compnay\my.name»,»Warn»,»3/4/2013 1:07 PM»,»Agent»,»The pending session on machine VM-VIEW7R2001 for user compnay\my.name has expired»,»POOL:view7regional02 DESKTOP:VM-VIEW7R2001 «
Some of the time i encounter error
Recently I found myself looking at an error which I’ve seen many times before with different customers View environments in which they are unable to connect to desktops getting the following error..
«The connection to the remote computer ended»
In 99% of cases this is usually due to missing firewall rules between the View Client (thick/thin client) and the View Agent (virtual desktop).
The following VMware KB details this error and how to troubleshoot.
http://kb.vmware.com/kb/2013003
However it only affected my test Windows 8 clients which were previously working.
The only thing that has changed was I had been applying and testing the CIS benemarks for Windows 8 in some new GPOs I had created, it had to be those what had broken it, so I set out trying to find which setting.
Unlinking the new CIS GPOs I found I could now connect to my View desktop succesfully so it definatley a setting in the CIS GPOs. The tough job was going through each setting and testing it to find which (initial guess work was not sucessful).
In the end I found the cause to be the following setting:
“System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing Enabled”
This setting being configured to enabled, caused a conflict with the View 4.5 connection server settings in the environment which resulted in connections to the View agent from a View client with this policy setting to be rejected.
This could be a few things, most likely that port 4172 UDP/TCP is not opened in the firewall.
As priously 4172 TCp are opend. and now i open both UDP/TCP.
Not configured the PCoIP Tunnel correctly, have a look at the config options for the connection broker.
I am directly connection to connection server i dont’ have install «Security Server» so i don’t enable «PCoIp Secure Gateway»option .
Further ,
I would strongly recommend not to use IP:s, use proper FQDN:s instead, you will never be able to secure it or loadbalance properly if using IP:s.
Still for testing we use Ips, for production we may use FQDN.
As i clear priviously , Many of time i connected to Pool as.
Vmware view Error is
«User»,»Severity»,»Time»,»Module»,»Message»,»Objects»
«compnaymy.name»,»Audit success»,»3/4/2013 2:11 PM»,»Connection Server»,»User compnaymy.name has logged out»,
«compnaymy.name»,»Info»,»3/4/2013 2:10 PM»,»Connection Server»,»User compnaymy.name requested Pool View7Regional02, allocated machine vm-view7r2001″,»POOL:View7Regional02 DESKTOP:vm-view7r2001 «
«compnaymy.name»,»Info»,»3/4/2013 2:10 PM»,»Connection Server»,»User compnaymy.name requested Pool View7Regional02″,»POOL:View7Regional02 «
«compnaymy.name»,»Info»,»3/4/2013 2:10 PM»,»Agent»,»The agent running on machine VM-VIEW7R2001 has accepted an allocated session for user compnaymy.name»,»POOL:view7regional02 DESKTOP:VM-VIEW7R2001 «
«compnaymy.name»,»Audit success»,»3/4/2013 2:10 PM»,»Connection Server»,»User compnaymy.name has logged in»,
«compnaymy.name»,»Warn»,»3/4/2013 1:07 PM»,»Agent»,»The pending session on machine VM-VIEW7R2001 for user compnaymy.name has expired»,»POOL:view7regional02 DESKTOP:VM-VIEW7R2001 «
Some of the time i encounter error
Recently I found myself looking at an error which I’ve seen many times before with different customers View environments in which they are unable to connect to desktops getting the following error..
«The connection to the remote computer ended»
In 99% of cases this is usually due to missing firewall rules between the View Client (thick/thin client) and the View Agent (virtual desktop).
The following VMware KB details this error and how to troubleshoot.
http://kb.vmware.com/kb/2013003
However it only affected my test Windows 8 clients which were previously working.
The only thing that has changed was I had been applying and testing the CIS benemarks for Windows 8 in some new GPOs I had created, it had to be those what had broken it, so I set out trying to find which setting.
Unlinking the new CIS GPOs I found I could now connect to my View desktop succesfully so it definatley a setting in the CIS GPOs. The tough job was going through each setting and testing it to find which (initial guess work was not sucessful).
In the end I found the cause to be the following setting:
“System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing Enabled”
This setting being configured to enabled, caused a conflict with the View 4.5 connection server settings in the environment which resulted in connections to the View agent from a View client with this policy setting to be rejected.
I recently ran into an interesting issue where I went through a series of troubleshooting steps that eventually led me to reinstalling the VMware Horizon View Agent on a master image but quickly realized I wasn’t able to. The error messages I was presented wasn’t too helpful so I thought writing this blog post may help others who may encounter the same problem.
The whole process started off with an administrator asking me to look at why a user wasn’t able to connect to their virtual desktops after we recompose their VDI with the latest snapshot that recently had 2GB of Windows updates installed. The user would attempt to log onto the View environment as such:
The Connection Server is preparing the desktop…
They would see a black screen as such:
Then they would get cut off and displayed the following error message:
VMware Horizon Client
The connection to the remote computer ended.
Suspecting the PCoIP logs would assist with the troubleshooting, I browsed over to the desktop’s VDMlogs folder:
\VDI-001c$ProgramDataVMwareVDMlogs
… then opened one of the pcoip_agent logs to review the entries. Some of the entries I noticed were:
Server died.
… and:
disconnect reason: 0
The follow log entries are as follows:
11/17/2015, 14:02:36.374> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x9bd8fbc8ee73a36a} [5] Adding session to list.
11/17/2015, 14:02:36.374> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x9bd8fbc8ee73a36a} [5] Total number of active sessions = 1
11/17/2015, 14:02:36.374> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x9bd8fbc8ee73a36a} [5] Sending connection response ok.
11/17/2015, 14:02:36.374> LVL:2 RC: 0 AGENT :pcoip_agent_connect_req: {s_tag:0x9bd8fbc8ee73a36a} [5] connection_response (end), 0
11/17/2015, 14:02:36.562> LVL:2 RC: 0 AGENT :monitor_soft_hosts: {s_tag:0x9bd8fbc8ee73a36a} Server died.
11/17/2015, 14:02:36.671> LVL:2 RC: 0 AGENT :tera_agent_disconnect [soft host]: agent close code: 6, disconnect reason: 0
11/17/2015, 14:02:36.671> LVL:2 RC: 0 AGENT :tera_agent_disconnect: {s_tag:0x9bd8fbc8ee73a36a} disconnect is ** NOT ** pending (hndl: 5, pid: 924, process handle: 0000060c)
11/17/2015, 14:02:36.671> LVL:2 RC: 0 AGENT :tera_agent_disconnect: {s_tag:0x9bd8fbc8ee73a36a} Server process already exited (hndl: 5, pid: 924, process handle: 0000060c)
11/17/2015, 14:02:36.671> LVL:2 RC: 0 AGENT :tera_agent_finish_disconnect_thread: connection_closed 6
11/17/2015, 14:02:36.703> LVL:2 RC: 0 AGENT :sSERVER_SESSION::~sSERVER_SESSION: {s_tag:0x9bd8fbc8ee73a36a} Closing pcoip server process handle 000000000000060C
Reviewing the View Connection server’s logs from the folder:
C:ProgramDataVMwareVDMlogs
… reveal the entry:
2015-11-17T14:17:10.024-04:00 DEBUG (0C70-094C) <e1f29aa5-68ed-437b-ad9f-cc1759d63d8b> [DesktopTracker] onEvent: PENDING_EXPIRED — UserName:a-tluk;DomainName:CONTOSO;UserDn:cn=s-1-5-21-206374890-975330658-925700815-10626,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int;UserSid:null;GroupSids:null;BrokerUserSid:S-1-5-21-206374890-975330658-925700815-10626;ConnectionId:fcca_***_1220;Protocol:null;ClientName:null;ClientAddress:null;ServerDn:cn=a34734d6-4e78-4d07-83c4-5ce3d1ce31cd,ou=servers,dc=vdi,dc=vmware,dc=int;ServerPoolDn:cn=standard_CON_desktop,ou=server groups,dc=vdi,dc=vmware,dc=int;ServerDnsName:CONFSTAWKST-158.tokiomillennium.com;DynamicIpAddress:10.23.0.92;ManagedObjectId:null;Id:e1f29aa5-68ed-437b-ad9f-cc1759d63d8b;State:PENDING_EXPIRED;SessionGuid:c80b-***-2d5b;PreviousSessionGuid:null;LoggedInAsDomain:CONTOSO;LoggedInAsUser:a-tluk;SessionType:DESKTOP;RemotableContent:null
Reviewing the Events database in the View Administrator console reveals the following:
The pending session on machine <VDIname> for user contosoa-tluk has expired.
What I’ve done in the past for troubleshooting black screen disconnection issues was to reinstall the VMware Horizon View agent but what I noticed was that attempting to install the View Agent on the master image after uninstalling it would briefly show the splash screen, disappear and nothing would happen. From there, I proceeded to uninstall VMware Tools and reinstall it but quickly noticed that the install would fail with the message:
VMware Product Installation
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
Attempting to copy the installer onto the desktop and run the install would generate the following error message:
Setup failed to extract the files necessary to install VMware Tools.
From here on, what ended up being the cause of all these issues was actually because there was no space in the %temp% directory to extract the installation files. The reason why this was the case was because the environment I was working in had SanDisk’s ioVDI solution deployed and the %temp% folder was redirected to a disposable disk that also stored the page file which had already filled up the disk. This was why the installer for VMware Tools and the Horizon View Agent would fail and it was also why the user had connection issues.
The whole ordeal concluded in a way that I did not expect so I hope the error messages I outlined here would be able to help anyone who happens to come across a similar issue with the same cause.
Recently I had to troubleshoot a VMware View Client connection problem. In a new VMware View environment the customer has installed a VMware Horizon View Security Server for the external connections. When a external View Client tried to connect through the Security Server using the PCoIP protocol to the View desktop the following appeared:
The connection to the remote computer ended
When the users connects to the View Desktop using the LAN (without the Security Server) everything worked fine. I suspected that a PCoIP port (4172 TCP and UDP) is blocked between the Security Server and desktop pool or vice versa.
To troubleshoot this problem I used the tool “Netcat”. With Netcat TCP and UDP ports can be checked (Telnet can only check TCP ports). So I used Netcat to check the TCP and UDP ports between the Security server and View Desktop (1) and the View Desktop to the Security Server(2).
Here is an example how to use Netcat:
On the View desktop run Netcat to listen to UDP port 4172:
nc –l –u –p 4172
On the security server run Netcat to connect to the View Desktop on UDP port 4172:
nc –u ipaddress 4172
You can type some text and press enter. The text typed in the screen must be displayed on both sides, If not the port is blocked.
So I discovered that the 4172 UDP protocol from the View desktop pool to the Security server was blocked by a firewall. After opening this port in the firewalls the problem was solved.
More information: Netcat for Windows can be downloaded here.
9. Создание пула Linked Clone.
Создадим пул машин с ОС Windows 7.
Идем в Inventory – щелкаем пулы и Add:
Выбираем автоматический:
Выбираем Dedicated (но галку автоназначения здесь не ставим – сами назначим пользователей – благо их всего 4):
Далее указываем, что будем использовать Linked Clones:
Обзываем пул:
А здесь уже жестко прописываем протокол PCoIP и 3D (память 256MB) и ставим галочку HTML Access:
Здесь указываем имя и число машин в пуле:
Здесь сколько GB на какие диски:
Не трогаем:
Тут указываем шаблон-снапшот-папка-хост итп:
Не трогаем:
Здесь лишь указываем наш OU HorizonPC:
И жмем финиш:
И далее назначим пользователей на машины.
Получим пул с двумя машинами Windows 7:
Также создадим пул с Windows 8:
10. Проверка работоспособности.
Запускаем View Client и логинимся-проверяем:
С iPhone:
Все работает.
Немного о подключении: пользователи могут подключаться к View Connection-серверу, используя SSL-подключение. В простейшем случае (наш) используется самоподписанный сертификат. В продуктивной среде необходимо использовать сертификаты, получаемые централизованно от сервера CA. Как это сделать, описано здесь: http://pubs.vmware.com/view-51/index.jsp?topic=%2Fcom.vmware.view.installation.doc%2FGUID-80CC770D-327E-4A21-B382-786621B23C44.html, здесь: http://derek858.blogspot.com/2012/05/vmware-view-51-installation-part-1-view.html и здесь в целом для vSphere: http://www.wooditwork.com/2011/11/30/vsphere-5-certificates-1-installing-a-root-certificate-authority-3/.
А теперь прикрутим HTML Access к нашим виртуальным десктопам.
11. Что нужно для HTML Access?
Для доступа к виртуальным десктопам с использованием HTML, необходимо установить VMware View Feature Pack. Состоит он из агента, устанавливаемого на шаблон десктопа, и серверной части, устанавливаемой на сервер VMware View Connection Server:
12. Установка агента VMware View Feature Pack.
Запускаем наш шаблон и включаем родной MS-брандмауэр (если был выключен).
Затем установка, снова ipconfig /release, выключение шаблона и снапшот:
Тоже самое проделываем со всеми шаблонами, нуждающимися в доступе с использованием HTML.
Затем пересобираем пул:
Выбираем новый снапшот:
Не меняем:
И ждем окончания процесса:
Далее установим серверную часть VMware View Feature Pack.
13. Установка серверной части VMware View Feature Pack.
Все просто до безобразия:
И теперь можно проверить новые фишки.
14. Проверка работоспособности HTML Access.
Идем по http-адресу нашего сервера view-mgr.horizon.local и попадаем на интересную страничку:
Выбираем HTML Access, вводим логин-пароль:
Выбираем наш пул:
И попадаем на машину (в которой работает даже тестовое видео!):
Также для 8ки:
БОНУС:
Наконец, в View 5.2 появилась функция Unity Touch, как это работает, показано здесь:
http://www.youtube.com/watch?v=eHZoUiDFeVE.
У меня же это работает так:
Конец 
| Code | Reason |
| 0 | No error |
| 1 | User-initiated client disconnect. |
| 2 | User-initiated client logoff. |
| 3 | Your Remote Desktop Services session has ended, possibly for one of the following reasons: The administrator has ended the session. An error occurred while the connection was being established. A network problem occurred. For help solving the problem, see «Remote Desktop» in Help and Support. |
| 260 | Remote Desktop can’t find the computer «». This might mean that «» does not belong to the specified network. Verify the computer name and domain that you are trying to connect to. |
| 262 | This computer can’t connect to the remote computer. Your computer does not have enough virtual memory available. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
| 264 | This computer can’t connect to the remote computer. The two computers couldn’t connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support. |
| 266 | The smart card service is not running. Please start the smart card service and try again. |
| 516 | Remote Desktop can’t connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. |
| 522 | A smart card reader was not detected. Please attach a smart card reader and try again. |
| 772 | This computer can’t connect to the remote computer. The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network administrator or technical support. |
| 778 | There is no card inserted in the smart card reader. Please insert your smart card and try again. |
| 1030 | Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again. |
| 1032 | The specified computer name contains invalid characters. Please verify the name and try again. |
| 1034 | An error has occurred in the smart card subsystem. Please contact your helpdesk about this error. |
| 1796 | 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. |
| 1800 | Your computer could not connect to another console session on the remote computer because you already have a console session in progress. |
| 2056 | The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator. |
| 2308 | Your Remote Desktop Services session has ended. The connection to the remote computer was lost, possibly due to network connectivity problems. Try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support. |
| 2311 | The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 2312 | A licensing error occurred while the client was attempting to connect (Licensing timed out). Please try connecting to the remote computer again. |
| 2567 | The specified username does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support. |
| 2820 | This computer can’t connect to the remote computer. An error occurred that prevented the connection. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 2822 | Because of an error in data encryption, this session will end. Please try connecting to the remote computer again. |
| 2823 | The user account is currently disabled and cannot be used. For assistance, contact your system administrator or technical support. |
| 2825 | The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support. |
| 3079 | A user account restriction (for example, a time-of-day restriction) is preventing you from logging on. For assistance, contact your system administrator or technical support. |
| 3080 | The remote session was disconnected because of a decompression failure at the client side. Please try connecting to the remote computer again. |
| 3335 | As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts. Wait a while before trying again, or contact your system administrator or technical support. |
| 3337 | The security policy of your computer requires you to type a password on the Windows Security dialog box. However, the remote computer you want to connect to cannot recognize credentials supplied using the Windows Security dialog box. For assistance, contact your system administrator or technical support. |
| 3590 | The client can’t connect because it doesn’t support FIPS encryption level. Please lower the server side required security level Policy, or contact your network administrator for assistance |
| 3591 | This user account has expired. For assistance, contact your system administrator or technical support. |
| 3592 | Failed to reconnect to your remote session. Please try to connect again. |
| 3593 | The remote PC doesn’t support Restricted Administration mode. |
| 3847 | This user account’s password has expired. The password must change in order to logon. Please update the password or contact your system administrator or technical support. |
| 3848 | A connection will not be made because credentials may not be sent to the remote computer. For assistance, contact your system administrator. |
| 4103 | The system administrator has restricted the times during which you may log in. Try logging in later. If the problem continues, contact your system administrator or technical support. |
| 4104 | The remote session was disconnected because your computer is running low on video resources. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
| 4359 | The system administrator has limited the computers you can log on with. Try logging on at a different computer. If the problem continues, contact your system administrator or technical support. |
| 4615 | You must change your password before logging on the first time. Please update your password or contact your system administrator or technical support. |
| 4871 | The system administrator has restricted the types of logon (network or interactive) that you may use. For assistance, contact your system administrator or technical support. |
| 5127 | The Kerberos sub-protocol User2User is required. For assistance, contact your system administrator or technical support. |
| 6919 | Remote Desktop cannot connect to the remote computer because the authentication certificate received from the remote computer is expired or invalid. In some cases, this error might also be caused by a large time discrepancy between the client and server computers. |
| 7431 | Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer. Make sure your computer’s clock is set to the correct time, and then try connecting again. If the problem occurs again, contact your network administrator or the owner of the remote computer. |
| 8711 | Your computer can’t connect to the remote computer because your smart card is locked out. Contact your network administrator about unlocking your smart card or resetting your PIN. |
| 9479 | Could not auto-reconnect to your applications,please re-launch your applications |
| 9732 | Client and server versions do not match. Please upgrade your client software and then try connecting again. |
| 33554433 | Failed to reconnect to the remote program. Please restart the remote program. |
| 33554434 | The remote computer does not support RemoteApp. For assistance, contact your system administrator. |
| 50331649 | Your computer can’t connect to the remote computer because the username or password is not valid. Type a valid user name and password. |
| 50331650 | Your computer can’t connect to the remote computer because it can’t verify the certificate revocation list. Contact your network administrator for assistance. |
| 50331651 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) The requested Remote Desktop Gateway server address and the server SSL certificate subject name do not match. 2) The certificate is expired or revoked. 3) The certificate root authority does not trust the certificate. Contact your network administrator for assistance. |
| 50331652 | Your computer can’t connect to the remote computer because the SSL certificate was revoked by the certification authority. Contact your network administrator for assistance. |
| 50331653 | This computer can’t verify the identity of the RD Gateway «». It’s not safe to connect to servers that can’t be identified. Contact your network administrator for assistance. |
| 50331654 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address requested and the certificate subject name do not match. Contact your network administrator for assistance. |
| 50331655 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server’s certificate has expired or has been revoked. Contact your network administrator for assistance. |
| 50331656 | Your computer can’t connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance. |
| 50331657 | An error occurred while sending data to the Remote Desktop Gateway server. The server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
| 50331658 | An error occurred while receiving data from the Remote Desktop Gateway server. Either the server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
| 50331659 | Your computer can’t connect to the remote computer because an alternate logon method is required. Contact your network administrator for assistance. |
| 50331660 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address. |
| 50331661 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
| 50331662 | Your computer can’t connect to the remote computer because the Remote Desktop Services client component is missing or is an incorrect version. Verify that setup was completed successfully, and then try reconnecting later. |
| 50331663 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is running low on server resources and is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
| 50331664 | Your computer can’t connect to the remote computer because an incorrect version of rpcrt4.dll has been detected. Verify that all components for Remote Desktop Gateway client were installed correctly. |
| 50331665 | Your computer can’t connect to the remote computer because no smart card service is installed. Install a smart card service and then try again, or contact your network administrator for assistance. |
| 50331666 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Try again using a valid smart card, or contact your network administrator for assistance. |
| 50331667 | Your computer can’t connect to the remote computer because no smart card is available. Try again using a smart card. |
| 50331668 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Reinsert the smart card and then try again. |
| 50331669 | Your computer can’t connect to the remote computer because the user name or password is not valid. Please type a valid user name and password. |
| 50331671 | Your computer can’t connect to the remote computer because a security package error occurred in the transport layer. Retry the connection or contact your network administrator for assistance. |
| 50331672 | The Remote Desktop Gateway server has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
| 50331673 | The Remote Desktop Gateway server administrator has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
| 50331674 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) Your credentials (the combination of user name, domain, and password) were incorrect. 2) Your smart card was not recognized. |
| 50331675 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not listed in the RD Gateway’s permission list 2) You might have specified the remote computer in NetBIOS format (for example, computer1), but the RD Gateway is expecting an FQDN or IP address format (for example, computer1.fabrikam.com or 157.60.0.1). Contact your network administrator for assistance. |
| 50331676 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not authorized to access the RD Gateway «» 2) Your computer is not authorized to access the RD Gateway «» 3) You are using an incompatible authentication method (for example, the RD Gateway might be expecting a smart card but you provided a password) Contact your network administrator for assistance. |
| 50331679 | Your computer can’t connect to the remote computer because your network administrator has restricted access to this RD Gateway server. Contact your network administrator for assistance. |
| 50331680 | Your computer can’t connect to the remote computer because the web proxy server requires authentication. To allow unauthenticated traffic to an RD Gateway server through your web proxy server, contact your network administrator. |
| 50331681 | Your computer can’t connect to the remote computer because your password has expired or you must change the password. Please change the password or contact your network administrator or technical support for assistance. |
| 50331682 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server reached its maximum allowed connections. Try reconnecting later or contact your network administrator for assistance. |
| 50331683 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server does not support the request. Contact your network administrator for assistance. |
| 50331684 | Your computer can’t connect to the remote computer because the client does not support one of the Remote Desktop Gateway’s capabilities. Contact your network administrator for assistance. |
| 50331685 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server and this computer are incompatible. Contact your network administrator for assistance. |
| 50331686 | Your computer can’t connect to the remote computer because the credentials used are not valid. Insert a valid smart card and type a PIN or password, and then try connecting again. |
| 50331687 | Your computer can’t connect to the remote computer because your computer or device did not pass the Network Access Protection requirements set by your network administrator. Contact your network administrator for assistance. |
| 50331688 | Your computer can’t connect to the remote computer because no certificate was configured to use at the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331689 | Your computer can’t connect to the remote computer because the RD Gateway server that you are trying to connect to is not allowed by your computer administrator. If you are the administrator, add this Remote Desktop Gateway server name to the trusted Remote Desktop Gateway server list on your computer and then try connecting again. |
| 50331690 | Your computer can’t connect to the remote computer because your computer or device did not meet the Network Access Protection requirements set by your network administrator, for one of the following reasons: 1) The Remote Desktop Gateway server name and the server’s public key certificate subject name do not match. 2) The certificate has expired or has been revoked. 3) The certificate root authority does not trust the certificate. 4) The certificate key extension does not support encryption. 5) Your computer cannot verify the certificate revocation list. Contact your network administrator for assistance. |
| 50331691 | Your computer can’t connect to the remote computer because a user name and password are required to authenticate to the Remote Desktop Gateway server instead of smart card credentials. |
| 50331692 | Your computer can’t connect to the remote computer because smart card credentials are required to authenticate to the Remote Desktop Gateway server instead of a user name and password. |
| 50331693 | Your computer can’t connect to the remote computer because no smart card reader is detected. Connect a smart card reader and then try again, or contact your network administrator for assistance. |
| 50331695 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to missing firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
| 50331696 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to invalid firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
| 50331698 | Your Remote Desktop Services session ended because the remote computer didn’t receive any input from you. |
| 50331699 | The connection has been disconnected because the session timeout limit was reached. |
| 50331700 | Your computer can’t connect to the remote computer because an invalid cookie was sent to the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331701 | Your computer can’t connect to the remote computer because the cookie was rejected by the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331703 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is expecting an authentication method different from the one attempted. Contact your network administrator for assistance. |
| 50331704 | The RD Gateway connection ended because periodic user authentication failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
| 50331705 | The RD Gateway connection ended because periodic user authorization failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
| 50331707 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway and the remote computer are unable to exchange policies. This could happen due to one of the following reasons: 1. The remote computer is not capable of exchanging policies with the Remote Desktop Gateway. 2. The remote computer’s configuration does not permit a new connection. 3. The connection between the Remote Desktop Gateway and the remote computer ended. Contact your network administrator for assistance. |
| 50331708 | Your computer can’t connect to the remote computer, possibly because the smart card is not valid, the smart card certificate was not found in the certificate store, or the Certificate Propagation service is not running. Contact your network administrator for assistance. |
| 50331709 | To use this program or computer, first log on to the following website: <a href=»»></a>. |
| 50331710 | To use this program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
| 50331711 | Your session has ended. To continue using the program or computer, first log on to the following website: <a href=»»></a>. |
| 50331712 | Your session has ended. To continue using the program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
| 50331713 | The RD Gateway connection ended because periodic user authorization failed. Your computer or device didn’t pass the Network Access Protection (NAP) requirements set by your network administrator. Contact your network administrator for assistance. |
| 50331714 | Your computer can’t connect to the remote computer because the size of the cookie exceeded the supported size. Contact your network administrator for assistance. |
| 50331716 | Your computer can’t connect to the remote computer using the specified forward proxy configuration. Contact your network administrator for assistance. |
| 50331717 | This computer cannot connect to the remote resource because you do not have permission to this resource. Contact your network administrator for assistance. |
| 50331718 | There are currently no resources available to connect to. Retry the connection or contact your network administrator. |
| 50331719 | An error occurred while Remote Desktop Connection was accessing this resource. Retry the connection or contact your system administrator. |
| 50331721 | Your Remote Desktop Client needs to be updated to the newest version. Contact your system administrator for help installing the update, and then try again. |
| 50331722 | Your network configuration doesn’t allow the necessary HTTPS ports. Contact your network administrator for help allowing those ports or disabling the web proxy, and then try connecting again. |
| 50331723 | We’re setting up more resources, and it might take a few minutes. Please try again later. |
| 50331724 | The user name you entered does not match the user name used to subscribe to your applications. If you wish to sign in as a different user please choose Sign Out from the Home menu. |
| 50331725 | Looks like there are too many users trying out the Azure RemoteApp service at the moment. Please wait a few minutes and then try again. |
| 50331726 | Maximum user limit has been reached. Please contact your administrator for further assistance. |
| 50331727 | Your trial period for Azure RemoteApp has expired. Ask your admin or tech support for help. |
| 50331728 | You no longer have access to Azure RemoteApp. Ask your admin or tech support for help. |
Table of Contents
- Summary
- More Information
- Script
- Example Event from Event Log
- Primary Disconnect Reasons
- Extended Disconnect Reasons
Summary
This article contains most of the current Remote Desktop Client disconnect codes and reasons. Please see parent article Remote Desktop Services RDS Logon Connectivity Overview for additional information.
More Information
The RDP client disconnect codes are written to the ‘Microsoft-Windows-TerminalServices-RDPClient/Operational’ event login ‘Applications and Services Logs/Microsoft/Windows’ in Event Viewer. Not all codes are enumerable from the COM method shown below. Additionally,
some of the disconnect codes returned are extended codes. If the disconnect code is not found in the Primary Disconnect Reasons table, see the Extended Disconnect Reasons table. When troubleshooting client-side connections, be aware that depending on a configuration
such as encryption and security level, the client may attempt connection multiple times and disconnect before the final connection is made.
Script
The following snippet is a PowerShell command to query COM MSTscAx with a decimal disconnect code ID. If the disconnect code is found the description will be returned.
NOTE: When running the command below, ‘An internal error has occurred.’. This is a generic return code description when the disconnect code in is not found and return description is not valid.
# powershell script to return description of rds client disconnect codes in decimal format (not hex)
Param(
[parameter(Position=0,Mandatory=$true,HelpMessage="Enter the disconnect reason code in decimal from client side rds trace")]
[string] $disconnectReason,
[string] $extendedReason = 0
)
$mstsc = New-Object -ComObject MSTscAx.MsTscAx
write-host «description: $($mstsc.GetErrorDescription($disconnectReason,$extendedReason))»
Example Event from Event Log
Below is an example event log entry event ID 1026 of an RDP client session disconnect event (event code 263 which is no error).
Log Name: Microsoft-Windows-TerminalServices-RDPClient/Operational
Source: Microsoft-Windows-TerminalServices-ClientActiveXCore
Date: 5/3/2017 7:40:58 AM
Event ID: 1026
Task Category: Connection Sequence
Level: Information
Keywords:
User: client-machine\jason
Computer: client-machine
Description:
RDP ClientActiveX has been disconnected (Reason= 263)
Event Xml:
<System>
<Provider
Name="Microsoft-Windows-TerminalServices-ClientActiveXCore"
Guid="{28AA95BB-D444-4719-A36F-40462168127E}"
/>
<EventID>1026</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>101</Task>
<Opcode>11</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated
SystemTime="2017-05-03T11:40:58.058887000Z"
/>
<EventRecordID>61070</EventRecordID>
<Correlation
ActivityID="{3371E543-77B1-41BA-8835-674829620000}"
/>
<Execution
ProcessID="14296"
ThreadID="15212"
/>
<Channel>Microsoft-Windows-TerminalServices-RDPClient/Operational</Channel>
<Computer>client-machine</Computer>
<Security
UserID=""
/>
</System>
<EventData>
<Data
Name="Name">Disconnect Reason</Data>
<Data
Name="Value">263</Data>
<Data
Name="CustomLevel">Info</Data>
</EventData>
</Event>
Primary Disconnect Reasons
| Code | Reason |
| 0 | No error |
| 1 | User-initiated client disconnect. |
| 2 | User-initiated client logoff. |
| 3 | Your Remote Desktop Services session has ended, possibly for one of the following reasons: The administrator has ended the session. An error occurred while the connection was being established. A network problem occurred. For help solving the problem, see «Remote Desktop» in Help and Support. |
| 260 | Remote Desktop can’t find the computer «». This might mean that «» does not belong to the specified network. Verify the computer name and domain that you are trying to connect to. |
| 262 | This computer can’t connect to the remote computer. Your computer does not have enough virtual memory available. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
| 264 | This computer can’t connect to the remote computer. The two computers couldn’t connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support. |
| 266 | The smart card service is not running. Please start the smart card service and try again. |
| 516 | Remote Desktop can’t connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network Make sure the remote computer is turned on and connected to the network, and that remote access is enabled. |
| 522 | A smart card reader was not detected. Please attach a smart card reader and try again. |
| 772 | This computer can’t connect to the remote computer. The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network administrator or technical support. |
| 778 | There is no card inserted in the smart card reader. Please insert your smart card and try again. |
| 1030 | Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again. |
| 1032 | The specified computer name contains invalid characters. Please verify the name and try again. |
| 1034 | An error has occurred in the smart card subsystem. Please contact your helpdesk about this error. |
| 1796 | 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. |
| 1800 | Your computer could not connect to another console session on the remote computer because you already have a console session in progress. |
| 2055 | This computer can’t connect to the remote computer. Check the user name, domain name and password and try again. |
| 2056 | The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator. |
| 2308 | Your Remote Desktop Services session has ended. The connection to the remote computer was lost, possibly due to network connectivity problems. Try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support. |
| 2311 | The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 2312 | A licensing error occurred while the client was attempting to connect (Licensing timed out). Please try connecting to the remote computer again. |
| 2567 | The specified username does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support. |
| 2820 | This computer can’t connect to the remote computer. An error occurred that prevented the connection. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator. |
| 2822 | Because of an error in data encryption, this session will end. Please try connecting to the remote computer again. |
| 2823 | The user account is currently disabled and cannot be used. For assistance, contact your system administrator or technical support. |
| 2825 | The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support. |
| 3079 | A user account restriction (for example, a time-of-day restriction) is preventing you from logging on. For assistance, contact your system administrator or technical support. |
| 3080 | The remote session was disconnected because of a decompression failure at the client side. Please try connecting to the remote computer again. |
| 3335 | As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts. Wait a while before trying again, or contact your system administrator or technical support. |
| 3337 | The security policy of your computer requires you to type a password on the Windows Security dialog box. However, the remote computer you want to connect to cannot recognize credentials supplied using the Windows Security dialog box. For assistance, contact your system administrator or technical support. |
| 3590 | The client can’t connect because it doesn’t support FIPS encryption level. Please lower the server side required security level Policy, or contact your network administrator for assistance |
| 3591 | This user account has expired. For assistance, contact your system administrator or technical support. |
| 3592 | Failed to reconnect to your remote session. Please try to connect again. |
| 3593 | The remote PC doesn’t support Restricted Administration mode. |
| 3847 | This user account’s password has expired. The password must change in order to logon. Please update the password or contact your system administrator or technical support. |
| 3848 | A connection will not be made because credentials may not be sent to the remote computer. For assistance, contact your system administrator. |
| 4103 | The system administrator has restricted the times during which you may log in. Try logging in later. If the problem continues, contact your system administrator or technical support. |
| 4104 | The remote session was disconnected because your computer is running low on video resources. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support. |
| 4359 | The system administrator has limited the computers you can log on with. Try logging on at a different computer. If the problem continues, contact your system administrator or technical support. |
| 4615 | You must change your password before logging on the first time. Please update your password or contact your system administrator or technical support. |
| 4871 | The system administrator has restricted the types of logon (network or interactive) that you may use. For assistance, contact your system administrator or technical support. |
| 5127 | The Kerberos sub-protocol User2User is required. For assistance, contact your system administrator or technical support. |
| 6919 | Remote Desktop cannot connect to the remote computer because the authentication certificate received from the remote computer is expired or invalid. In some cases, this error might also be caused by a large time discrepancy between the client and server computers. |
| 7431 | Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer. Make sure your computer’s clock is set to the correct time, and then try connecting again. If the problem occurs again, contact your network administrator or the owner of the remote computer. |
| 8711 | Your computer can’t connect to the remote computer because your smart card is locked out. Contact your network administrator about unlocking your smart card or resetting your PIN. |
| 9479 | Could not auto-reconnect to your applications,please re-launch your applications |
| 9732 | Client and server versions do not match. Please upgrade your client software and then try connecting again. |
| 33554433 | Failed to reconnect to the remote program. Please restart the remote program. |
| 33554434 | The remote computer does not support RemoteApp. For assistance, contact your system administrator. |
| 50331649 | Your computer can’t connect to the remote computer because the username or password is not valid. Type a valid user name and password. |
| 50331650 | Your computer can’t connect to the remote computer because it can’t verify the certificate revocation list. Contact your network administrator for assistance. |
| 50331651 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) The requested Remote Desktop Gateway server address and the server SSL certificate subject name do not match. 2) The certificate is expired or revoked. 3) The certificate root authority does not trust the certificate. Contact your network administrator for assistance. |
| 50331652 | Your computer can’t connect to the remote computer because the SSL certificate was revoked by the certification authority. Contact your network administrator for assistance. |
| 50331653 | This computer can’t verify the identity of the RD Gateway «». It’s not safe to connect to servers that can’t be identified. Contact your network administrator for assistance. |
| 50331654 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address requested and the certificate subject name do not match. Contact your network administrator for assistance. |
| 50331655 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server’s certificate has expired or has been revoked. Contact your network administrator for assistance. |
| 50331656 | Your computer can’t connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance. |
| 50331657 | An error occurred while sending data to the Remote Desktop Gateway server. The server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
| 50331658 | An error occurred while receiving data from the Remote Desktop Gateway server. Either the server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance. |
| 50331659 | Your computer can’t connect to the remote computer because an alternate logon method is required. Contact your network administrator for assistance. |
| 50331660 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address. |
| 50331661 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
| 50331662 | Your computer can’t connect to the remote computer because the Remote Desktop Services client component is missing or is an incorrect version. Verify that setup was completed successfully, and then try reconnecting later. |
| 50331663 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is running low on server resources and is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance. |
| 50331664 | Your computer can’t connect to the remote computer because an incorrect version of rpcrt4.dll has been detected. Verify that all components for Remote Desktop Gateway client were installed correctly. |
| 50331665 | Your computer can’t connect to the remote computer because no smart card service is installed. Install a smart card service and then try again, or contact your network administrator for assistance. |
| 50331666 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Try again using a valid smart card, or contact your network administrator for assistance. |
| 50331667 | Your computer can’t connect to the remote computer because no smart card is available. Try again using a smart card. |
| 50331668 | Your computer can’t stay connected to the remote computer because the smart card has been removed. Reinsert the smart card and then try again. |
| 50331669 | Your computer can’t connect to the remote computer because the user name or password is not valid. Please type a valid user name and password. |
| 50331671 | Your computer can’t connect to the remote computer because a security package error occurred in the transport layer. Retry the connection or contact your network administrator for assistance. |
| 50331672 | The Remote Desktop Gateway server has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
| 50331673 | The Remote Desktop Gateway server administrator has ended the connection. Try reconnecting later or contact your network administrator for assistance. |
| 50331674 | Your computer can’t connect to the remote computer due to one of the following reasons: 1) Your credentials (the combination of user name, domain, and password) were incorrect. 2) Your smart card was not recognized. |
| 50331675 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not listed in the RD Gateway’s permission list 2) You might have specified the remote computer in NetBIOS format (for example, computer1), but the RD Gateway is expecting an FQDN or IP address format (for example, computer1.fabrikam.com or 157.60.0.1). Contact your network administrator for assistance. |
| 50331676 | Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not authorized to access the RD Gateway «» 2) Your computer is not authorized to access the RD Gateway «» 3) You are using an incompatible authentication method (for example, the RD Gateway might be expecting a smart card but you provided a password) Contact your network administrator for assistance. |
| 50331679 | Your computer can’t connect to the remote computer because your network administrator has restricted access to this RD Gateway server. Contact your network administrator for assistance. |
| 50331680 | Your computer can’t connect to the remote computer because the web proxy server requires authentication. To allow unauthenticated traffic to an RD Gateway server through your web proxy server, contact your network administrator. |
| 50331681 | Your computer can’t connect to the remote computer because your password has expired or you must change the password. Please change the password or contact your network administrator or technical support for assistance. |
| 50331682 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server reached its maximum allowed connections. Try reconnecting later or contact your network administrator for assistance. |
| 50331683 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server does not support the request. Contact your network administrator for assistance. |
| 50331684 | Your computer can’t connect to the remote computer because the client does not support one of the Remote Desktop Gateway’s capabilities. Contact your network administrator for assistance. |
| 50331685 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server and this computer are incompatible. Contact your network administrator for assistance. |
| 50331686 | Your computer can’t connect to the remote computer because the credentials used are not valid. Insert a valid smart card and type a PIN or password, and then try connecting again. |
| 50331687 | Your computer can’t connect to the remote computer because your computer or device did not pass the Network Access Protection requirements set by your network administrator. Contact your network administrator for assistance. |
| 50331688 | Your computer can’t connect to the remote computer because no certificate was configured to use at the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331689 | Your computer can’t connect to the remote computer because the RD Gateway server that you are trying to connect to is not allowed by your computer administrator. If you are the administrator, add this Remote Desktop Gateway server name to the trusted Remote Desktop Gateway server list on your computer and then try connecting again. |
| 50331690 | Your computer can’t connect to the remote computer because your computer or device did not meet the Network Access Protection requirements set by your network administrator, for one of the following reasons: 1) The Remote Desktop Gateway server name and the server’s public key certificate subject name do not match. 2) The certificate has expired or has been revoked. 3) The certificate root authority does not trust the certificate. 4) The certificate key extension does not support encryption. 5) Your computer cannot verify the certificate revocation list. Contact your network administrator for assistance. |
| 50331691 | Your computer can’t connect to the remote computer because a user name and password are required to authenticate to the Remote Desktop Gateway server instead of smart card credentials. |
| 50331692 | Your computer can’t connect to the remote computer because smart card credentials are required to authenticate to the Remote Desktop Gateway server instead of a user name and password. |
| 50331693 | Your computer can’t connect to the remote computer because no smart card reader is detected. Connect a smart card reader and then try again, or contact your network administrator for assistance. |
| 50331695 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to missing firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
| 50331696 | Your computer can’t connect to the remote computer because authentication to the firewall failed due to invalid firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance. |
| 50331698 | Your Remote Desktop Services session ended because the remote computer didn’t receive any input from you. |
| 50331699 | The connection has been disconnected because the session timeout limit was reached. |
| 50331700 | Your computer can’t connect to the remote computer because an invalid cookie was sent to the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331701 | Your computer can’t connect to the remote computer because the cookie was rejected by the Remote Desktop Gateway server. Contact your network administrator for assistance. |
| 50331703 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is expecting an authentication method different from the one attempted. Contact your network administrator for assistance. |
| 50331704 | The RD Gateway connection ended because periodic user authentication failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
| 50331705 | The RD Gateway connection ended because periodic user authorization failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance. |
| 50331707 | Your computer can’t connect to the remote computer because the Remote Desktop Gateway and the remote computer are unable to exchange policies. This could happen due to one of the following reasons: 1. The remote computer is not capable of exchanging policies with the Remote Desktop Gateway. 2. The remote computer’s configuration does not permit a new connection. 3. The connection between the Remote Desktop Gateway and the remote computer ended. Contact your network administrator for assistance. |
| 50331708 | Your computer can’t connect to the remote computer, possibly because the smart card is not valid, the smart card certificate was not found in the certificate store, or the Certificate Propagation service is not running. Contact your network administrator for assistance. |
| 50331709 | To use this program or computer, first log on to the following website: <a href=»»></a>. |
| 50331710 | To use this program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
| 50331711 | Your session has ended. To continue using the program or computer, first log on to the following website: <a href=»»></a>. |
| 50331712 | Your session has ended. To continue using the program or computer, you must first log on to an authentication website. Contact your network administrator for assistance. |
| 50331713 | The RD Gateway connection ended because periodic user authorization failed. Your computer or device didn’t pass the Network Access Protection (NAP) requirements set by your network administrator. Contact your network administrator for assistance. |
| 50331714 | Your computer can’t connect to the remote computer because the size of the cookie exceeded the supported size. Contact your network administrator for assistance. |
| 50331716 | Your computer can’t connect to the remote computer using the specified forward proxy configuration. Contact your network administrator for assistance. |
| 50331717 | This computer cannot connect to the remote resource because you do not have permission to this resource. Contact your network administrator for assistance. |
| 50331718 | There are currently no resources available to connect to. Retry the connection or contact your network administrator. |
| 50331719 | An error occurred while Remote Desktop Connection was accessing this resource. Retry the connection or contact your system administrator. |
| 50331721 | Your Remote Desktop Client needs to be updated to the newest version. Contact your system administrator for help installing the update, and then try again. |
| 50331722 | Your network configuration doesn’t allow the necessary HTTPS ports. Contact your network administrator for help allowing those ports or disabling the web proxy, and then try connecting again. |
| 50331723 | We’re setting up more resources, and it might take a few minutes. Please try again later. |
| 50331724 | The user name you entered does not match the user name used to subscribe to your applications. If you wish to sign in as a different user please choose Sign Out from the Home menu. |
| 50331725 | Looks like there are too many users trying out the Azure RemoteApp service at the moment. Please wait a few minutes and then try again. |
| 50331726 | Maximum user limit has been reached. Please contact your administrator for further assistance. |
| 50331727 | Your trial period for Azure RemoteApp has expired. Ask your admin or tech support for help. |
| 50331728 | You no longer have access to Azure RemoteApp. Ask your admin or tech support for help. |
Extended Disconnect Reasons
| Code | Reason |
| 0 | No error. |
| 1 | Extended Reason: Your Remote Desktop Services session has ended. Your network administrator might have ended the connection. Try connecting again, or contact technical support for assistance. |
| 2 | Extended Reason: Your Remote Desktop Services session has ended. You have logged off the remote computer. Your network administrator or another user might have ended your session. Try connecting again, or contact technical support for assistance. |
| 3 | Extended Reason: Your Remote Desktop Services session ended because the remote computer didn’t receive any input from you. |
| 4 | Extended Reason: The remote session ended because the total login time limit was reached. This limit is set by the server administrator or by network policies. |
| 5 | Extended Reason: Your Remote Desktop Services session has ended. Another user connected to the remote computer, so your connection was lost. Try connecting again, or contact your network administrator or technical support group. |
| 6 | Extended Reason: The connection was disconnected because the remote computer is low on memory. |
| 7 | Extended Reason: 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. |
| 8 | Extended Reason: The client could not establish a connection to the remote computer. The most likely causes for this error are: 1) Remote connections might not be enabled at the remote computer. 2) The maximum number of connections was exceeded at the remote computer. 3) A network error occurred while establishing a connection. 4) The remote computer might not support the required FIPS security level. Please lower the client side required security level Policy, or contact your network administrator for assistance. |
| 9 | Extended Reason: The connection was denied because the user account is not authorized for remote login. |
| 256 | Extended Reason: The remote session was disconnected because there was an internal error in the remote computer’s licensing protocol. |
| 257 | Extended Reason: The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator. |
| 258 | Extended Reason: The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer. Please contact the server administrator. |
| 259 | Extended Reason: The remote session was disconnected because the remote computer received an invalid licensing message from this computer. |
| 260 | Extended Reason: The remote session was disconnected because the Remote Desktop client access license stored on this computer has been modified. |
| 261 | Extended Reason: The remote session was disconnected because the Remote Desktop client access license stored on this computer is in an invalid format. |
| 262 | Extended Reason: The remote session was disconnected because there were network problems during the licensing protocol. Please try connecting to the remote computer again. |
| 263 | Extended Reason: The remote session was disconnected because the client prematurely ended the licensing protocol. |
| 264 | Extended Reason: The remote session was disconnected because a licensing message was incorrectly encrypted. |
| 265 | Extended Reason: The remote session was disconnected because the local computer’s client access license could not be upgraded or renewed. Please contact the server administrator. |
| 266 | Extended Reason: The remote session was disconnected because the remote computer is not licensed to accept remote connections. Please contact the server administrator. |
| 267 | Extended Reason: The remote session was disconnected because license store creation failed with access denied. Please run the remote desktop client with elevated privileges. |
| 1024 | Extended Reason: Remote Desktop Connection could not find the destination computer. This can happen if the computer name is incorrect or the computer is not yet registered with RD Connection Broker. Try connecting again, or contact your network administrator. |
| 1026 | Extended Reason: An error occurred while Remote Desktop Connection was loading the destination computer. Try connecting again, or contact your network administrator. |
| 1028 | Extended Reason: An error occurred while Remote Desktop Connection was redirecting to the destination computer. Try connecting again, or contact your network administrator. |
| 1029 | Extended Reason: Couldn’t connect to the remote computer (there was a problem setting up the virtual machine). Try connecting again, or contact your network administrator for help. |
| 1030 | Extended Reason: An error occurred while Remote Desktop Connection was starting the virtual machine. Try connecting again, or contact your network administrator. |
| 1031 | Extended Reason: Windows can’t find the IP address of the destination virtual machine. This can happen if the virtual machine doesn’t have Hyper-V enlightenments and the name of the virtual machine doesn’t match the computer name in Windows. Contact your network administrator for assistance. |
| 1032 | Extended Reason: There are no available computers in the pool. Try connecting again, or contact your network administrator. |
| 1033 | Extended Reason: Connection processing has been canceled. Try connecting again, or contact your network administrator. |
| 1040 | Extended Reason: Your computer can’t connect to the remote computer because the Connection Broker couldn’t validate the settings specified in your RDP file. Contact your network administrator for assistance. |
| 1041 | Extended Reason: A timeout error occurred while Remote Desktop Connection was starting the virtual machine. Try connecting again, or contact your network administrator. |
| 1042 | Extended Reason: A session monitoring error occurred while Remote Desktop Connection was starting the virtual machine. Try connecting again, or contact your network administrator. |
| 4339 | Extended Reason: The remote computer does not support RemoteApp. For assistance, contact your system administrator. |
| 4498 | Extended Reason: The remote session was disconnected because of a decryption error at the server. Please try connecting to the remote computer again. |