Unable to connect to RD Gateway outside network
Hi, I have a single RDS, very small environment. I have RDSH and RD Gateway on the same box with a GoDadday Cert. AD Domain name is a .local. When I connect to the RDS through the Gateway it works fine internally, I get my desktop, externally it does not connect at all. Nothing in the event log on the server. If I use RDweb it works, my firewall is forwarding tcp:443, I don't have UDP Transport enabled, even when I did I was forwarding UDP:3391 as per the RDS Gateway Manager. If I wireshark my box I see connections from my WAN IP. The only errors I see are via the RD Client, this is just the usual "remote desktop can't connect" etc
OS is Server 2012 R2
Any ideas?
OS is Server 2012 R2
Any ideas?
ASKER
Hi Brain B, Correct, I can connect to RDWeb from outside my network. I Agree with what you said, I have infact made sure I am on the latests firmware revision for my firewall (Watchguard XTM) and I also restarted it out of hours. I can see the traffic passing through on the firewall logs. I have disabled the Windows firewall also. I will look at your suggestion to enable all traffic. Thanks.
ASKER
Hi Brian B, it still did not connect. I will open a support case with Watchguard, just to be sure.
Any more ideas would be welcome. I am out of them.
Any more ideas would be welcome. I am out of them.
Hi, enable UDP transport then check your Wireshark results between external and internal , do you see the UDP traffic when connecting externally ? Like Brian B said it must be some difference being introduced by your Watchguard.
Go to my Bio and send me the wireshark traces if you want?
OK thanks, the issue is your own firewall blocking this ? you can see it in the trace....
ASKER
I've requested that this question be deleted for the following reason:
I don't understand.
I don't understand.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi, You did not go into as much detail as the other guy, it was not the firewall where the RDS was, it was actually the firewall where the connection was coming from and in fact after I spoke to Watchguard tech support based on his feedback it turns out to be a Fireware bug. The other issue is that I don't want to expose logs to the Internet therefore it worked for me to not post them on a public forum.
This is a joke, I struggle to understand why this has been such an issue. Life is hard enough without going out looking for arguments, enjoy your T-Shirt I guess.
This is a joke, I struggle to understand why this has been such an issue. Life is hard enough without going out looking for arguments, enjoy your T-Shirt I guess.
Thanks for taking the time to properly close the question.
FYI: Instead of sending me T-Shirts, I have opted for Experts-Exchange to donate money to charity on my behalf.
FYI: Instead of sending me T-Shirts, I have opted for Experts-Exchange to donate money to charity on my behalf.
Your firewall logs will give you more information as to the exact nature of the problem, but I would start by making sure the firewall allows all traffic between the outside and this specific server, then narrow it down from there.