I'm trying to access my service fabric cluster to see the files in it via RDP, but when I use mstsc /v:mycluster.brazilsouth.cloudapp.azure.com:3389 the following error message shows up:
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.
How do I enable my cluster to allow RDP connection?
Just say if you need more infos.
Thank you in advance.
SF cluster instances is a VMSS, by default, Azure opens RDP port on Load Balancer, you don't need change anything. You could find the RDP port on Azure Portal. <your resource group>--><Load balancer>--><Settings>--><Inbound NAT rules>.
According to your description, please ensure your VMSS instance is running.
This is documented in the Microsoft documentation at https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-nodetypes#remote-connect-to-a-vm-scale-set-instance-or-a-cluster-node.
Related
Going through exercises of Fundamentals of Azure, we(me and my team) are unable to connect via our Windows 10 desktops to RDP 3389.
Attached screen-shot.
Test connections outbound of RDP on the portal work as expected. Connection is successful.
But via clicking "Connect" from the dowloaded RDP file we get this error.
There is section to setup Linux VM via windows; currently exploring that but we see little hope.
There can be various reasons that RDP to Azure VM can fail.
Please check Troubleshoot Remote Desktop connections to an Azure virtual machine section if this helps.
If you just created a new VM in Azure it might be a firewall restriction that is causing the error. You can check if the RDP port 3389 be allowed from your client IP address in the network security group.
i'm using the portal : https://portal.azure.com, and log in with your Azure account.
I made 2 VM one Windows and other Linux.
But when i want to open them with RDP (win2016) and SSH (linux) with the Key Public/Private made correctly (puttyGen, Putty) i can't run them.
What i have to understand.
I'm connected on public wireless (SSID MacDonald or SSID Airport), my VM IP are founded with :
Get-AzNetworkInterfaceIpConfig
i set a Static IP from the Configuration NetWorking of my VM (Linux and Windows).
But what i can do to resolde this issue that i can't connect on my VM, with RDP or SSH ?
thank you
I think more info will be needed for someone to be helpful here.
first wall, what error message did you get when you try to connect using RDP or SSH?
did you allow RDP or SSH port when you create these VMs? These can be checked in VM settings page on the Azure portal. below is a screenshot of my Linux VM, for your reference:
update:
I'm not allowed to comment at the moment, so I'm posting my response to the additional info here.
if you're able to connect to the VMs using another connection, it means things work as expected on these VMs. Most likely the wireless connection you mentioned blocks outgoing RDP or SSH traffic. check with its admin on that.
I have one question regarding Azure connection from corporate networks.
I have created a VM and a database on azure. I can connect to the DB and RDP to the VM from my home machine. But when I am in office, I cannot connect any of them. This is the error I am getting.
I thought my office proxy is causing the problem, I removed proxy connection but that did not help. I created an instance on AWS and tried connecting to the Azure VM and DB from inside that instance. But that did not help either.
From this, I can think of only one reason that Azure does not allow incoming connection from corporate networks for free tier. I have allowed incoming request from everywhere in the rule of Azure VM and DB.
My azure subscription is free tier.
Can anyone tell me if that is correct or what is the correct way to solve this problem?
UPDATE: The question is not relevant anymore. The problem was with our office network. I have created a NAT to RDP to azure machine and everything is working fine.
I suspect that the Azure firewall is restricting access to your SQL server. As for your VM, you may have some ACLs set up which are restricting access.
To enable the SQL firewall rules:
https://azure.microsoft.com/en-us/documentation/articles/sql-database-configure-firewall-settings/
To check the ACLs on your Virtual Machine endpoints:
https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-set-up-endpoints/
I was onsite at a client location which disallowed outbound RDP traffic. They set up a SOCKS proxy and installed a SOCKS client on my machine with limited rules to allow RDP to Azure.
Today, my azure subscription credit has expired and my VM got shutdown automatically. I have added my credit and activated my account and restarted my virtual machine. But now, I am not able to remote login to my VM using Remote desktop like before.
I have checked the endpoints for "Remote Desktop (TCP, 3389, 3389)" and it exist. And check the VM status and it is Running.
But when i tried to login using Remote Desktop it says "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"
Kindly help me to resolve the issue.
Thanks in advance
Sundar
Check machine IP address. Becuase IP usually changes after shutdown.
I created a AX 2012 R3 DEMO Environment in the AZURE. I am trying to login into the RDP but not able to Login. And get the error as:
Remote Desktop Connection
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.
OK Help
Make sure connecting to the RDP port isn't being blocked by your firewall (possibly port 3389)
-This is a common problem
-You can see what PORTS are being used by going to the Azure Portal -> Virtual Machines -> Endpoints
Also make sure the VM is turned on :)