LSRemote - Some PCs won't accept any input and display black screen

[cology]

Some PCs work just fine and I found a couple that will not work at all with LSRemote. I found on one XP machine that if I start up XP Remote it just shows a blank screen with the cursor in the upper left hand corner. But if I leave it and remote desktop into the PC then LSRemote starts to work. It will then display the screen and accept input. But as soon as I exit Remote Desktop, LSRemote goes back to black with the cursor in the upper left hand corner. Very odd...

Windows XP Pro
Firewall disabled
Server service is running
Remote Registery is running
Admin shares are available (C$,Admin$)

I have attached a screen shot of the behavior. It will not accept any of the VNC commands or inputs.

[Hemoco]

Please test: Remote control 2.0 beta and leave your remarks

[Hemoco]

We don't control the development of winvnc, we just use it for the remote control so it's hard to tell when it will be ready.

[cology]

Lansweeper wrote:
We don't control the development of winvnc, we just use it for the remote control so it's hard to tell when it will be ready.

My bad, I didn't read your post properly. I thought you stated it has been fixed in winvnc and you are going to implement it in the next release. Any chance of using a different VNC product? UltraVNC (UVNC) version 1.0.5 is Vista-compatible. http://www.uvnc.com/download/index.html

[cology]

cology wrote:

Lansweeper wrote:
We don't control the development of winvnc, we just use it for the remote control so it's hard to tell when it will be ready.

My bad, I didn't read your post properly. I thought you stated it has been fixed in winvnc and you are going to implement it in the next release. Any chance of using a different VNC product? UltraVNC (UVNC) version 1.0.5 is Vista-compatible. http://www.uvnc.com/download/index.html

Bump for an answer!

Any chance of using a different VNC product? UltraVNC (UVNC) version 1.0.5 is Vista-compatible. http://www.uvnc.com/download/index.html

[Hemoco]

cology wrote:

Any chance of using a different VNC product? UltraVNC (UVNC) version 1.0.5 is Vista-compatible. http://www.uvnc.com/download/index.html

This is not currently planned.

[Hemoco]

We are aware of the RDP issue.
We will implement the new version of Winvnc if(when) it fixes the problem.

[cology]

Lansweeper wrote:
We are aware of the RDP issue.
We will implement the new version of Winvnc if(when) it fixes the problem.

Awesome news! Any timeframe for this release? It would help me out a ton!!! Thansk!

[cology]

More info...

Does TightVNC work on Windows Vista?

Unfortunately, TightVNC has known issues with Windows Vista operating system, just like all other versions and free distributions of VNC-derived software. Vista's new security features broke the way VNC service was implemented. And it's not clear yet how much effort would be required to workaround the problems. Unfortunately, that does not look very simple.

It seems it has an issue with XP SP3 also. That is what this XP machine is running that keeps TightVNC from working properly.

[cology]

Found the answer which is not a good one!!! I wonder if there is a fix for TightVNC that Lansweeper utilizes???

Services (like VNC) can interact only with session 0. Normally console is attached to session 0, but during or after an MSTSC session, session 0 might not be attached to session 0 and is therefore not available to VNC. Please try to connect to your XP using RDP and run QWINSTA.EXE from an MSDOS window. If "console" and "session 0" is NOT on the same line, then VNC cannot serve you the console. On my XP system, console is attached to session number 2 during RDP connection and unavailable to VNC.

Okay, now for the simple answer to your problem... have you rebooted the target machines to see if that will clear up your blank screen? There is a known issue that TightVNC will get a blank screen if an RDP session has been initiated prior to the VNC session. While there may be a way to clear the video block, rebooting might do the trick. Again this issue is caused by VNC emulating a local login, while RDP's behavior is to black out the screen while someone is logged in remotely.

Sure enough after I reboot the XP machine, LSRemote works because console is assigned to Session ID 0. But as soon as I remote desktop into the XP machine, it breaks again. It switches the console from Session ID 0 to ID 3.

As for Vista, LSRemote won't work at all with them since console is never assigned Session ID 0.

Any plan to fix this???