Hi All,
I have followed the article written below by Keith, and have set up a virtual network on Azure with one machine hosting AD & DNS, and the other configured for RDP session virtualisation (so i can publish an app for multi user access)
http://blogs.technet.com/b/keithmayer/archive/2013/09/04/step-by-step-remote-desktop-services-on-windows-azure-a-cost-effective-alternative-to-desktop-as-a-service-part-2.aspx
i have already sorted the Microsoft licensing and published the app required, however i have encountered an issue with either the DNS or RD Gateway - the issue is that when i type the address of the RDP machine in an internet browser (http://machinename.domain/RDweb)
it times out and cannot find the machine to even get to the RDweb login screen, and a 'could not connect' is displayed in the browser.
If i type the azure address of the machine in the browser (https://machinename.cloudapp.net) then i can get to the RDweb screen OK. I have tried checking the DNS settings and the AD machine is OK (internal address of 10.0.0.4), however it times out when looking
for the RDP machine (internal address of 10.0.0.5). I cannot connect by the external IP address of the VM either.
Would someone possibly be able to point me to some information on how i can configure/check the DNS or RD gateway so that the RDP machine is able to be found? (sorry i am not really a gun at DNS related material) - I have tested and if i try to access the RDP machine via the RDweb address in IE internally from one of the machines, it does work and the RDweb login screen appears, just not from an external source.
Any help you could offer would be much appreciated.
thank you,
Michael.