This issue is with a 2011 SBS Standard server.
I have a user who works remotely. He can RDP to the server, or to a workstation if I give it a public IP through the firewall, but anything involving RD Gateway doesn't work, including RWA to a computer. After logging into RWA and clicking "connect", it tries to connect for about 1 minute then says:
"This computer can't connect to the remote computer. The two computers couldn't connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support."
- Client has this trouble with both of his Win8 machines. One used to be a Win7 machine, and it worked for a time while the W8 machine didn't. One day the W7 machine stopped working too. Since then, neither has worked, he upgraded his W7 machine to W8, and it still doesn't work.
- Same results when he works from a coffee shop, or off his mifi device
- A friend of his has the same trouble with a Win7 machine, both at the client's house and at his own house. However, an XP machine at his own house works fine.
- I've tested with the client's credentials from my own home Win7 machine without any trouble. I talked to another tech who did the same without issue.
- He has Comcast, with a recent upgrade to an all-in-1 modem/router/WAP device. He swears that it didn't stop working at the same time that it was changed out. I disabled the firewall and security in it, no change. I also tried disabling Norton, and resetting IE, and verifying that the RDP plugin is enabled in IE. No change.
It almost seems like it's a patch that's causing it, but I've found nothing on my internet searches. Or maybe the newer versions of windows use some kind of authentication through RD Gateway that the Comcast equipment won't allow? Anyone seen this?
TL;DR - RWA/RD gateway doesn't work for some computers at some remote locations. Older XP machines seem to work, W7/W8 don't. Terminal services works fine for them. RWA/RD Gateway works fine from my own Win7 machine too, using the same credentials.
For now, I put his work desktop on a static IP, used the firewall to set up NAT to a public address, and he just directly RDPs to that. But it's not the solution I want to stay with.
