Black Screen after RDP session

[axslinger]

Heres the scenario. In my business my wife has to connect to our Win Server 2003 once a day to do some reports. She has to do it with VNC because she has to utilize programs that are already running on the locally logged in users desktop.

Everything works fine until I do a RDP session from another computer or from a customer site. After that, every time she logs w/UVNC, she just gets a black screen. The only "solution" I have found is to reboot the server. Then it works ok until I use RDP again. I was previously using RealVNC and didn't have that problem but I wanted to standardize my organization switch everything to UVNC.

Is there a solution to this issue?

Thanks,
Brian

[mod=494,1227986724]moved from mslogon to general help[/mod]

[redge]

yes, uvnc 1.0.3
uninstall old release 1.0.2

steps.

1.
http://sourceforge.net/project/download ... 103RC6.exe

2.
http://sc.uvnc.com/Ultravnc_Addons_Setup_103RC6.exe

3.
[topic=10763][/topic]

[jwagner]

I have downloaded and installed uvnc 1.05, default installtion on win 2003 virtual server, I still get the black screen after RDP session and cannot get beyond the balck screen.
In the properties window Video Hook Driver is unchecked, and will not stay checked.
Check Video Hook driver says driver cannot be found.

Can anyone help me over this black screen hump?

[redge]

follow this topic
[topic=14196][/topic]

[jwagner]

Thanks for your suggestion, redge, but:
Terminal Services is running,
I aconnected, I can click on the conection icon and see that I ma connected.
my problem is the black screen.
My sense is that the driver for the screen is not installing properly.

When I connect to my own desktop computer, (where the screen does come up properly) the right-click admin properties window does show the video hook driver checked (but only while connected), but in the remote instance I am fighting with, I cannot determine whether the video hook driver is checked because I cannot see with the black screen.

I tried installing the drivers separately that came with the v 1.05 install, but the system came back wiht a message that I cannot install drivers from an RDP connection.

[redge]

sorry, i won't use mirror driver.

[jwagner]

Let's forget about the miror driver, that was just an attempt on my part to get beyond the black screen.

Are you aware of any other steps I can take to get beyond the black screen issue?

[redge]

you need ultravnc server installed as service for success
uvnc_service

[jwagner]

Redge, I have included the uvnc_service line in the ini file, and restarted the remote computer.

under Services I now see uvnc_service as Started with Automatic setting.

Unfortunately, that still does not eliminate the black screen.

Right clicking on the uvnc server icon does show the Uninstall Service line and the Start Service (must be installed first) lines

When I click the Start service line, a window pops up that has Use Program wiht restricted access clicked on, when I unclick and say OK the window disappears, but so does the icon in the tray. Does this mean anyhting?

[redge]

you total confusing.

Redge, I have included the uvnc_service line in the ini file, and restarted the remote computer.

This above comment of service command is totally unrelated for rdp issue, is only help for connect winvnc to repeater before user logon (allow access of logon screen)

Right clicking on the uvnc server icon does show the Uninstall Service line and the Start Service (must be installed first) lines

if uvnc_service really running, you should see only:
Install Service (greyed aka inactive)
Uninstall Service (black color)
Stop Service (black color)
Start Service (must be installed first) (greyed aka inactive)

[jwagner]

Redge, I really appreciate that you reply. But you are right, I am confused.
I have been trying to follow the varous threads that you referred me to. So I try everything someone says they have had success with.

If you have a step-by-step solution on how to get beyond the RDP black screen I would be very grateful. Otherwise I will just have to forget UltrVNC and find a differnt tool altogether.

Thanks for your help.

[YY]

Hi! jwagner,

Based on your description, I think the primary problem is the UVNC not running as service. There may be other issue, but this must be fixed first.

Please follow these steps:
1. At Service.msc, Stop the uvnc_service if you found it has started.
2. At Service.msc, make sure Terminal Services is running.
3. Right clicking on the uvnc server icon, then click "Start Service (must be installed first)"
4. A "Run As" window popup and ask for confirm. To save the setting, you must UNCHECK the "Protect my computer and data from unauthorized program activities". Of course, your user right must be sufficient to write/save the "ultravnc.ini" too. Click OK

5. Then the UVNC EYE icon may disappear, and appear again after a short moment.

If the above can be done w/o problem, the UVNC s/b running as service successfully. You can open the TaskMgr to confirm, you should see two sessions of winvnc.exe

After the above is OK, try your test again to see what will be going on.

[kev123]

It may be caused by session bitmap cache in Terminal service. I came cross it using RDP, then I solved it by this: http://support.microsoft.com/kb/555840

___________________________________________
NeoRouter - the network revolves around you
http://www.neorouter.com