Hello,

I first noticed this problem after performing a new install of agent 4.8.3 on an SBS 2011 server.    

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.

Hi,

Can you please check to see if the affected systems are running a 32-bit operating on a 64-bit supported processor?

Chris

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 November 9, 20159 yr by SimonW

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.

 

Hi Simon,

Glad it works now. Thanks for pointing out what the problem was, this helps other users too.

Chris

Chris,

What did you do to resolve it? I get what the problem is, but not the resolution.

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

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.

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

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)?

 

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

Hello Adam,

Can you please contact our Support Team at support@pulseway.com regarding your query