Neoware Thin Client CA21- VNC Operation
I'm trying to get the pre-installed version of VNC working on a Neoware CA21. The service is pre-installed (defaults to manual) so I can set it to Automatic and it will start when the system does. I do not know how to set a password on the service and this prevents the client from connecting. If I start the .exe file manually from the install folder it tells me the service is already running. If I stop the service and run the .exe file it starts and I get a configurable icon in the system tray. I can set a password here and connect to it but the password for the .exe and the password for when it runs as a service do not appear to be the same...when the machine restarts I can't connect. Any ideas on how to set a password on the service version of VNC which runs with this model of thin client? Any help is greatly apprecaited.
Software/Hardware used:
neoware thin client windows xp embedded VNC
So my question is how to I setup a VNC password when it runs as a service? Let me know what you think, thanks!
Software/Hardware used:
neoware thin client windows xp embedded VNC
ASKED:
April 14, 2010 2:13 PM
UPDATED:
April 15, 2010 1:51 PM
RELATED QUESTIONS
Answer Wiki:
Last Wiki Answer Submitted:
Be the first to answer this question.
All Answer Wiki Contributors:
Be the first to answer this question.
To see all answers submitted to the Answer Wiki: View Answer History.
Are you completely sure it is a password issue ?
Yes, the error is very specific and normal VNC operation, it will not work without setting a password. Its just that in this case the password I assign to the executable file when it runs vs the service do not seem to match even though they come from the same application.
Have you tried the HP support forums ?
Also, I’m not sure if this CA21 is the same as the e90. If so, maybe you could find an answer in these e90 manuals
I haven’t tried the HP support forums, I wanted to try this site out and see if anyone has run into this issue. The CA31 and e90 are the same model, nothing in the manual regarding this problem.
Well, this is a great site with many experts covering different IT areas, but as always, there might be some specific situations/problems that have not been experienced by any member so far, and could be better covered by the device manufacturer support people.
Anyway, there is still a chance that some other member provide a useful answer.
If not, It would be nice if you could share the solution when you find it.
Sure will, here is my work-around:
The VNC app can be started as either a service or by running the executable. I drag the exe shortcut to the All Users startup folder, configure it with a password, then reboot. It now starts with the system and the password configured. The only drawback is it won’t start until someone logs in while running it as a service would. Not a big deal.