Connecting NT4 Client to VNCserver running HP-UX 11.00
aft er reboot of server
"Beerse, Corné"
cbeerse@hiscom.nl
Wed Aug 28 09:19:01 2002
> -----Original Message-----
> From: Sam.Gigliuto@doi.vic.gov.au [mailto:Sam.Gigliuto@doi.vic.gov.au]
> I get a grey screen when connecting with my windows NT4
> client to my
> HP-UX 11.00 server
> immediately after rebooting the server. It gives me a message saying
> something like" Initial screen loading'
> which soon disappears and then the grey background continues
> to display. I
> have configured the
> VNC startup as part of the normal startup process i.e in the
> /sbin/rc3.d
> directory but no matter how I shuffle
> the order of the processes, I continue to see this problem.
> If I stop and
> restart the VNC process
> using the same script as the reboot calls from the command line it all
> starts to work.
>
> Is anyone else seeing this problem ( I saw an email in
> the list from
> someone
> who was experiencing the same problem)?
> Is there somewhere I can go to get some info on how to fix this
> problem?
I don't know details on your problem, I do know some HP-UX odities.
What user is starting the Xvnc? Best to start Xvnc as a 'normal' user. User
accounts over 60000 (or such, like nobody) are restricted for security
reasons. Accounts in the sytem range (0 - 100) don't use proper shells or
don't have proper homedirectories for the ~/.vnc directory. From the past, I
recal using the '-pn' option to Xvnc.
I've succesfully put http://www.sourcecodecorner.com/articles/vnc/linux.asp
on linux. Major differences are:
No need to start xdm or such as it is most likely already running. Test this
with `Xvnc :4 -query localhost`. Only need to alter /etc/services and
inetd.conf files.
In inetd.conf:
Don't use 'nobody', better use 'sys'.
Use proper path to Xvnc ;-)
Use a working fontpath! (grab it from `xset -display :0.0 -q`)
Might need -pn option.
CBee