Ошибка 0x3000066 rdp

Hello, I recently configured a temporary RemoteApp solution to allow telework users to access their desktops.

On users with Windows machines, the only issue we ran into was certain versions requiring the following registry change:

reg.exe Add «HKCU\Software\Microsoft\Terminal Server Client» /V «RDGClientTransport» /T REG_DWORD /D «1»

I know this isn’t best practice as it forces RPC over HTTP, but as this is a temporary solution we are ok with it.

However, users with a Mac downloaded Remote Desktop Connection 10 from the app store, and they receive the message stated in the title.  It’s similar to the Windows 10 issue, but I don’t know how to fix it, as obviously the reg fix won’t work.

I’ve also read that if I had the RDC 8.0.44 legacy version I may not encounter this error.  So my question is two-fold:

1. Does anyone know how to get RDC 10 to use RPC over HTTP?

2. If not, does anyone know where I can get RDC 8.0.44 (I’ve search websites and even torrent sites, but no luck)

Thank you in advance!

Hello, I recently configured a temporary RemoteApp solution to allow telework users to access their desktops.

On users with Windows machines, the only issue we ran into was certain versions requiring the following registry change:

reg.exe Add «HKCUSoftwareMicrosoftTerminal Server Client» /V «RDGClientTransport» /T REG_DWORD /D «1»

I know this isn’t best practice as it forces RPC over HTTP, but as this is a temporary solution we are ok with it.

However, users with a Mac downloaded Remote Desktop Connection 10 from the app store, and they receive the message stated in the title.  It’s similar to the Windows 10 issue, but I don’t know how to fix it, as obviously the reg fix won’t work.

I’ve also read that if I had the RDC 8.0.44 legacy version I may not encounter this error.  So my question is two-fold:

1. Does anyone know how to get RDC 10 to use RPC over HTTP?

2. If not, does anyone know where I can get RDC 8.0.44 (I’ve search websites and even torrent sites, but no luck)

Thank you in advance!

Главная » Грабли » Маленькая, но злая ошибка с публикацией RD Gateway

При публикации RD Gateway с помощью IIS ARR можно столкнуться с одной маленькой, но очень досадной ошибкой. При попытке запустить опубликованный remoteapp на смартфоне (проявляется и на Windows Phone, и на Android, и на iOS) или, например, на Mac OS X, пользователь получит ошибку 0x03000008 и предложением обратиться к администратору 🙂

Причины могут быть разными, например:

• https://blog.thesysadmins.co.uk/remote-desktop-ios-8-1-0-error-0x03000008.html — настройки политики для NPS;
• https://social.technet.microsoft.com/Forums/office/en-US/02177dba-e8ff-4043-a287-1c6327370b7f/ipad-remote-problem-error-code-0x03000008?forum=winRDc — ошибки клиента.

Однако есть еще одна небольшая тонкость. Если RD Gateway опубликован через IIS ARR, то в правиле публикации необходимо указать тип сопоставления шаблона как «Regular expression», а не «Wildcard» для случая, когда правило задается с шаблоном «.*» и фильтрацией по значению HTTP_HOST. В противном случае можно получить ту самую ошибку 0x03000008.

Если рассмотреть внимательно трассировку («Failed Request Tracing») для публикации с wildcard, можно заметить, что некоторые запросы на rpcproxy не подпадают под шаблон правила и локальный IIS пытается обрабатывать их самостоятельно, естественно выдавая в ответ 404.

Пример такой ситуации:

После перевода правила на использование регулярных вырожений публикация начинает работать корректно.

Пример рабочего правила:

P.S. Естественно, самое главное не забывать, что для регулярных выражений шаблон, отвечающий любому числу любых символов не «*», а «.*» (точка — любой символ, * — любое количество).

Code error : 0x3000066 on MacBook and iPad

remote-desktop-servicesremote-desktop-client

Comment

KarlieWeng-MSFT answered • Nov 23, ’20

Comment

Unable to connect to remote desktop on mac Error code: 0x3000066

I saw there’s a new update for MS Remote Desktop to supposedly fix this issue but I still could not connect. Can someone from MS get this resolve asap please?

remote-desktop-client

Comment

MariaRobison-7145 answered • Apr 16, ’21 | KarlieWeng-MSFT commented • Apr 27, ’21

I found my answer here: https://docs.microsoft.com/answers/answers/169154/view.html
It’s working for me now. YAY!!!

Comment

JanTurowski-3722 answered • Dec 24, ’21

Is there a bottom line fix to resolve this with a new version or? We cannot be using the beta app forever.

Comment

2 Replies

What’s new in the macOS client

We regularly update the Remote Desktop client for macOS, adding new features and fixing issues. Here’s where you’ll find the latest updates.

If you encounter any issues, you can always contact us by navigating to Help > Report an issue.

Updates for version 10.7.5 (1969)

Date published: January 25, 2022

In this release, we’ve addressed an issue that caused display configuration to not work properly when using the client on 2021 MacBook Pro 14″ and 16″ devices with multiple monitors. This issue mainly affected devices with external monitors positioned above the MacBook display. We also addressed an issue that caused the client to crash when used on earlier versions of macOS 12, and fixed customer-reported smart card and folder redirection issues.

How to fix Unable to Connect – Error Code 0x3000064 (RDP from macOS)

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.

Microsoft RDP client for Mac receiving «Unable to connect» error code 0x5000007 from Microsoft RD Gateway

Posted on Apr 2, 2020 5:10 PM

Hello, I recently configured a temporary RemoteApp solution to allow telework users to access their desktops.

On users with Windows machines, the only issue we ran into was certain versions requiring the following registry change:

reg.exe Add «HKCUSoftwareMicrosoftTerminal Server Client» /V «RDGClientTransport» /T REG_DWORD /D «1»

I know this isn’t best practice as it forces RPC over HTTP, but as this is a temporary solution we are ok with it.

However, users with a Mac downloaded Remote Desktop Connection 10 from the app store, and they receive the message stated in the title.  It’s similar to the Windows 10 issue, but I don’t know how to fix it, as obviously the reg fix won’t work.

I’ve also read that if I had the RDC 8.0.44 legacy version I may not encounter this error.  So my question is two-fold:

1. Does anyone know how to get RDC 10 to use RPC over HTTP?

2. If not, does anyone know where I can get RDC 8.0.44 (I’ve search websites and even torrent sites, but no luck)

Thank you in advance!

Главная » Грабли » Маленькая, но злая ошибка с публикацией RD Gateway

При публикации RD Gateway с помощью IIS ARR можно столкнуться с одной маленькой, но очень досадной ошибкой. При попытке запустить опубликованный remoteapp на смартфоне (проявляется и на Windows Phone, и на Android, и на iOS) или, например, на Mac OS X, пользователь получит ошибку 0x03000008 и предложением обратиться к администратору 🙂

Причины могут быть разными, например:

• https://blog.thesysadmins.co.uk/remote-desktop-ios-8-1-0-error-0x03000008.html — настройки политики для NPS;
• https://social.technet.microsoft.com/Forums/office/en-US/02177dba-e8ff-4043-a287-1c6327370b7f/ipad-remote-problem-error-code-0x03000008?forum=winRDc — ошибки клиента.

Однако есть еще одна небольшая тонкость. Если RD Gateway опубликован через IIS ARR, то в правиле публикации необходимо указать тип сопоставления шаблона как «Regular expression», а не «Wildcard» для случая, когда правило задается с шаблоном «.*» и фильтрацией по значению HTTP_HOST. В противном случае можно получить ту самую ошибку 0x03000008.

Если рассмотреть внимательно трассировку («Failed Request Tracing») для публикации с wildcard, можно заметить, что некоторые запросы на rpcproxy не подпадают под шаблон правила и локальный IIS пытается обрабатывать их самостоятельно, естественно выдавая в ответ 404.

Пример такой ситуации:

После перевода правила на использование регулярных вырожений публикация начинает работать корректно.

Пример рабочего правила:

P.S. Естественно, самое главное не забывать, что для регулярных выражений шаблон, отвечающий любому числу любых символов не «*», а «.*» (точка — любой символ, * — любое количество).

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.

«Microsoft Error Code 30066» Введение

Как правило, специалисты по ПК называют «Microsoft Error Code 30066» как тип «ошибки времени выполнения». Разработчики программного обеспечения, такие как SoftwareDeveloper, обычно работают через несколько этапов отладки, чтобы предотвратить и исправить ошибки, обнаруженные в конечном продукте до выпуска программного обеспечения для общественности. К сожалению, такие проблемы, как ошибка 30066, могут не быть исправлены на этом заключительном этапе.

Ошибка 30066, рассматриваемая как «Microsoft Error Code 30066», может возникнуть пользователями Microsoft в результате нормального использования программы. Таким образом, конечные пользователи предупреждают поставщиков о наличии ошибок 30066 проблем, предоставляя информацию разработчику. Затем Microsoft Corporation исправляет эти дефектные записи кода и сделает обновление доступным для загрузки. В результате разработчик может использовать пакеты обновлений для Microsoft, доступные с их веб-сайта (или автоматическую загрузку), чтобы устранить эти ошибки 30066 проблемы и другие ошибки.

В чем причина ошибки 30066?

У вас будет сбой во время выполнения Microsoft, если вы столкнетесь с «Microsoft Error Code 30066» во время выполнения. Мы можем определить происхождение ошибок ошибки 30066 во время выполнения следующим образом:

Ошибка 30066 Crash — Ошибка 30066 остановит компьютер от выполнения обычной программной операции. Когда Microsoft не может обеспечить достаточный вывод для данного ввода или действительно не знает, что выводить, он часто путает систему таким образом.

Утечка памяти «Microsoft Error Code 30066» — этот тип утечки памяти приводит к тому, что Microsoft продолжает использовать растущие объемы памяти, снижая общую производительность системы. Потенциальные триггеры могут быть «бесконечным циклом», или когда программа выполняет «цикл» или повторение снова и снова.

Ошибка 30066 Logic Error — «логическая ошибка», как говорят, генерируется, когда программное обеспечение получает правильный ввод, но генерирует неверный вывод. Это происходит, когда исходный код Microsoft Corporation вызывает уязвимость при обработке информации.

Microsoft Error Code 30066 проблемы часто являются результатом отсутствия, удаления или случайного перемещения файла из исходного места установки Microsoft. Обычно, установка новой версии файла Microsoft Corporation позволяет устранить проблему, из-за которой возникает ошибка. Помимо прочего, в качестве общей меры по профилактике и очистке мы рекомендуем использовать очиститель реестра для очистки любых недопустимых записей файлов, расширений файлов Microsoft Corporation или разделов реестра, что позволит предотвратить появление связанных с ними сообщений об ошибках.

Распространенные проблемы Microsoft Error Code 30066

Усложнения Microsoft с Microsoft Error Code 30066 состоят из:

• «Ошибка Microsoft Error Code 30066. «
• «Microsoft Error Code 30066 не является приложением Win32.»
• «Microsoft Error Code 30066 должен быть закрыт. «
• «К сожалению, мы не можем найти Microsoft Error Code 30066. «
• «Microsoft Error Code 30066 не найден.»
• «Проблема при запуске приложения: Microsoft Error Code 30066. «
• «Microsoft Error Code 30066 не выполняется. «
• «Microsoft Error Code 30066 выйти. «
• «Ошибка в пути к программному обеспечению: Microsoft Error Code 30066. «

Эти сообщения об ошибках Microsoft Corporation могут появляться во время установки программы, в то время как программа, связанная с Microsoft Error Code 30066 (например, Microsoft) работает, во время запуска или завершения работы Windows, или даже во время установки операционной системы Windows. Важно отметить, когда возникают проблемы Microsoft Error Code 30066, так как это помогает устранять проблемы Microsoft (и сообщать в Microsoft Corporation).

Microsoft Error Code 30066 Истоки проблем

Большинство проблем Microsoft Error Code 30066 связаны с отсутствующим или поврежденным Microsoft Error Code 30066, вирусной инфекцией или недействительными записями реестра Windows, связанными с Microsoft.

В основном, осложнения Microsoft Error Code 30066 связаны с:

• Поврежденные ключи реестра Windows, связанные с Microsoft Error Code 30066 / Microsoft.
• Вредоносные программы заразили Microsoft Error Code 30066, создавая повреждение.
• Другая программа злонамеренно или по ошибке удалила файлы, связанные с Microsoft Error Code 30066.
• Другая программа находится в конфликте с Microsoft и его общими файлами ссылок.
• Поврежденная загрузка или неполная установка программного обеспечения Microsoft.

Продукт Solvusoft

Загрузка
WinThruster 2022 — Проверьте свой компьютер на наличие ошибок.

Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11

Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление

Mac rdp error 0x300005c

Вопрос

I’ve been using Microsoft Remote Desktop to work from home for the past few weeks.

Last night I updated my macOS to Catalina and now I can’t access Microsoft Remote Desktop.

Can someone help? Error message: Error code: 0x300005c

• Перемещено Herb Gu Microsoft contingent staff 27 апреля 2020 г. 7:17

Все ответы

Since this forum focuses more on questions related to Office desktop applications, if you need further assistance on this problem, I’d like to help you move the thread to the following forum: Remote Desktop clients. You may get more helpful replies there.

The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thanks for your kind understanding.

Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Office 2019.

Источник

Mac rdp error 0x300005c

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

Cannot connect from Macbook to Mac Pro using Microsoft Remote Desktop for Mac. Steps taken

1. Add PC
2. Enter local IP address as name of PC to remote into. User acct: «ask if required»
3. Add local IP address to gateway section
4. Save

Refer to pic: https://imgur.com/USgHVym

Systems, software, settings
Macbook Pro MacOS 10.15.4 Catalina
Macbook MacOS 10.14.4 Mojave
Microsoft Remote Desktop: Version 10.3.10 (1783)

We couldn’t connect to the remote PC because the Remote Desktop Gateway is temporarily unavailable. Try connecting later or contact your network administrator for assistance.

Error code: 0x300005e

>> Enter local IP address as name of PC to remote into. User acct: «ask if required»

Is this IP address for Mac pro(target PC)? Please also check if you have made the setting to enable Mac pro to accept remote desktop.

>> Add local IP address to gateway section

Is this IP address for Gateway server? If not, you should contact your IT to check the details for Gateway used.

Note: This configuration will allow you to connect through a Remote Desktop Gateway ( used to allow secure connections using HTTPS from computers outside your corporate network ).

Please check with your IT administrator if port 443 is on listening or occupied by other service.

Источник

Mac rdp error 0x300005c

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

I am getting below error when I am trying to run a .rdp file

An error occurred while communicating with the Remote Desktop Gateway. If this keeps happening, contact your network administrator for assistance.

Error code: 0x3000066

I have a local deployment and a cloud based deployment of RDGateway.

I have a Windows Server 2012 R2 with Remote Desktop Gateway role installed with a pluggable authentication module (Cookie based) for gateway authentication.

On my local setup, I am able to test the pluggable authentication module on all OS ( Windows and Mac). The Windows machine uses the default MSTSC client to invoke/run the .rdp file, and on Mac I am able to test it using both

Microsoft Remote Desktop Client 8.x and 10.x

So, Locally everything works fine.

No When I have deployed my Gateway on Cloud(Azure):

The same setup works on windows and Mac with Microsoft Remote Desktop 8.x client but gives above error when the .rdp file is launched using Microsoft Remote Desktop 10.x

I don’t think this is certificate or any networking issue as the .rdp file can be launched successfully from the Microsoft Remote Desktop 8.x

Источник

question

Remote desktop from a Mac or iOS gives error 0x3000008

I have a load balancer (HAProxy) in front of two Remote Desktop Gateways (2012R2). When connecting from a Mac or an iOS device I receive an error 0x3000008 on the client side and in the event logs on the gateway server I see:

The user «user@domain.com», on client computer «X.X.X.X:36008», has initiated an outbound connection. This connection may not be authenticated yet.

I’ve disabled enforcebindings in the registry.

Works fine from a Windows client.

1 Answer

The answer mentioned «The problem comes from the fact that the RDP client (MAC, iOS, Android. etc) uses absolute URI in the SSL tunnel. WAP server supports only relative URI. Absolute URI support has been added to Azure AD Application Proxy recently. If it’s possible it is recommended you should use Azure AD Application Proxy. The Product Group team has been informed about this and is working on finding a work-around. But at the moment we don’t have plans on fixing the issue in WAP (2016).»

Have you tried to skip the HAProxy and directly connect to the RD Gateways ? Does the issue persist?

If the Answer is helpful, please click «Accept Answer» and upvote it.

Going directly to the RDPGateway works fine.

HAProxy is not making any changes to the URI, so it must be something else. The RDP client should work the same on Windows as Mac. It would be nice to get some client side logging to troubleshoot.

It seems there is some misunderstanding. It doesn’t mean HAProxy is making some changes to the URI. But maybe the HAProxy supports only relative URI while the RDP client for MAC or iOS uses absolute URI. That’s the problem.

Источник

Microsoft RDP — MAC High Sierra Errors

I have a client that connects to our MS VDI environment via a MAC using RDP. Her RDP client V8 shows a black screen that says negotiating connection. I updated to the new RDP V10 the message changes to 0x204. After upgrading to High Seirra 10.13.4 it worked for 2 days. Now I am getting the same error again. When the client connects I can see them coming in to my corporate network but they never get connected. I believe the issue is on the MAC side which may be blocking the incoming connection. I have made sure the MAC has RDP allowed via the firewall. I have also tried with the firewall off and no AV software.

Anyone have a solution?

Enter to win a $250 Amazon Gift Card

Generally reinstalling an application in OS X is almost never necessary nor does it produce any meaningful result.

If the binaries of a formerly functional (OS X) application bundle have suddenly gone corrupt, then the underlying filesystem and/or drive housing it are probably about to die, hard.

Quit RDP on the Mac, hold the option key & click on the Go menu to enable showing the Library & select that.

Within that user’s Library (NOT the top-level Library folder),

navigate into Containers and set aside com.microsoft.rdc.macos and com.microsoft.rdc.mac (one of those is for v8, just pull them both aside).

go back to the User’s Library and open the Group Containers folder.

Set aside the folder

In the Terminal (logged in as the user in question) issue the following, which will reset (kill and it will then auto-relaunch) the preference caching daemon, as prefs are AGGRESSIVELY cached in current versions of OS X.

Then test. Best of luck & let us know how it goes.

Источник