Jamie Thomson on Thu, 27 Mar 2014 15:12:47
I have an HDInsight cluster that I cannot connect to using RDP and the reason (it appears) is that my client explicitly blocks port 3389. This isn't a problem for most Azure VMs because they use different port numbers (and one can change the port number anyway) however this is not the case with HDInsight VMs which still seem to be on 3389 (I'm assuming this is the case given that I cannot connect to them).
Clearly I have to go and do some pleading to my client's IT department however in my experience those debates tend to last for weeks so in the meantime, is there any method by which the RDP port for the HDInsight head node can be changed?
thanks in advance
Dharshana_Bharadwaj on Mon, 31 Mar 2014 16:11:27
With the current release of HDInsight, a supported approach to change the RDP port for HDInsight service is not available. However, there is a feedback site for HDInsight here for logging any feature requests for future consideration. Thanks for your feedback!
Jamie Thomson on Mon, 31 Mar 2014 19:58:03
cool, thank you Dharshana.