RD Gateway custom port

Ilia Ershov 131 Reputation points
2021-04-02T14:03:54.27+00:00

I am setting up RD Gateway on Windows Server 2019 to run on non-default port.
Settings applies, i can see correct bindings in IIS site and active listening port on the server. Also checked registry values - all correct
But clinet connection from Windows 10 RDP client with RD Gateway serverFQDN:port fails (with default 443 port connection successfull).
New custom port is available, I can access it via telnet
IIS Site opens on new custome port
Any ideas?

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
0 comments No comments
{count} votes

Answer accepted by question author
  1. Ilia Ershov 131 Reputation points
    2021-04-05T11:07:22.58+00:00

    The issue resolved with this registry entry
    [HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client]
    "RDGClientTransport"=dword:00000001

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Carl Fan 6,891 Reputation points
    2021-04-05T04:21:10.537+00:00

    Hi,
    Have you checked the settings below:
    Add Inbound Firewall rule for YourCustomPortValue
    Regedit

    [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\TerminalServerGateway\Config\Core]

    IsUdpEnabled REG_DWORD 0

    Cmd

    net stop tsgateway && net start tsgateway

    Regedit

    [HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\TerminalServerGateway\Config\Core]

    HttpsPort REG_DWORD (YourCustomPortValue)

    Cmd

    net stop tsgateway && net start tsgateway
    Hope this helps and please help to accept as Answer if the response is useful.
    Best Regards,
    Carl

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.