Jump to content

Remote desktop services - RDweb and connecting internally.

pooley

By pooley
in Windows Server 2012

 Share

Recommended Posts

pooley

pooley

Posted
Posted

Ok long story short, LA have decided we can no longer have port 3389 open to the www but are happy to have 443 open.

 

So i'm moving from a std RDS setup to using RDweb.

 

Single server setup, all roles on one server.

 

All certs are installed and I can connect to my RDWeb fine. From within there I want the staff to be able to click on the RDP icon and connect to the RDS sever.

 

when I click on the RDP icon or go to "connect to a remote pc" and enter the RDS computer name it opens an RDP window and tries to connect over 3389.

 

What am I missing? Been at this all morning and can no longer see thee wood for the trees!!

 

Cheers

 

Si

Steve21

Steve21

Posted
Posted

You aren't missing anything really :p If you click RDP it'll RDP! (But that's RDP within the network, not externally)

 

Think of it this way, the RemoteApp part (web based) is supposed to be a gateway, if you have the gateway on the internet, then RDP internally would connect as normal RDP does via 3389 etc.

 

If you want it all web-based you can use RemoteApps (As RemoteApps not RDP) and publish each app like that.

 

If you look at my old example http://www.edugeek.net/forums/windows-server-2012/175934-rdp-options-3.html#post1511844 you'll see we have both, RDP as an option (This is RDP within the network as it's to a different server), or RemoteApps. Both externally only require 443 as the RDP is still a RemoteApp but internally it'll use 3389 etc

 

If that makes sense?

 

Steve

pooley

pooley

Posted
  • Author
Posted (edited)

Yep makes sense, but I stil can't connect, 3389 is obviously available internally.

 

I'm now getting "remote gateway server is temporarily unavailable"

 

When I try and connect it's showing as it connecting to

 

Remote computer : rdsserver.blabla.internal

Gateway server : remote.externaldomain.com

 

Which looks correct.

Edited by pooley
  • Thanks 1
pooley

pooley

Posted
  • Author
Posted
We had exactly the same issue. Ask your LEA to put port nating on for you.

 

 

I have a NAT from external IP to Internal Ip which has always worked when we had straight RDP access.

Steve21

Steve21

Posted
Posted

You shouldn't need any gateway as it's an internal RDP. That's for people externally to remote in via.

 

Make a RemoteApp program that just runs mstsc /v "myserver", when they click the program it should remote direct to the server internally

 

Steve

pooley

pooley

Posted
  • Author
Posted
You shouldn't need any gateway as it's an internal RDP. That's for people externally to remote in via.

 

Make a RemoteApp program that just runs mstsc /v "myserver", when they click the program it should remote direct to the server internally

 

Steve

 

Hi Steve, cheers for that but it still gves the gateway error.

 

Just to be clear, I am trying to access the server from outside of the school network, I can log into rdweb fine, it's just the link from rdweb to my rdp server (same server) doesn't work.

Steve21

Steve21

Posted
Posted

Do any of your apps work? If you do notepad or something on the server. Just wondering if it's not entirely happy with the outside setup in total more than the RDP side of things

 

Steve

pooley

pooley

Posted
  • Author
Posted
Do any of your apps work? If you do notepad or something on the server. Just wondering if it's not entirely happy with the outside setup in total more than the RDP side of things

 

Steve

Ahh good shout, and no it's not happpy with any apps.

 

Keeps popping up a connection window, I press connect and it says cannot find computer. It looks llike it's trying to resolve my internal server fqdn as an external url ?

 

So DNS?

alfatec

alfatec

Posted
Posted
Do you have Bypass RD Gateway server for local addresses ticked in Deployment properties. Also is this from a Domain connected laptop externally?
pooley

pooley

Posted
  • Author
Posted
Just to clarify that's a DNS address as per your external address? Not internal domain address?

 

Steve

 

Yep, so internal DNS record rdserver.local.bla - remote.externaldomain.com

pooley

pooley

Posted
  • Author
Posted
I have recent configured RDS on server 2012 and 2016. I got few error when I had the RD Gateway server name entered wrongly and when certificates were not trusted.

 

follow this link

https://www.virtuallyboring.com/setup-rd-gateway-role-on-windows-server-2012-r2

 

I have installed third party ssl cert and working without any problem.

 

Thanks mate, all certs are signed and trusted, looking again at what i've entered where.

Steve21

Steve21

Posted
Posted

If you set it up via the gateway/Server Manager it should have already assigned a self-signed and it copies it to the RDS hosts etc for you. (If you have a wildcard can add it for all though)

 

It'll show up under the config of the collection, and show the 4 certs under the Broker/SSO/Web Access and Gateway.

 

Steve

pooley

pooley

Posted
  • Author
Posted (edited)

RAAAAAAAAAAA DN bloooooooomin SSSS

 

Added a CNAME pointing to external fqdn as appoosed to A record pointing to IP and it works. (I thought I'd done that already, probably did and then removed/changed it)

 

Wood / trees.

 

Thanks for all the help guys.

 

Been at this since yesterday, always trus your instincts, if it's MS based and doesnt work it's a dns issue ;)

Edited by pooley

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...