The other day, I was struggling with a deployment. My updated my cert but it didn't seem to make any difference; I still kept getting FABRIC_E_SERVER_AUTHENTICATION_FAILED (or something like that). Anyway - bad. 

It was time to get dirty and go to the machines themselves. Having not done that in a while, I needed a refresher. I bring that information here. 

In a managed cluster, your ports start at 50000 and go up per instance. For a typical 5-node cluster, this would be 50000, 50001, ...50004. But what URL? 

If you go to your managed cluster in the Azure portal, you'll see in "Overview", the URL for the SF Explorer. THAT'S IT... almost. 

Let's say it's https://hawkins-av-club.eastus.cloudapp.azure.com:19080/Explorer.

For the machines themselves, it would be:

  • hawkins-av-club.eastus.cloudapp.azure.com:50000
  • hawkins-av-club.eastus.cloudapp.azure.com:50001
  • hawkins-av-club.eastus.cloudapp.azure.com:50002
  • hawkins-av-club.eastus.cloudapp.azure.com:50003
  • hawkins-av-club.eastus.cloudapp.azure.com:50004

To actually connect, you can issue the following command on a plain old command shell.

mstsc /v:hawkins-av-club.eastus.cloudapp.azure.com:50000

You should get the Remote Desktop to launch. Invariably, there will be some warning about a problem with the cert because Microsoft screws that up too. However, as long as you remember your username and password for managing the cluster, you should be good to go. 

Once logged in, you can interact with the desktop. At this point, it's good to know your command line stuff because there aren't a lot of icons. It's mostly Start/Run... type. 

But hey, at least you're under the hood.

Comments


Comments are closed