Jump to content
SimonW

The agent failed to start rd session

Recommended Posts

Hello,

I first noticed this problem after performing a new install of agent 4.8.3 on an SBS 2011 server.   Capture.thumb.PNG.3e8593d3c33a63dbc6e4fe 

I thought it was related to just this Server (which has been rebooted since install and the firewall is disabled), but found that this error occurs with a number of Windows 7 hosts as well.  I can't immediately establish the reason why some hosts connect and others don't.

I've not encountered this error before so am unsure where to start with troubleshooting.

Appreciate any assistance.

Share this post


Link to post
Share on other sites

Do you mean a 32 Bit version of Pulseway Agent, or the OSE?

I have checked two of the systems that fail to connect (Windows Server 2008 and Windows 7) and both OSE are 64 bit.

I've just noticed that I am unable to connect to any host that is on an external network to our Enterprise Server.  (I'm definitely trying to Remote Desktop, not Microsoft Remote Desktop Connection)

Edited by SimonW

Share this post


Link to post
Share on other sites

Found the cause of my problem.  The Pulseway server was presented to the Internet via Windows Application Proxy, hence the public IP address of each host was that of the WAP server.

 

Share this post


Link to post
Share on other sites

Hi Ken,

Do you use a Proxy to connect to the Internet? If so, try adding *.pulseway.com and pulseway.com to the proxy direct access list.

Chris

Share this post


Link to post
Share on other sites

I am also running into this situation. We just upgraded our Server 2008 R2 64Bit to Server 2012 R2 64Bit to make use of the remote desktop function and tool. However when trying to connect to any device we have it setup for we get the error "The agent failed to start the rd session." 

Any help with this would be amazing.

We do not use a proxy. Our Pulseway server is located on AWS though.

Share this post


Link to post
Share on other sites

Hi Charles,

Would you be able to send an email to support [at] pulseway [dot] com? I'll get pick up your email once I see it.

-Paul

Share this post


Link to post
Share on other sites

I too am running an Enterprise server behind WAP.  Is there any fix for allowing remote desktop to work, when it thinks the clients are on the local network (thanks to WAP for masq the source IP)?

 

Share this post


Link to post
Share on other sites

I just signed up for the trial SaaS, have two agents installed on Windows 10 Pro 64bit, and get the same error when trying to remote desktop - any logs or trouble shooting I can do?

Direct connection, no proxy

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Similar Content

    • By BigEz
      Hi Everyone!
      How is possible assign automatically an hardware asset to a customer in PSA when a ticket is created trough a support request ? What kind of configuration i've to do in RMM side to match a customer in PSA?
    • By Ian G
      Hello,
      We are long-term Pulseway customers but lately the Pulseway client has developed a bug and continuously uses up to 20%+ CPU utilisation.
      We logged this with Pulseway on the 4th of July this year but they have been completely ignoring the ticket. I regularly reply to the email thread for an update (at least once a week) but I am ignored. The only time I had a meaningful response was when I threatened to cancel our subscription. This was short lived and now I am back to being ignored with no status updates on my ticket.
      We like the product but we have a handful of servers with this bug and I am simply installing other monitoring products on them. Today I have sent my usual email to Pulseway support asking for a status update on my ticket but I'm certain I'll get nothing back...
      The next step will then be to install a better monitoring product like Infradog and to write the same post on Spiceworks so people know that Pulseway doesn't offer good technical support.
       
    • By patrickjung
      I hope I am in the right Subforum to ask this question.
      I recently started to use Pulseway and am impressed what I am able to do with it but I noticed one feature missing that I need.
      Is it possible with Pulseway to check Servers/Clients with log files for backups if they have been successful or failed? For example if there is a NAS connected to a network and someone is doing a USB Backup on it I want to check if it has failed so I will get a notification when it fails. I want to use it on Windows and Linux machines so my best guess is to use a script of somekind right?
       
    • By istvankolkert
      I have enabled lost of notifications on my pc but none of the show up, the did once or twice but not anymore, has anyone a idea why?
    • By John @ Maven
      I am having issues with pulsewaycredentialprovider.dll stopping the Windows login screen from loading on Windows 10 1809.
      I have submitted a ticket to support at support@pulseway.com as well.
      The issue is that with Pulseway software installed and the credential provider loading the system boots to the displayed screen but will go no further.  I am able to run terminal and PowerShell commands from the web interface (prior to software uninstall) but can never log in.  Pulseway remote does not work either.
      This is happening on two Windows 10 1809 DELL Optiplex computers with fresh Windows 10 PRO installations.
      RIght now our only solution is to leave Pulseway uninstalled.
      Any information or solution helpful.
      Thanks.
      John


×
×
  • Create New...