![]() ![]() Note: this is not a Virtual Machine (classic). A ping to the IP address fails four times with "Request timed out." Boot Diagnostics option shows the login screen. ![]() From the Quick start option, I don't see how to connect to this either I'm guessing, I need to specify a different port, but don't see where to do it here either => Update: this appears to be in the Network Security Group's Inbound security rules in the Azure portal.I did miss associating the subnet part of the Network Security Group to a virtual network, so I did associate my NSG with the default subnet set up for my Virtual Network.In the Network Security Group option for the VM, I verified that port 3389 allowed any source and wasn't specific.Flushed DNS on my computer, ipconfig /flushdns.The book seems to imply that simply downloading this file and connecting will work and there's no need to specify the port. You can perform this action using the services. Even though the How-To book doesn't show where/how to specify a port, when I download the RDP file from the Connect option, it specifies the port 3389. Try to restart the Remote Desktop Services service.The RDP file details (IP removed of course): full address:s::3389 The error occurs before I'm able to enter any credentials - it doesn't find the IP at all. Remote Desktop can't connect to the remote computer for one of these reasons: 1) Remote access to the service is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network. Upvote if it does.Following a how-to book's guide on setting up a VM through the Azure Portal and getting the error when trying to connect HTH other people who run into this post while searching. In any case, this should be in the docs for Remote Desktop Access - Microsoft PMs I hope you monitoring recent replies and are able to fix this in future Windows updates (add docs, and detection for this case). Remote client can send your password hash which matches the one stored locally on the machine. This type of setup (PIN from start) does not create a password hash which I assume is what RDP client uses to authenticate you in a remote session, so the step 3 (log out and log back in with a password) is what fixes it on the local machine and then Jump Desktop is a secure and reliable remote desktop infrastructure that lets you connect to any computer, anywhere in the world without VPNs or gateways. This would be the same case if you use Windows Hello, Fingerprint reader or other similar deviceĢ. When I setup the machine I immediately setup login PIN during initial process and have been using it ever since instead of password. MACHINE_NAME\user1, Password: your_MSA_passwordġ. After this I was able to login from Remote Desktop client on a Mac using the following: User: Log back in using password for your MSA (not PIN, fingerprint or anything else)Ĥ. Usern local user as the above post describes.ģ. I have observed that other users with longer names like are truncated to To verify run user manager: Start R: lusrmgr.msc. I verified that my user (me) is in the Remote Desktop Users group (this gets setup automatically in step 1). The machine was setup to use MSA from start, there is no specially created local user except the "administrator" that gets createdĢ. I enabled the Remote Desktop Access on my Windows 10 Pro machine while logged in as Microsoft Account (MSA) user. I run across this thread in the search of the answer and the following worked for me.ġ. I am not sure why the RDP can not authenticate the hotmail credentials that must be stored somewhere against the account? As it has no issue using these credentials when logging in to the machine locally. How many Windows sessions are in use when connecting to a user session via RDP. Hopefully this example makes sense and is clear on what I am trying to achieve. Windows 10 Dual Monitor remote session only showing one monitor on connection. However if I was to username " johnc" and password "mypassword" then it would autheticate and connect me fine as it can recognise the shortened system generated username in What I couldn't work out is why the user was only able to make a connection using thier shortened username as per the internal user that windows created automatically when the hotmail profile was created.Īs an example say my hotmail account was called " a nd password "mypassword" if i tried to RDP using username " "mypassword" I would received a username and passsword could not be authenticated error in the remote desktop connection dialog. I am ok with how to configure the system to allow remote sessions and also how to assign users to the correct group in order for them to connect. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |