Can't connect to RDP through the gateway?

Question

System administration

Conditions. There is a big office, inside a domain network. An RDP gateway is also organized for the ability to work remotely if necessary. The gateway has its own certificate. The root store is issued by administrators and must be installed on the client computer in the root store. Authorization on the gateway - through the same domain account (login-password)
Problem.It is impossible to be connected to this RDP. Judging by the tests carried out, the connection is rejected by the gateway. Tried google, found almost nothing. Found small tips did not help. The system firewall is disabled in principle, the antivirus was disabled. Killed all processes except system ones. I even installed a virtual system with a different OS - the result is the same. Moreover, when I contacted the admins, they connected in front of me through my account from their remote computer. Everything is working. As for raising the gateway logs, while the admins did not pull, I decided to try to figure it out on my own. Haven't tried in safe mode, haven't tried from another computer with a different OS. View traffic failed. Port 3389 leaves only a few packets, more like ping.
I tried to connect from two different computers, which are geographically located in completely different places (different provider, IP, etc.). Both are running Windows 7 x64 uk-UA (no SP, no updates), both have been configured and used by me. No idea what the problem is. Some software, or settings I made, or something else.
Well, actually, the question. What is wrong and what to do? How to localize the problem? Why are my computers so unique and not liked by the gateway?

Answer 1

Problem solved. In an unknown way.
Our manager (not the admin!) set up/added something somewhere - and it all worked. Haven't found out the details yet. I'll try to find out later.

Answer 2

There are actually a lot of options:
1) Ask administrators who have access to that very gateway - let them look in the logs;
2) Change the provider, but even from a laptop from a cafe, go to see if your provider is doing stupid things. Rarely, but it happens.
3) The firewall is completely disabled - there should be no problems on your part. An additional point is the anti-virus systems, if they are, I would turn them off completely at the time of the test.

Answer 3

what messages do you get when the gateway rejects?

Answer 4

First, at a minimum, roll up SP1 and all updates to the system and install the latest version of the RDP client.
Take a close look at local logs

Answer 5

Let's start by checking the connection.
You can check the connection by telnet.
At the command line, type
telnet <IP RDP server> 3389
If the connection succeeds, the screen will be cleared and the cursor will blink from above, if it does not pass, you will see an error after a while.
If the connection goes through, then continue to dig the RDP server, watch the Windows logs, etc. But usually there shouldn't be any problems. If the connection fails - 2 options:
1. the connection is cut by your external gateway - this is 100% for the admins.
2. connection is cut by a fusee on the RDP server itself (which should not be, because according to you it is disabled).
PS: telnet client is disabled by default in Win7/8, it must be enabled in Programs and Features->Turn Windows features on or off.