Thanks Mike and Nick for the detailed description. I will look into the following points :-
- Performance of the server during the issues. I don't know anything about > your environment - how many users, what size server, etc., but if there is > excessive resource contention on the server running Tomcat and/or guacd, > this could cause failures in the connections. > - Network characteristics. Look between your clients and the Tomcat > server, between Tomcat and guacd, and between guacd and the remote > services. Look at bandwidth and latency. Monitor the network links for > any erratic or inconsistent behavior. Your 150-200ms latency could be part > of the problem, but, again, that depends on where that latency is. > Depending on the network characteristics you may need to architect the > Guacamole install a little differently (put guacd somewhere different, put > the full Guacamole stack somewhere different, etc.). > - Configuration. Guacamole works pretty well "out of the box" - that is, > if you use the defaults, and things suggested in the manual, you are > unlikely to get a bad configuration. If you start tweaking parameters, or > you forget to set something up, you may end up with results like this. > Follow the manual, avoid tuning things unnecessarily, and go with what > others are doing that works. > - Log files. Look at the log files carefully. Both Tomcat and guacd > logs, along with system logs. Are you getting OOM killer errors on Linux? > Are you seeing segfaults? What is being logged at the time that the > connections fail? Remember, the messages that you've posted above are > intended for telling end-users what's going on - the log files are what's > there to tell *you* what's going on. Don't forget to adjust the level of > verbosity for both Guacamole Client ( > http://guacamole.apache.org/doc/gug/configuring-guacamole.html#webapp-logging) > and > guacd ( > http://guacamole.apache.org/doc/gug/configuring-guacamole.html#guacd.conf > ). On Sat, Jul 20, 2019 at 5:33 PM Adrian Owen <[email protected]> wrote: > What results you get with mstsc? > > > > Adrian > > > > *From:* Mike Jumper [mailto:[email protected]] > *Sent:* 20 July 2019 07:36 > *To:* [email protected] > *Subject:* Re: ERROR : "Remote desktop currently unavailable" > > > > On Thu, Jul 18, 2019 at 3:28 AM Amarjeet Singh <[email protected]> > wrote: > > ...Error : The remote desktop server is currently unavailable. If the > problem persists, please notify your system administrator, or check your > system logs. > > > > This means the RDP server refused the connection. Your guacd logs will > note this. > > > > Error : The connection has been closed because the server is taking too > long to respond. This is usually caused by network problems, such as a > spotty wireless signal, or slow network speeds. Please check your network > connection and try again or contact your system administrator. > > > > Note : We have checked the ping request as well. There are no packet > drops. There is delay of only 150-200ms. > > > > That's some hefty latency. Even if you're not seeing packet drops, it's > likely the issue here is that your network is performing poorly. > > > > If you're positive there are no network issues, the RDP server may simply > not be responding. > > > > Error : The remote desktop server has forcibly closed the connection. If > this is undesired or unexpected, please notify your system administrator, > or check your system logs. > > > > Either an administrator logged in to the Windows machine and disconnected > the user, or Windows is configured to force the session to disconnect after > a certain time period and this time period has elapsed. Your guacd logs > would have noted these specifics. > > > > - Mike > > >
