I have a server setup as a DC with AD and RDServices installed.
I have a second server with the GW and CB and IIS and licensing and whatever else it installed.
I am using no-ip.biz to provide the external name / DNS for RDWeb.
I am using DSL and have the ports 443; 3389; and 3391 open.
_______________________
Internally, I can open RDWeb, click on an app and VOILA! It opens just fine.
Externally, I can open RDWeb, login with my credentials, click on an app . . . . then wait for it... wait for it andBOOM! The really helpful "...gateway unavailable..." message appears. At this point, it might as well be theBlue Screen of Death.
I am not an ordinary dummy but I am extraordinarily challenged. LOL.
DNS is my biggest weakness - but I am almost at wits end, thinking there has to be something I need to do in DNS to make this work. Many of you say (in other posts) create an A record for external and internal and etc etc etc. I am supposed to be a professional and "get it"...... but I don't. That's my weakness. I am a DNS Flunky.
But alas, I hope my brothers and sisters who are great at quantum physics and algebraic triginometric pi-alpha equations can help me out here.
Embarrassed? Sure... but at least I am asking for some help.
Hell, I'd even open up a rescue session so I could watch what the hell you do to fix this damn thing.
_________________
In all seriousness, guys, I am really stuck and need some guidance and help. Anything someone will do to resolve this would be more than appreciated.
Chris