I'm new to screenconnect and on trial right now. Very likely to buy if I can get the Unattended application to work well. The first issue I've noticed is that I have a couple of instances where the guest doesn't reconnect to the server after closing out a session.

Laptop with Windows 7 Home Premium: I installed unattended client from an admin user account, and it showed up on the server as "Connected". I Joined it with my host account and it worked perfect; I had a perfect session. I closed out the session and noticed the Guest wasn't "Connected" anymore on the server. I've noticed that it takes 1 or 2 seconds for a guest to reconnect after closing out the session. However, 3 hours later it was still Disconnected. On the guest laptop, the client status jumps between "Waiting to Connect..." and "Connecting..." every few seconds, never actually making it to "Wiating for other party". I restarted the laptop and when the service launched it connected successfully, and once again I was able to join the guest from my Host and I had a perfect session. Once again when I closed the session the guest didn't reconnect to the server, and it continued to show "Disconnect" and on the guest laptop the unattended application status was switching back and forth as above. I stopped the service and started it again and it reconnected to server again. Same results after one good session. I reinstalled the unattended build and problem solved.

HOWEVER, I'm having the same issue with another windows 7 home premium pc again, but this time reinstalling the unattended client isn't fixing it. I've got a couple dozen unattended guests all on Windows rangiing from xp to vista to 7, but the only "common denominator" is Windows 7 as none of my xp/vista machines had this problem. Note that not all my Windows 7 machines have/had the problem either, so its not consistently a windows 7 issue.

Any thoughts???

OK, this is clearly a Windows 7 issue. I'm up to 5 windows 7 guests all with the exact same scenario as above. Only 1 has NOT had that problem at this point, and that may be a fluke that I've not been able to amply test... What do I need to do to make this work in windows 7?

We figured this out. It was a proxy setting. When our stuff first attempts connection, it tries without consulting the proxy settings. After a failure it is supposed to try with the proxy. Well, it was trying with a proxy on any successive attempt (not just failures), and his proxy settings were a little screwy.

Now we try with a proxy every odd time we connect, and after a successful connection, we correctly reset our counter, and don't increment it on disconnection.

I don't think so, but i'll be in build 1985 released today.