What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Monitoring RD Gateway Server Deployments

Votes:

0

We have several different Remote Desktop (aka: Terminal Service) deployments that users access via RD Gateway Server (2012 R2) setups. Some deployments have a separate connection broker server and others have the connection broker service collapsed onto the RD Gateway Server. Connections are established to the Gateway Server via a public IP on TCP:443 or UDP:3391 depending on the connection transport method being used. The user is ultimately routed through an authentication/load balancing process which connects them to one of the Remote Desktop servers allowing for secured connections without deploying site-to-site VPNs.

In the past several months, we have had occasions where the Gateway Server stops processing inbound connections requests which stops any new sessions from being created. Existing sessions typically continue to operate. The users do receive a generic RD Gateway error stating that the remote computer they are trying to reach is unavailable. When this happens, we sometimes have to restart the Gateway Svcs or often times it takes a reboot of the Gateway server.

I would really like to monitor this process better, so we would be able to respond quicker to the incident prior to having a user alert us of the issue. Ideally, I would like to be able to setup monitors that would login as a test user via the RD Gateway system and record average login times and then trigger an alert if it were to be unsuccessful. If not the ideal method, then any other suggestions on how to monitor would be greatly appreciated.

Is there anyway of doing this with PRTG? We have a few thousand sensors deployed and being able to do this would really help remove a thorn from our side while we continue to investigate the root cause of the underlying issue.

Thank you,

-C

2012r2-rdp rd-gateway rdp

Created on Dec 12, 2017 1:40:43 AM



4 Replies

Votes:

0

Dear Chad,

RDP logins cannot be monitored out of the box. If the issue would be to monitor a set of defined connections, an option could be to use a flow sensor or packet sniffer to monitor the RDP bandwidth for certain connections and alert if that is zero for some time. However the setup has to be done manually, including the input of the according filter rules. And on top of that, it is not exactly what you want to monitor.

It might be easier trying to see if the gateway gets event log entries on failure. Then the event log could be monitored.

Created on Dec 12, 2017 1:37:06 PM by Arne Seifert [Paessler Support]



Votes:

0

Hello! Have the same question, so no any solution for the past years?

Created on Feb 14, 2019 7:55:16 AM



Votes:

2

Regarding current connections monitoring to RD Gateway you can use PS: (Get-Counter @("\Terminal Service Gateway\Current connections") -ComputerName "127.0.0.1").CounterSamples.CookedValue

Created on Feb 14, 2019 11:18:54 AM



Votes:

2

Dear Vasiliy,

in this case, please implement a custom sensor. Regarding requests for a sensor build into PRTG, we established a way which allows us to estimate the demand: How to propose a feature.

Created on Feb 14, 2019 11:43:11 AM by Arne Seifert [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.