3389 windows terminal services exploit android#

Also for all the extra ease of not needing to deal with outbound firewalls comes the lack of support from most RDP clients (last I checked the OSX clients couldn’t connect to RD Gateway)

Uses port 443/HTTPS so people behind poorly configured outbound firewalls can connect – sounds great but RDP already offers encryption and changing the port doesn’t add security. Sounds good but we only have one terminal server. Manage multiple servers from a single entry point with fine grained control over who can connect to what and so on. The only argument that I think holds any weight is setting up a VPN (such as Cisco) that supports two factor authentication, that sounds good but will massively reduce the number of devices that are supported.Īs far as I can see reading the advantages of a RD Gateway are: We allready have a PPTP VPN setup but it just uses the same account username/password combo to authenticate as our Terminal server would so I don't see a terminal server adding to our attack surface. “Don’t open port 3389 put a VPN in front of it” – but as far as I can see the two main arguments for this are encryption (Doesn’t RDP already do this?) and better authentication because people will brute force RDP. However when I talk about setting up a public facing RDP the responses are generally along lines of: Other obvious things such OS updates and anti-virus.Lock accounts with more than 7 failed attempts and look at maybe some script to block based on IP addresses with failed logins ( ).Set there encryption level to highest (with a certificate) and not allow “Negotiate”.My plan is to setup (obviously with our real domain name) to point to our server then secure it by: I want this to be stupid simple and work on everything.

3389 windows terminal services exploit android#

They are going to be using a bunch of devices including iPads, Android Divices, Windows (XP to 8), OSX, Linux, pretty much anything with an RDP client. We are looking at setting up a terminal server for staff to access remotely. TL DR We are looking at opening port 3389 for a terminal server all the advice I’ve seen is that its suicidal but without good explanations as to why.