I have created a test lab in Azure utilizing the guides below:
https://www.microsoft.com/en-us/download/details.aspx?id=41684
and
http://social.technet.microsoft.com/wiki/contents/articles/24277.test-lab-guide-install-exchange-server-2013-on-the-windows-2012-r2-base-configuration.aspx#Step_4_Install_and_configure_EX1
I have a server named EX1 that's running Exchange. Last night I was able to connect to it just fine but this morning I am unable to connect to it via the Azure portal. Here is the error that I get:
The machine is Running as shown under status. I've tried resetting the remote desktop connection which didn't work. I switched the endpoints for Remote Desktop to 3389 for the public port but still can't get in. Any suggestions?
Have you tried deleting the endpoints and re-creating them?
Related
I have set up an server on Azure and have the Remote Desktop service running with a couple apps I want to connect with.
I can see my apps but when trying to connect I get
We couldn't connect to the remote PC because the PC can't be found. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
Error code: 0x104
Workspace with apps showing
I have no problem connecting to same server with Remote Desktop, but only the apps. When connecting to the RDP I use the public IP and port so I think there might be and issue in Azure not letting me in?
I'm trying to connect to the remote desktop but i'm getting following errors. I went to the azure portal and my rdp port is open i.e. 3389 as it's showing up in the dashboard.
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.
I actually created twice but still no luck.
Same scenario was happen with me as well. For that i upload the certificate to the windows azure portal. After that i was able to connect to the windows azure cloud service successfully.
I am using a Cloud services running a single worker role with two instances. For almost a year I have been able to connect using RDP.
This week I wanted to connect, but couldn't. The remote desktop connection display the wrong credentials displaying: "Use the following credentials to connect: Password for Admin"
When an deployment is uploaded to the staging environment, I am able to connect. After swapping to the production environment, I cann't connect.
But the old deployment can be connected in the staging environment.
When I set up the connection from another PC, I am able to connect.
I think there is something going on with my PC, but no idea where to look.
Can somebody help me?
It turned out I have checked "Save my credentials" by accident. There was an entry in the Windows Credential Manager.
Deleted the entry, I can connect again.
After creating the RDP account, I had to reimage the webrole (Roles And Instances -> WebRole -> Reimage). After the reimage I was able to connect.
Hoping someone can shed some light on my RemoteApp/Azure dilemma
I have successfully setup RDS on Server 2012 VMs in Azure - session host, rdweb and connection broker, opted not to have a gateway as only running one session host.
Created an self-signed certificate in RDS tools in Server Manager and bound this to rdweb, named the cert remote.cloudapp.net. I also uploaded this to the cloud service for the VMs using Azure powershell.
So via an Azure VM on the domain in Azure I can connect to remoteapp and successfully run an application.
However when I connect externally via a browser on my standalone laptop I get the following error in the RDS Log:
Remote Desktop Connection Broker Client failed to redirect the user
REMOTE\appuser. Error: NULL
I have tried the fix of look for an Pool ID of NULL in the Windows Internal Database and I only have one pool ID which is the collection I created, so can't be that.
Also get this error returned when I try to run a remoteapp after successfully logging into the RDweb page:
Remote Desktop Services cannot connect to the remote computer for one
of these reasons: Remote Access is not enabled to the server Remote
computer turned off Remote computer not available on the network
I am totally stumped, is there something I am missing that is so simple.
Just installed azure connect on my localhost, but it won't connect. I see my machine dbates-HP as a active endpoint in my vistual network/connect section on my azure portal and organized it into a group.
I can see in the azure connect portal that the machine endpoint is active, and that it refreshes since the last connected updates.
My local connect client lists the following diagnostics messages:
Policy Check: There is no connectivity policy on this machine.
IPsec certificate check: No IPsec certificate was found.
Also tried with firewall turned off.
Duncan
In some scenarios getting Windows Azure connect to working becomes very complex. I have worked on multiple such scenarios and found most common issues are related with network settings. To start investigate you need to collect the Azure Connect logs first from your machine and try to figure the problem out by yourself. I have described some info about collecting log here:
http://blogs.msdn.com/b/avkashchauhan/archive/2011/05/17/collecting-diagnostics-information-for-windows-azure-connect-related-issues.aspx
To open a free Windows Azure support incident please use link below:
https://support.microsoft.com/oas/default.aspx?gprid=14928&st=1&wfxredirect=1&sd=gn
Have you "linked" your Azure role with the machine group you created? The message "There is no connectivity policy on this machine" suggests that you haven't defined (in portal) to whom this machine should connect to.