Either start the server (Xvnc) from /etc/dt/config/Xservers or start it
with the -query <hostname> flag.
Tom
On Tue, 20 Mar 2001, Ajit Alok wrote:
> I wish I could have native solaris look for my window client when I connect to Unix
> VNC server.
>
> Like one provided by exceed.
>
>
>
> Thanks
> Ajit
>
> vnc-list-digest wrote:
>
> > vnc-list-digest Tuesday, March 20 2001 Volume 01 : Number 1068
> >
> > ............................
> > VNC-LIST-DIGEST is a daily collection of the messages sent to the
> > VNC mailing list. For more information about VNC see the home page
> > http://www.uk.research.att.com/vnc .
> >
> > In this issue:
> >
> > RE: VNC Passwords Resetting on Servers After Reboot
> > VNC Performance Issues on Win NT / Novell networks
> > RE: Installing Vnc on 500 workstations
> > Re: VNC security (uhm... maybe a feature request)?
> > RE: Some CPU ideas
> > ............................
> >
> > ----------------------------------------------------------------------
> >
> > Date: Mon, 19 Mar 2001 18:19:46 -0500
> > From: "Nick Fisher" <[EMAIL PROTECTED]>
> > Subject: RE: VNC Passwords Resetting on Servers After Reboot
> >
> > Hi,
> > I had a similar problem recently. I think your gonna find that you set the
> > "user" password rather than the "default" password. Thus before the user is
> > logged in it uses the default password (old) and when your logged in it uses
> > the user password (new).
> > Assuming your using the Win version......
> > I personaly used regedit to clear the HKCU\Software\ORL\WinVNC3 (User
> > settings) and HKLC\Software\ORL\WinVNC3\Default\Password. Then restart VNC
> > and it'll prompt for a password.
> > - --THERE MUST BE A BETTER WAY THAN THIS--
> >
> > I've found the only good way to change to password on multple servers is by
> > creating a .reg file with the correct
> > HKLC\Software\ORL\WinVNC3\Default\Password in it and use that. I would be
> > delighted to hear of a better way though....
> >
> > Nick Fisher
> > ITS Interactive
> > www.itsinteractive.com
> > [EMAIL PROTECTED]
> > Phone: (617) 964-6250 x125
> > FAX: (617) 964-2280
> >
> > - -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Bardaville, Phil
> > Sent: Monday, March 19, 2001 12:15 PM
> > To: [EMAIL PROTECTED]
> > Subject: VNC Passwords Resetting on Servers After Reboot
> >
> > Hello,
> >
> > We use VNC on multiple servers and are having a problem after booting
> > said servers. The VNC password seems to go back to the old password
> > after the reboot and not the most recent password.
> >
> > Has anyone else seen this or can someone explain what possibly could be
> > happening?
> >
> > Thanks,
> >
> > Phil
> >
> > - ---------------------------------------------------------------------
> > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > to [EMAIL PROTECTED]
> > See also: http://www.uk.research.att.com/vnc/intouch.html
> > - ---------------------------------------------------------------------
> >
> > ------------------------------
> >
> > Date: Tue, 20 Mar 2001 11:57:48 +1100
> > From: John IRELAND <[EMAIL PROTECTED]>
> > Subject: VNC Performance Issues on Win NT / Novell networks
> >
> > Hi
> >
> > As technical support on a large site we frequently use VNC to access users
> > remote desktops. The network consists of Windows NT and Novell servers, over
> > CISCO implemented VLANS. The problem is, there is a sharp descrease in VNC's
> > performance when remotely accessing a workstation on another subnet, when
> > the remote user is logged in. However when you log the remote user out and
> > log in yourself, VNC's performance increases to an acceptable level. Has
> > anyone experienced this issue or would know of any way around it. I read
> > through the FAQ and archived mailing lists however could not find anything.
> >
> > Regards
> >
> > John Ireland
> >
> > ------------------------------
> >
> > Date: Mon, 19 Mar 2001 21:27:48 -0500
> > From: "Rick W. Vanover IV" <[EMAIL PROTECTED]>
> > Subject: RE: Installing Vnc on 500 workstations
> >
> > You may think also of the SCRIPTIT tool - which I believe is part of the NT
> > Resource Kit? Info of it:
> > http://www.microsoft.com/ntserver/nts/deployment/custguide/scriptit3.asp
> > Don't know where to get it, but put the net to the test and it'll arrive
> >
> > R
> >
> > - -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Renato Jr
> > Sent: Monday, March 19, 2001 5:55 PM
> > To: [EMAIL PROTECTED]
> > Subject: RES: Installing Vnc on 500 workstations
> >
> > About the values from registry ... you export to *.REG on key
> >
> > HKEY_CURRENT_USER\Software\ORL
> > HKEY_LOCAL_MACHINE\SOFTWARE\ORL
> >
> > EXAMPLE:
> >
> > by script user, run:
> > C:\WINDOWS\REGEDIT.EXE /S F:\UTILITY\VNC.REG
> >
> > Renato Jr
> > Duetto Informatica
> > [EMAIL PROTECTED]
> > (51) 332.1702
> >
> > - -----Mensagem original-----
> > De: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]Em nome de Gamlem, Noralf
> > Enviada em: Segunda-feira, 19 de Margo de 2001 05:09
> > Para: '[EMAIL PROTECTED]'
> > Assunto: SV: Installing Vnc on 500 workstations
> >
> > Hmmm... I can imagine installing the program on one WS first, then record
> > the changes. Actually my experience says these files are necessary:
> >
> > c:\program files\orl\vnc\vnchooks.dll
> > c:\program files\orl\vnc\winvnc.exe
> > c:\program files\orl\vnc\zlib.dll
> > c:\windows\system\omnithread_rt.dll
> >
> > Export the registry settings from HKEY_CURRENT_USER\Software\ORL and
> > HKEY_LOCAL_MACHINE\SOFTWARE\ORL. In addition it would be wise to export
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices if
> > you would like to run Vnc as a service (remove everything except the WinVNC
> > line).
> >
> > Copy the necessary files and update the registry settings through the logon
> > script and when the user reboot next time you will be up and running
> > (hopefully)...
> >
> > - -Noralf-
> >
> > - -----Opprinnelig melding-----
> > Fra: Liza Vorster [mailto:[EMAIL PROTECTED]]
> > Sendt: 19. mars 2001 08:45
> > Til: '[EMAIL PROTECTED]'
> > Emne: RE: Installing Vnc on 500 workstations
> >
> > Hi There
> >
> > How will I go to work if I have to install VNC on +- 300 win98 and 95
> > machines we did copy files to the c drives of the users and ran the vnchooks
> > file to update the registry settings but this does not work. We receive lots
> > of dll errors and we stil have to ask the users to run this files for us
> > befor we can remote control them
> >
> > Thanks for your help
> > Liza
> >
> > - -----Original Message-----
> > From: John Poznicek [mailto:[EMAIL PROTECTED]]
> > Sent: Saturday, March 17, 2001 6:24 AM
> > To: [EMAIL PROTECTED]
> > Cc: [EMAIL PROTECTED]
> > Subject: RE: Installing Vnc on 500 workstations
> >
> > I currently rollout vnc to workstations / servers across our wan, on
> > an as needed basis. Using a simple script, and the soon.exe that
> > is part of the NT4.0 resource kit. This could be accomplished without
> > the util soon. Just makes it easier to create the at command.
> >
> > The user never knows that the script has been run, nor does it ask
> > the user for any response. The vnc service is installed, and password
> > and other registry entries are installed, and the service started.
> >
> > It could be very easily modified to run from a login script. Or to
> > run thru a list of your machines and remotely install to them all at
> > once, etc..
> >
> > Please tell me your 500 workstations are NT, or 2k - and we wont have
> > a problem. If your running 9x - you have more problems than trying
> > to run an install script from a login <grin>
> >
> > The basics are just scheduling a job to install the registry keys,
> > and then running the winvnc.exe You can get by the user not having admin
> > permissions this way <grin>. You then have another scheduled job run
> > the winvnc.exe -install and then do a net start. All done.
> >
> > Let me know if you interested - and I'll drop you a copy of my script.
> >
> > Be more than happy to step you through setting it up - a little more
> > detail on your network would be helpful. Ie are you 100% NT, and do
> > you have the schedule / task service running - it is defaulted to be
> > running, but maybe you have turned it off? You could add a line in
> > the script to make sure this service is running, etc..
> >
> > let me know,
> >
> > John Poznicek, MCSE
> > [EMAIL PROTECTED]
> >
> > - ------------------------------
> >
> > Date: Fri, 16 Mar 2001 14:22:26 +1100
> > From: Bradley ROBINSON <[EMAIL PROTECTED]>
> > Subject: Installing Vnc on 500 workstations
> >
> > Hi to everyone, and thanks to all that have worked on Vnc.
> >
> > I have been given the task of rolling out Vnc to approx 500 windows based
> > workstations. I'm looking for a way of running the Vnc setup.exe through
> > login scripts and would like a way of doing this without the user needing to
> > click the next buttons etc, is this possible?
> > I'm also looking at a way of using a service with admin type rights to
> > install and start the service on NT.
> > I've looked over the site and through the mailing archive and cannot find
> > any info relating to this, If anyone can help or has suggestions it will be
> > very much appreciated
> >
> > Regards
> > Brad Robinson
> >
> > Ansto Server Support
> > [EMAIL PROTECTED]
> >
> > - ------------------------------
> >
> > - ---------------------------------------------------------------------
> > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > to [EMAIL PROTECTED]
> > See also: http://www.uk.research.att.com/vnc/intouch.html
> > - ---------------------------------------------------------------------
> > - ---------------------------------------------------------------------
> > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > to [EMAIL PROTECTED]
> > See also: http://www.uk.research.att.com/vnc/intouch.html
> > - ---------------------------------------------------------------------
> > - ---------------------------------------------------------------------
> > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > to [EMAIL PROTECTED]
> > See also: http://www.uk.research.att.com/vnc/intouch.html
> > - ---------------------------------------------------------------------
> > - ---------------------------------------------------------------------
> > To unsubscribe, send a message with the line: unsubscribe vnc-list
> > to [EMAIL PROTECTED]
> > See also: http://www.uk.research.att.com/vnc/intouch.html
> > - ---------------------------------------------------------------------
> >
> > ------------------------------
> >
> > Date: Tue, 20 Mar 2001 03:11:23 +0000
> > From: Jonathan Morton <[EMAIL PROTECTED]>
> > Subject: Re: VNC security (uhm... maybe a feature request)?
> >
> > >Unfortunately, VNC does not really support any kind of (enforced)
> > >seperation of these two kinds of users. The underlying issue, from a
> > >security standpoint, is that VNC doesn't differentiate between
> > >authentication and authorization: if you authenticate at all, you're
> > >authorized (as far as VNC is concerned) to do whatever you want on the
> > >server. From a security standpoint, it'd be useful to see
> > >segmentation between the "view" mode and the "modify" mode (where your
> > >input is actually processed by the server).
> >
> > I've thought about this issue as well - VNC needs a better security system,
> > quite badly. It's perfectly possible for the VNC server to differentiate
> > between two passwords, and disable all input controls for the alternate
> > password. However, I don't know of any server which actually does this. I
> > also agree that this would be a useful feature.
> >
> > - --------------------------------------------------------------
> > from: Jonathan "Chromatix" Morton
> > mail: [EMAIL PROTECTED] (not for attachments)
> > big-mail: [EMAIL PROTECTED]
> > uni-mail: [EMAIL PROTECTED]
> >
> > The key to knowledge is not to rely on people to teach you it.
> >
> > Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
> >
> > - -----BEGIN GEEK CODE BLOCK-----
> > Version 3.12
> > GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
> > PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
> > - -----END GEEK CODE BLOCK-----
> >
> > ------------------------------
> >
> > Date: Tue, 20 Mar 2001 03:53:00 +0000
> > From: Jonathan Morton <[EMAIL PROTECTED]>
> > Subject: RE: Some CPU ideas
> >
> > >>> Notice that, opening notepad and maximizing it to full screen then typing
> > >>> will cause a full window update for each char.
> > >
> > >Just curious -- I realize that the hooks will tell WinVNC that it needs to
> > >process the entire client area, but what kind of processing does WinVNC do
> > >after that to determine how much actually changed? Does it perform any
> > >kind of differencing operation?
> >
> > I understand WinVNC does do a simple differencing operation, to determine a
> > smaller changed-area for transmission. ChromiVNC uses a more complex
> > algorithm to work out more precisely where areas have changed (see below -
> > I considered it necessary due to certain properties of Macintosh window
> > redraws). Xvnc has much more control over what is drawn where, so it
> > doesn't do any of this (even though it might actually help in some cases).
> >
> > >Something I had considered (and WinVNC may already be doing) was that if
> > >the server maintained a memory storage of what had been transmitted to the
> > >client, then it could compare new regions to that and only send the
> > >differences. As a further optimization, you could have a "Delta Hextile",
> > >or (better) "Enable Delta Encoding" checkbox like the "Enable CopyRect
> > >Encoding". Then, you could BitBlt the new region against the stored region
> > >using the XOR RasterOp, which might even be performed by hardware in newer
> > >video cards. The resulting region would be black in all areas that had not
> > >changed, and Hextile encoding should be extremely efficient in transmitting
> > >that, whereas it might not be efficient re-transmitting all of the
> > >underlying image. Of course, the viewer would have to recognize that it
> > >was receiving an XOR Delta packet, and would need to use the XOR RasterOp
> > >as well when adding it to the screen.
> >
> > Very interesting idea - it might make it's way into ChromiVNC as an
> > optimisation, although probably not as a separate encoding unless other
> > implementations adopt the new encoding.
> >
> > The way ChromiVNC works is to keep a copy of whatever it sent to the
> > client, and a separate "modified bitmap". When the 'kernel hooks' generate
> > a modified region, it is marked in the "modified bitmap" and set aside.
> > Once the system is idle(ish) or a little time has passed (this is to allow
> > aggregation of multiple screen paints into a single transmission),
> > ChromiVNC scans the physical screen in the areas marked "modified" and
> > eliminates areas where the screen actually hasn't changed. It then
> > generates update rectangles from the reduced "modified bitmap", determines
> > the best compression method for each, and transmits them. At present I'm
> > trying to think up better ways of doing this to reduce bandwidth and/or CPU
> > consumption, or to trade one against the other.
> >
> > All of the above is done in software, but consumes little enough CPU that
> > all Macs with accelerated video have powerful enough CPUs not to benefit
> > significantly from any hardware acceleration of the differencing process.
> > Even on an ancient 68040-based machine, the performance is still reasonably
> > comparable to, say, Xvnc on a 486 (ie. not good but tolerable). The
> > situation may well be different with PCs, where video acceleration was
> > introduced earlier and CPUs are (for general purposes) slightly less
> > powerful. However, the extra complexity and hardware-dependence might not
> > be a good thing.
> >
> > Going back to XOR, it is still a good optimisation to trim off large
> > "blank" areas of non-changed screen for several reasons. Firstly, the
> > client has to allocate memory for and process a large screen area, if this
> > is routinely left in (consider a 1024x768 screen where only a single
> > DOS-box character has changed). Also, HexTile is actually not very
> > efficient at encoding large blank areas - it must generate at least one
> > byte for every 16x16 tile which is sent. RRE or CoRRE are much better for
> > this, but rapidly fall behind HexTile as the number of subrects increases
> > relative to the size of the update. Even the Zlib-based encoders probably
> > have *some* overhead for large blank spaces, especially if CPU utilisation
> > is taken into account.
> >
> > - --------------------------------------------------------------
> > from: Jonathan "Chromatix" Morton
> > mail: [EMAIL PROTECTED] (not for attachments)
> > big-mail: [EMAIL PROTECTED]
> > uni-mail: [EMAIL PROTECTED]
> >
> > The key to knowledge is not to rely on people to teach you it.
> >
> > Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
> >
> > - -----BEGIN GEEK CODE BLOCK-----
> > Version 3.12
> > GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
> > PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
> > - -----END GEEK CODE BLOCK-----
> >
> > ------------------------------
> >
> > End of vnc-list-digest V1 #1068
> > *******************************
> >
> > To stop receiving this digest, mail [EMAIL PROTECTED]
> > with the line 'unsubscribe vnc-list-digest' in the message BODY
> > See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
> To unsubscribe, send a message with the line: unsubscribe vnc-list
> to [EMAIL PROTECTED]
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
