Share this post

Link to post

Share on other sites

jmwills 284

jmwills
284

Logmein requires Java Scripting in order to run so make sure that is enabled on both ends, They have recently update the client software a couple of times this year so, if nothing else works, I would remove the software from that machine, delete form your console, and reinstall it. All in all, about a 2 minute process.

Share this post

Link to post

Share on other sites

Savvy 0

Savvy
0

Logmein requires Java Scripting in order to run so make sure that is enabled on both ends, They have recently update the client software a couple of times this year so, if nothing else works, I would remove the software from that machine, delete form your console, and reinstall it. All in all, about a 2 minute process.

Hi Jmwills, sorry I forgot to mention that I have installed all recent updates as well as removed and reinstalled on both client and console (logmein site).

All posts I find from Google mention the that the terminal server display error is commonly caused by installing logmein through a remote desktop session. however I actually installed it locally.

Share this post

Link to post

Share on other sites

pcdoc 114

pcdoc
114

Interesting, I use logmein with WHS 2011 everyday with not issues and no special configurations doing exactly what you described. It sounds like something else on your network is attached to you server. Have you tried it with any of the clients shutdown to see if it could possibly be on of the computers connected to it?

Share this post

Link to post

Share on other sites

Savvy 0

Savvy
0

You installed the update that turns off the remote display when you login from LogMeIn. No reason why your session should not be allowed to continue.

Nope, no settings turned on that turns off remote display that I can find.

Interesting, I use logmein with WHS 2011 everyday with not issues and no special configurations doing exactly what you described. It sounds like something else on your network is attached to you server. Have you tried it with any of the clients shutdown to see if it could possibly be on of the computers connected to it?

I will try shutting down all clients and then attempt to connect again, any idea of which service it could be?

I set up a WHS2011 box a few months ago for a friend's dad, I logmein into it about once a week to check on it..

Did you by chance install logmein from a remote desktop session? That might be giving it issues..

edit: just read where you said you installed it locally.. very bizarre issue, have you tried updating your graphics driver?

Yep googled as much as I could before posting, so I definitely know its not the installation.

I haven’t tried updating GPU drivers, but if they were at fault logmein wouldn’t work at all right?

Share this post

Link to post

Share on other sites

pcdoc 114

pcdoc
114

Just out of curiosity, I'm wondering why you want to use LogMeIn. I use RDP to access mine and it works just fine.

Can not speak for him but me I have several reasons. For starters, I can every system (even those with Home Premium) available to me on one page. RDP does not work on versions less than professional without a hack. Secondly Logmein is more secure than RDP. Lastly, I can also have systems outside my network also attached to it along with those on the same network. In addition, every system is independent so if something gets hosed such as this silly roll-up, I can still access my systems even if the server is down. For me it is a better and more versatile solution than using RDP.

Share this post

Link to post

Share on other sites

ikon 438

ikon
438

I don't know about the security aspects of the 2 (I'm under the impression that MS has done quite a bit to secure RDP, but I could certainly be mistaken). I don't have the issue of not being able to get to my computers because the server is down; I RDP into all of them directly. I guess that kinda makes all of mine independant too.