I have win 11 machine form which I am trying to RDP server 2019. Once I enter user name and password I get following error.
The same server is connecting form my old laptop running win 10.
I have tried changing registry settings, change the setting of RDP experiences, group plolicy for system cryptography but no luck.
Found the issue, On win 11 machine the client encryption setting was not enable and causing the issue.
All I need to do is to enable the TLS protocol. I have used IISCrypto to enable this.
since 1-2 months I have problems on some machines in my environment when I try to connect via RDP.
The environment configuration uses a Microsoft PKI (Windows Server Certificate Authority). All computers that are integrated in the domain, request and are given a certificate from:
Computer
RDP (as server)
All machines in the domain have the ROOT CA and SUBCA certificate installed.
The problem is intermittent, on the same machine it does not work, the computer is restarted and for a while it works.
The credentials with which I connect work and the user with which I connect has permissions for RDP (he is a domain administrator).
When I connect using the FQDN (pc1.mydomain.com) the window to enter credentials appears, I enter them correctly and it tells me that the credentials are invalid. I make several tests to verify that I have not made a mistake when entering the credentials. It seems to fail in the connection protection process.
When I connect using IP to the same machine as before, the certificate appears, but if checked, the certificate is valid for the FQDN indicated above, so the certificate is OK (in date, valid and has not been revoked). If I accept the certificate, it starts the connection protection and finally connects.
If I access the same machine physically or through VMWare console, it lets me login correctly.
I have gone to check the Windows event log both in system, as application, as in RDP and I do not see any error, neither in the client from which I connect, nor from the server from which I connect.
If I connect from another machine that is not Windows (Mac) using the Microsoft RDP application, if it lets me connect, even when from Windows it fails.
It happens from several clients and on several machines to which I connect via RDP.
At the Firewall level all the rules are correct, both in the Windows Firewall and in the Network Firewall.
What is the operating system of the pc/server with the issues? I have an issue with an old Windows 2008 r2 server similar to this.
My Azure marketplace VM image was removed suddenly by Microsoft due to WannaCry vulnerability.
I'm trying to run Certification Test Tool 1.2 for Azure Certified on a new VM created from the new patched image.
I am logged in as a local administrator and running the tool on the VM as per the documentation: "The certification tool runs on a running VM, provisioned from your user VM image, to ensure that the VM image is compatible with Microsoft Azure."
I've tried running the tool on default Classic (not Azure Resource Manager) Windows Server 2012 R2 Datacenter and Windows Server 2016 Datacenter VMs.
I've tried turning the Windows firewall and UAC off.
I have not tried changing the firewall rules on Azure for the VM because: "When you create a Windows virtual machine in the Azure classic portal, common endpoints like those for Remote Desktop and Windows PowerShell Remoting are typically created for you automatically."
Here is the log created from running the tool on a brand new Azure Classic VM (with WannaCry patches applied):
5/18/2017 6:23:22 AM
Log generated by Certification Test Tool for Azure Certified
Test name: ****** Test Date :5/18/2017 6:23:22 AM Tested on: ******.cloudapp.net Test for: Microsoft Azure Test in: Windows Server
5/18/2017 6:23:24 AM
Test case/Verification: TestConnection
Description: Instantiates connection to the specified VM.
Connection Attempt: 1 Connecting to the Azure VM.... ******.cloudapp.net Error in connecting to the VM. Reason for not connecting to the VM : System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server ******.cloudapp.net failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic. at System.Management.Automation.Runspaces.AsyncResult.EndInvoke() at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult) at System.Management.Automation.Runspaces.Internal.RemoteRunspacePoolInternal.Open() at System.Management.Automation.RemoteRunspace.Open() at WindowsAddin.PSConnection.OpenSession() ----------------------------------------------------------------->
EDIT: Add a couple links.
I did manage to connect and run the tool, the trick was not to run it on the machine. You must run it from a remote machine. The tool denies access to itself.
I was using HP UFT 12.52 on Windows 7 without any problems. But lately we have moved to Windows 10 and it is not possible to connect to license server anymore. Connection to the license server is established over OpenVPN (the same as on Windows 7 machine)
There were two errors during installation on Windows 10:
could not register component HP.SP.Ext.STRemoteAgent.dll
could not register component HP.SP.Ext.STRemoteAgentSSE.dll
Registered them manually according to Error - Component registration failed for: HP.ST.Ext.STRemoteAgent.dll
Have already tried:
ping [license server IP] - OK
telnet [license server IP] [port] - OK
disabled UAC, SmartScreen, FireWall
UPDATE:
I have tired installation of UFT 12.52 on Windows 10 with full admin privileges: there where no error of component registration, and there was no error on licensing License server is not available, so the problem now is to figure out which admin privileges is still missing. Any suggestions?
I am trying to Remote Desktop onto an Azure instance from Mac OS X, but can't find a tool that allows me to do it. Address and username is fine, but none of the clients seem to have the capabilities to include the instance information.
I have so far tried the Miscrosoft RDC and CoRD but to no avail.
Has anyone succeeded in using RDP to an Azure instance on a Mac?
By default, you can't connect to an Azure Windows server except through the Windows Remote Desktop client.
To connect from OS X, whether through CoRD or the Microsoft Remote Desktop client for Mac, you need to turn off network level authentication:
Connect to the Azure server using the Remote Desktop client on a Windows machine
Under Control Panel, go to System, then open 'Advanced system settings'
On the Remote tab, uncheck "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)"
Re-connect from OS X
you need to create connect from microsoft remote desktop on mac
add ip, user, password
and you can connect now
if you still can't connect , check your azure endpoint setting
set the port that your firewall can pass
I have the same problem with you, and I think there is nothing to do with the network level authentication. The main reason is the default remote desktop app will connecting through port 3389, but your VM's default endpoint set another public port, here is what i do to solve it:
Download the latest version of Microsoft Remote Desktop app at Mac app store.
Add the port after your connection's DOMAIN/IP like yourvmdomain.com:yourpublicport. You will find the public port on endpoint setting tab. To me, the public port of Remote Desktop is 58494, so the connection will be xx.xx.xx.xx:58494.
This works for me.
Download the new Microsoft remote desktop client, which will allow you to connect to Azure instances without changing the configuration.
(As suggested in the comment from Kim Burgess)
It's tricky to connect to an Azure Cloud Service (aka Web or Worker Role) from a Mac, since PaaS instances sit behind a load balancer. You therefore need to specify which instance to connect to via cookies.
Royal TS supports cookies, so I got this working:
Install Royal TS free version (http://www.royalapplications.com/ts/osx/features)
Add the Remote Desktop plugin
Create new connection
Enter usual details (server/username/password)
Advanced > Connection > Load Balance Info > Cookie: mstshash=Your.Server#Your.Server_IN_0
This cookie info is available in the RDP file you can download for your instance from the Azure management portal (just open it in a text editor).
I use the Microsoft Remote Desktop application on OSX to connect to an Azure VM.
Recently I set up a VM from a Windows machine and was able to connect successfully using the admin username and password, but found that I had to reset the admin password to connect from OSX.
You can easily reset the password from the Azure portal for the VM. Go to "Support + troubleshooting/Reset Password".
I often have to enter the user name in the form:
PC name: xxx.xxx.xxx.xxx:yyyyy
Gateway: No gateway configured
User name: localhost\user.name
Hope that helps someone.
To access Azure instances from a MAC download Microsoft Remote Desktop client in Appstore. The default RDP client Azure provides doesnt work on a MAC. Worked for me
Check that your Networking Inbound Port rules (typically port 3389, but will change behind a load balancer) for the Azure VM allow you in.