Reputation: 611
I created a windows azure VM with Windows server 2008 R2. The status of the server is running. The port is open. But I cannot RDP to it. It gives me an error
Remote Desktop can’t connect to the remote computer for one of these reasons:
- Remote access to the server is not enabled
- The remote computer is turned off
- 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.
Any help ? I actually created twice but no luck
EDIT
I am able to connect from home. but not from work network. so definitely a work network restrictions. Could you suggest what should be my next step to make it accessible from work
Upvotes: 18
Views: 39149
Reputation: 1
I had the same issue. I did the following to resolve it:
ipconfig /renew
cmd
and enterch -si 1
and then enter.ipconfig /release
Upvotes: 0
Reputation: 936
Here's what works for me. My friend at work figured it out.
1) In Azure, Create a Load Balancer.
2) Inside the Load Balancer > Go to Inbound NAT rules Use HTTP, Port 80, Single Virtual Machine, Target your VM, Target Port is 3389.
I don't know the underlying principles on how it works but it does. Thank you Mr. Arturo Tiangco
Upvotes: 0
Reputation: 491
Just wanted to share what worked for me.
After receiving an error prompt:
Connect is disabled for this virtual machine because of the following issues: Network interface 'vmwindows1094': Network security group 'VMWindows10-nsg' does not have inbound security rule that allows port 3389. VMWindows10-nsg
I have added an inbound port rule. Under VM > Settings > Add inbound port rules.
Port: 3389
Protocol/Source/Destination: Any (this can be configured based on your security rules)
Action: Allow
Upvotes: 0
Reputation: 1421
In my case it's the proxy settings. I changed it form my chrome browser settings
Settings -> show advanced settings -> Change Proxy settings -> LAN settings
and than enabling the proxy settings & Bypass proxy server for local addresses
Upvotes: 0
Reputation: 646
I was also facing the same issue. Have followed the Below steps and it got resolved.
Hope this helps to resolve the issue
Upvotes: 0
Reputation: 160
In my case,
After I did "Reset Remote", "Reset VM", Initially the Public and Private Port was different as expected, I changed both Public & Private to "3389" and then Edited the RDP File (which was originally downloaded from Azure) to have my UserID on it, then it worked. (Didn't bother on security as it is for a short session)
Upvotes: 0
Reputation: 7
An error message displays in the management portal for tenants when accessing a virtual machine using RDP (Connect->Desktop on the command bar), that Remote desktop can't connect to the remote computer for one of these reasons:
You may need to include the public profile in the setting that allows Remote Desktop through the virtual machine's firewall. You will need to adjust the firewall setting in the Control Panel of the tenant's virtual machine using Virtual Machine Manager. Perform the following procedure:
Upvotes: -1
Reputation: 30903
RDP port (3389) is widely blocked from network administrators of most corporations. What you need to do is either of:
Of course, if you use that VM for Secure Web (which works on 443) you have to chose another port number.
Upvotes: 32