Windows 10: Remote connection to Windows EC2 through RDP App — Error Code : 0x50331670
Discus and support Remote connection to Windows EC2 through RDP App — Error Code : 0x50331670 in Windows 10 Network and Sharing to solve the problem; I am trying to connect to remote EC2 instance from a Windows VDI. I am getting a Error code : 0x50331670. What is the issue ?…
Discussion in ‘Windows 10 Network and Sharing’ started by GaneshamoorthyC, Sep 9, 2021.
-
Remote connection to Windows EC2 through RDP App — Error Code : 0x50331670
I am trying to connect to remote EC2 instance from a Windows VDI. I am getting a Error code : 0x50331670. What is the issue ?
-
RDP not allowing remote connection
I had it working perfectly fine the other day but I logged into my server, removed a open port and both computer quit.
I run the computers with the firewall off, I see no point in them being on, it’s a windows firewall a hacker will know how to get around so fire wall is OFF.
Ports are 9000 for server and 3390 for htpc
ip:9000
ip:3390This does not work from a linux workstation using ‘Remote Desktop Client’
It does not work from mac RDP
It does not work from windows RDP
And it does not work from my iphone.I know it’s enabled as I can RDP into the computers at my home (except htpc at the moment, I think that one needs restarted)
Ports are open, both tcp / udp ports are open using the internal server IP wich is MAC assigned by the router. Server — 10.0.1.2 — 9000
And same thing for the htpc — 10.0.1.8 — 3390Besides the obvious of firewall, ports, and ‘remote connection enabled’ any ideas?
-
Windows 7 and Remote Desktop Connection
Hey guys,
Bit of a long winded post, but please bare with me!
I am getting the following error when a user on our network is trying to access a VPN using RDP.
Researching this particular error is telling me to delete a registry value at HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing. It then tells me that if I receive the following error:
«The remote computer disconnected the session because of an error in the licensing protocol“
to run the RDP as admin. That does not work either. I cannot remote into the machine and i cannot remote FROM the machine and it was working fine yesterday for the user. There are a total of 3 users RDPing into a remote server that their job requires them to. This one user is the only person having trouble.I have called the company whose server they remote into and they are able to log in as this specific user without any issues at all. This user is able to use co workers computers using her login credentials just fine as well. However, if her co workers use her computer with their own credentials they are unable to remote in.
This leads me to believe that the RDP on this specific users computer is corrupt in some way. Is there any way to fix the RDP within Windows 7 itself?
Thanks!
-
Remote connection to Windows EC2 through RDP App — Error Code : 0x50331670
Connect RDP on MAC
How to connect RDP in Mac with Microsoft Remote Desktop 10. and rectify
Error: 0x204 when trying to connect to server using Microsoft remote desktop app on Mac
Remote connection to Windows EC2 through RDP App — Error Code : 0x50331670
-
Remote connection to Windows EC2 through RDP App — Error Code : 0x50331670 — Similar Threads — Remote connection EC2
-
Connect to disconnected RDP remote connection using tscon
in Windows 10 Gaming
Connect to disconnected RDP remote connection using tscon: I connect to RDP user session on the VM from command line tscon. The problem is I am not able to connect to the session if it is not active. Is there a way to connect to the rdp session using tscon even if user session is disconnected? Or Can I make disconnected session… -
Connect to disconnected RDP remote connection using tscon
in Windows 10 Software and Apps
Connect to disconnected RDP remote connection using tscon: I connect to RDP user session on the VM from command line tscon. The problem is I am not able to connect to the session if it is not active. Is there a way to connect to the rdp session using tscon even if user session is disconnected? Or Can I make disconnected session… -
Can’t access Microphone through RDP when MIC is directly connected to remote system
in Windows 10 Gaming
Can’t access Microphone through RDP when MIC is directly connected to remote system: I use RDP to connect to a number of headless no console Windows 10 Client systems.Trying to use Zoom and similar apps, I want to RDP to the remote computer and use Zoom, but I am NOT using a webcam or microphone connected to the local system the console system I am running… -
Can’t access Microphone through RDP when MIC is directly connected to remote system
in Windows 10 Software and Apps
Can’t access Microphone through RDP when MIC is directly connected to remote system: I use RDP to connect to a number of headless no console Windows 10 Client systems.Trying to use Zoom and similar apps, I want to RDP to the remote computer and use Zoom, but I am NOT using a webcam or microphone connected to the local system the console system I am running… -
Can’t access Microphone through RDP when MIC is directly connected to remote system
in Windows 10 Drivers and Hardware
Can’t access Microphone through RDP when MIC is directly connected to remote system: I use RDP to connect to a number of headless no console Windows 10 Client systems.Trying to use Zoom and similar apps, I want to RDP to the remote computer and use Zoom, but I am NOT using a webcam or microphone connected to the local system the console system I am running… -
RDP Remote Desktop cannot connect on Win10
in Windows 10 Network and Sharing
RDP Remote Desktop cannot connect on Win10: I’m a computer programmer and I can’t debug this stupid thing! Both my Win10 and Win7 local PCs can ping and see each other network drives. But none can RDP to another! Giving the notorious ‘3 dumb reasons’ excuse none of which applies, of course.Now, I don’t want ‘try…
-
Remote Desktop RDP connection errors after Win10 1909 upgrade
in Windows 10 BSOD Crashes and Debugging
Remote Desktop RDP connection errors after Win10 1909 upgrade: Hi,I recently upgraded a Lenovo P53 running Win10 1809 to Win10 1909. The Lenovo P53 is typically accessed via Remote Desktop RDP from an HP Probook 640 G1 running Win10 1809 and located at home. The HP accesses the Lenovo P53 over our company’s VPN.
The Lenovo P53 hosts…
-
RDP: Remote Connection Protical
in Windows 10 Network and Sharing
RDP: Remote Connection Protical: I went and opend up Microsoft Edge to enter my IP address in the box that I type a URL in and the I hited enter and this what the page said:
Hmmm… can’t reach this page
192.168.1.123 refused to connect.Search the web for 192 168 1 123
ERR_CONNECTION_REFUSED
Why? Did I…
-
RDP connection fails: Remote Desktop can’t find computer errors.
in Windows 10 Network and Sharing
RDP connection fails: Remote Desktop can’t find computer errors.: I have VM running windows 10 pro (other VMs using same config work fine).
Every time when I try to connect via RDP it throws: «Remote Desktop can’t find the computer [hostname]. This might mean that [hostname] does not belong to specified network. Verify the computer name and…
| 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. |
Главная » Грабли » Маленькая, но злая ошибка с публикацией 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. Естественно, самое главное не забывать, что для регулярных выражений шаблон, отвечающий любому числу любых символов не «*», а «.*» (точка — любой символ, * — любое количество).
Hopefully I am explaining this properly.
I can successfully Remote desktop connect if I am on my local wifi network at work, but when I go home and try to connect from a different network it fails.
I can connect easily with my PC from home , but not Mac High Sierra or Ipad for that matter.
I opened up the port for RDC in my ATT router and I use that IP address:port. This works with PC to PC.
I have the latest version of MRD, I even tried the beta but that had the same version # and failed as well.
I get error code 0x0300008 or 0x300005. Mainly saying the certificate failed.
The host PC is running win7 pro 64.
My PC at home is a small screen laptop, I would really prefer to use my MBPR since it is a much larger screen.
And yes team viewer works, but I’d like to solve this since I’ve spent so much time.
Thanks for your help,
Steve
Hi,
I’m running Microsoft Remote Desktop
10.2.1 (1143) Beta on Mac High Sierra 10.13.6 attempting to connect to a local (LAN) Windows 10 system.
I can connect initially, but if I suspend the Mac and reopen it and try to connect via MRD I get the error «Your session ended because of an error. If this keeps happening, contact you network administrator for assistance. Error ode: 0x4»
If I reboot the Windows 10 box, or connect to it via another remote tool (eg TeamViewer) and then disconnect, I can reuse MRD to connect again.
It’s as if its maintaining the original connection, and can’t reconnect.
I’ve only recently started using V10, and V8 had been working fine. I re-downloaded V8 and tried to connect whilst I was getting the V10 0x4 error and in V8 the msg is «Connection reset by peer».
Anything I can check on the network/router, Mac or Windows settings?
I also see a few other entries on here of similar issues from Mac High Sierra with no responses — has something recently changed on the Mac side that is causing issues?
Thanks.