Cant connect to the Remote Desktop Gateway?

My saved RDP connections through Remote Desktop Gateway server suddenly stopped working with error message:

Your computer can't connect to the Remote Desktop Gateway server. Contact your network administrator for assistance

However I can connect directly by IP without RDP Gateway

Windows 10 Pro v.1601

• My knee jerk reaction is check your firewall rules/port forwarding/authentication groups pointing to any internal authentication servers using something like RADIUS.

  Are you using RADIUS for authentication? If so, check your NPS authentication group[s].

  Spice [2] flagReport
  Was this post helpful? thumb_up thumb_down

• Can you manually use the RDG from the outside?
  If you sign into RDWeb with chome and download one of the .rdp files, open it up with notepad and make sure it has the correct RDG settings

  Spice [1] flagReport

  Was this post helpful? thumb_up thumb_down

• My recommendation is pretty much close to the other ones. Check that the RD gateway is accessible through the public IP as well. Trace the configuration same as your working environment and make sure it matches your configuration obviously with different IP addresses but same logic.

  Spice [2] flagReport

  Was this post helpful? thumb_up thumb_down

• BBigford wrote:

  My knee jerk reaction is check your firewall rules/port forwarding/authentication groups pointing to any internal authentication servers using something like RADIUS.

  Are you using RADIUS for authentication? If so, check your NPS authentication group[s].

  Sorry don't know how to answer this yet. I never had to configure this part manually even on the existing working RDS. I'll get back to you on this. I only setup the RD CAP and RAP and they seem to be correct.

• dbeato wrote:

  My recommendation is pretty much close to the other ones. Check that the RD gateway is accessible through the public IP as well. Trace the configuration same as your working environment and make sure it matches your configuration obviously with different IP addresses but same logic.

  I can access the FQDN and IP of the Gateway from external and internal [had to add DNS forwarders internally]. Right now the setup is single server [public IP > single server]. Public IP works and I have tried two different Public IPs just to isolate the forwarding rules as well.
  

• I'm clueless, even with running BPA doesn't show any errors. Tried different remote locations and computers and they all seem to give the same result.

• Thanks for the input guys. I figured out my issue. Based from the information I provided above and the BPA result, it kinda suggested that there wasn't an issue with my RDS config. I reviewed my network settings and updated it it to a simpler structure. Works well now.

• fernanespiritu wrote:

  Thanks for the input guys. I figured out my issue. Based from the information I provided above and the BPA result, it kinda suggested that there wasn't an issue with my RDS config. I reviewed my network settings and updated it it to a simpler structure. Works well now.

  Can you provide more input about what you changed? Something with your firewall/etc? You mentioned a "simpler network", please elaborate on that. Definitely helpful to people in the community, as well as anyone online that stumbles upon this thread, to give some clarity about what specifically resolved your issue, if no suggestions in here were helpful.

  Spice [2] flagReport

  Was this post helpful? thumb_up thumb_down

• BBigford wrote:

  fernanespiritu wrote:

  Thanks for the input guys. I figured out my issue. Based from the information I provided above and the BPA result, it kinda suggested that there wasn't an issue with my RDS config. I reviewed my network settings and updated it it to a simpler structure. Works well now.

  Can you provide more input about what you changed? Something with your firewall/etc? You mentioned a "simpler network", please elaborate on that. Definitely helpful to people in the community, as well as anyone online that stumbles upon this thread, to give some clarity about what specifically resolved your issue, if no suggestions in here were helpful.

  Well basically my main network is on 10.0.0.xx with 255.255.0.0 and I was trying to build the new RDS environment on 10.0.12.xx. I can ping everything from anywhere internally so I never thought it would be an issue. I would say, I haven't found the real cause of issue or mis-configuration I made. But placing the new RDS environment on the same octet with the prod network made it easier. My network is simple, no vlans or complex routing, but would need to revisit placing the RDS network to a different octet next time.

  does that make sense?

  Spice [1] flagReport

  Was this post helpful? thumb_up thumb_down