0

Here is what I have done so far -

  1. Configured Remote Desktop Services
  2. Purchased a domain "domain.com"
  3. Purchased a wild card ssl certificate, the thought is that I want to use "rds.domain.com" to access the RDS Server.

RDS Deployment Properties -

RD Gateway:

Server name: rds.domain.com

RD Web Access:

RD Web Access Server= RDS.DOMAIN.LOCAL URL: = RDS.DOMAIN.LOCAL/RdWeb

Certificates

The certs have been installed and the Green Bar is showing up when I go to rds.domain.com

IP Setup

In the domain controller I set up a new Forward Lookup Zone called domain.com, then created a Host (A) Record with the name rds, and pointed it to my RDS server.

I then forwarded ports 443, 3391.

Within my Domain Host, I configured two (A) records, @ XX.XX.XX.XX and * XX.XX.XX.XX - the public ip addresses are the same for both.

I can connected perfectly fine internally, but externally it does not seem to work.

Thank you in advance for any help someone can provide.

Community
  • 1
Matthewi
  • 1
  • 1
  • Naturally. How will the FQDN's be resolved externally? External users don't have access to your internal DNS do they? – joeqwerty Jun 05 '18 at 12:19
  • 1
    Nope, they do not. You are correct sir. Not sure what I was thinking, as soon as I saw "How will the FQDN's be resolved externally", I laughed and then cried a little on the inside. – Matthewi Jun 08 '18 at 03:50
  • LOL. Hopefully that means you've got it fixed. – joeqwerty Jun 08 '18 at 12:14

1 Answers1

0

When you attempt the connection from outside does the rds machine hear you knocking on the door? Are you getting through to it and it ignores you, or are you not reaching it at all? A few things to throw out there: If you are trying to connect using the Microsoft rdp client (mstsc) then you should be forwarding port 3389. You can use the client on other ports but 3389 is the default. The rds machine should log your attempted connections from outside so see if it mentions anything when you try to connect. If it doesn't log anything then you aren't reaching it. So check the router/firewall(s) and make sure you are forwarding the packets. If it does log something that will usually tell you why the connection failed. if the outside machine you are using to make the connection is not a domain member then your login credentials could be the problem. you would need to login with "domain name slash username" not just username. Just thinking out loud here, HTH.

Larryc
  • 315
  • 1
  • 5