Gururek's community posts

Hi Polina,
Thanks, those files seemed to fix the problem!

The host log doesn't contain any mention of a connection attempt. I just checked the server logs and found this:
203.15.34.142;585222764309;;;V51794E7E7DE441F8;69105;09-19-06 29-03-2019;Error: Viewer was banned.
This is repeated over and over.

Yes I have, before the host upgrades. The server is also the latest version.

I have recently upgraded all our computers via remote deployment to the latest host version, and now I am unable to connect to any host with the Viewer. They are all connecting to the server and I can see them listed in Viewer as online, but when I connect the host goes offline for the duration of the 5 retries and then comes back online. If I try again, the same thing.
This is the error I'm getting:

26-03-2019__23:17:28__939 Connection #984376. Connection to "LAB8825.fdn.uq.edu.au.local". Mode: <Authorization>. Connecting...
26-03-2019__23:17:28__940 InetConnection #984376. Internet connection to LAB8825.fdn.uq.edu.au.local (203.15.61.39:15155).
26-03-2019__23:17:29__067 InetConnection #984376. Method "Connect" - OK. LAB8825.fdn.uq.edu.au.local connected to ID server: 203.15.61.39.
26-03-2019__23:17:29__070 InetConnection #984376. Socket error. Name: "LAB8825.fdn.uq.edu.au.local", host: "203.15.61.39:15155". Exception class: "EIdConnClosedGracefully". Message: "Connection Closed Gracefully.".
26-03-2019__23:17:29__071 Connection #984376. Connection to "LAB8825.fdn.uq.edu.au.local" failed. Mode: <Authorization>.
26-03-2019__23:17:29__072 Context #984376 removed. Mode: <Authorization>.

Thanks for the response, a restart did seem to solve the problem. Was that mentioned in the installation procedure as a requirement?

Hi,
I upgraded my viewer to 6.9 Beta and it was working fine, but yesterday I upgraded the RU Server to the latest Beta as well and now the server is becoming unavailable. The RU Server works for a short while, then the Viewer no longer connects to it and the address book is no longer able to be opened on the server itself. If I stop the service and start it again, it works again for a short while and then stops.
Regards,
Alex.