vnc-list-request,Dz:C#!
======= 2005-12-24 20:00:01 [EMAIL PROTECTED]@#:=======
>Send VNC-List mailing list submissions to
> [email protected]
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://www.realvnc.com/mailman/listinfo/vnc-list
>or, via email, send a message with subject or body 'help' to
> [EMAIL PROTECTED]
>
>You can reach the person managing the list at
> [EMAIL PROTECTED]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of VNC-List digest..."
>
>
>Today's Topics:
>
> 1. Re: Stopping RealVNC (William Hooper)
> 2. RE: vnc proxy (Luptak, Miroslav)
> 3. Re: Stopping RealVNC (Hal Vaughan)
> 4. Re: Stopping RealVNC (Hal Vaughan)
> 5. Re: vnc proxy (Mark Ceulemans)
> 6. RE: Connection problem (John Aldrich)
> 7. RE: Cant Connect (John Aldrich)
> 8. RE: Stopping RealVNC (John Aldrich)
> 9. Re: Stopping RealVNC (Hal Vaughan)
> 10. AllowShutdown registry key in WinVNC v4 & 4.1.1 (Raper, Jonathan)
> 11. General configuration (Mickey Shekdar)
> 12. RE: vnc proxy (Luptak, Miroslav)
> 13. AllowShutdown registry key in WinVNC v4 & 4.1.1 (Raper, Jonathan)
> 14. RE: AllowShutdown registry key in WinVNC v4 & 4.1.1 (Raper, Jonathan)
> 15. xterm is not running ([EMAIL PROTECTED])
> 16. 2 dsl connections one problem! ([EMAIL PROTECTED])
>
>--__--__--
>
>Message: 1
>Date: Fri, 23 Dec 2005 08:14:25 -0500 (EST)
>Subject: Re: Stopping RealVNC
>From: "William Hooper" <[EMAIL PROTECTED]>
>To: [email protected]
>
>Hal Vaughan wrote:
>
>> Is it possible to stop a RealVNC server on Linux from the command line,
>> or any other way without "kill -9 $(pidof vncserver)" ?
>
>man vncserver
>"-kill :display#
> This kills a VNC desktop previously started with vncserver."
>
>> And is it
>> possible to stop a running server on Windows from the console as well?
>
>winvnc4 --help
>" -stop - Stop the WinVNC server system service."
>
>--
>William Hooper
>
>--__--__--
>
>Message: 2
>Subject: RE: vnc proxy
>Date: Fri, 23 Dec 2005 14:31:48 +0100
>From: "Luptak, Miroslav" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>, <[email protected]>
>
>Hello, Mark.
>
>You don't need a special VNC proxy. Any TCP forwarder will do, try
>rinetd from http://www.boutell.com/rinetd.
>
>Here is how it could work:
>
>1. let's suppose this:
> - Nic1 on the Windows Server is 192.168.1.1
> - vncviewer will be running on a host on the {company network}
> - you want to open a VNC session to a server on the {local network}
> with IP 10.10.10.10 and VNC Server running on the default port
>
>2. on the Windws Server, create rinetd.ini containing the following
>line:
>192.168.1.1 5901 10.10.10.10 5900
>
>3. on the Windows server execute "rinetd.exe -c rinetd.ini"
>
>4. on any machine on the {company network}, execute "vncviewer
>192.168.1.1:1".
> This will connect you to the VNC Server on machine 10.10.10.10 on
>the
> {local network}
>
>Best regards,
>
>Miro
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Mark Ceulemans
>> Sent: Friday, December 23, 2005 09:07
>> To: [email protected]
>> Subject: vnc proxy
>>
>> Hi All,
>> I am trying to setup a rather complex environment.
>> { company network }<-> tcpip< -> ( Nic1 Windows
>> Server Nic2) <->
>> tcpip <-> { local network }
>> The server in the middle has 2 network cards (with no
>> routing). The
>> local network is in a local tcpip range (f.e. 10.x addresses).
>> Now, I want from within the company network to open a
>> session to a
>> machine in the local network.
>> Can this be done?
>> Is there f.e. a vnc proxy that can reroute the vnc
>> request from a
>> server within the company network to a machine in the
>> local network?
>> Any help will be greatly appreciated.
>> Cheers,
>> --
>> Kind regards,
>> Mark Ceulemans
>> _______________________________________________
>> VNC-List mailing list
>> [email protected]
>> To remove yourself from the list visit:
>> http://www.realvnc.com/mailman/listinfo/vnc-list
>
>--__--__--
>
>Message: 3
>From: Hal Vaughan <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>Organization: Threshold Digital, Ltd.
>To: [email protected]
>Subject: Re: Stopping RealVNC
>Date: Fri, 23 Dec 2005 09:38:36 -0500
>
>On Friday 23 December 2005 08:14 am, William Hooper wrote:
>> Hal Vaughan wrote:
>> > Is it possible to stop a RealVNC server on Linux from the command line,
>> > or any other way without "kill -9 $(pidof vncserver)" ?
>>
>> man vncserver
>> "-kill :display#
>> This kills a VNC desktop previously started with vncserver."
>
>Odd. I *know* I checked the man page on this and never found it. I have no
>idea why. (Maybe it's the result of trying to figure this out at 3 am?)
>
>> > And is it
>> > possible to stop a running server on Windows from the console as well?
>>
>> winvnc4 --help
>> " -stop - Stop the WinVNC server system
>> service."
>
>But doesn't that refer to VNC as a service, not as a program? I want to be
>clear about this because some of the people I'm working with do not want VNC
>as a service or starting every time they boot. It should only start when it
>is run and never be seen as a service. (It's been a long time since I've
>worked much on Windows, but if I remember and understand, a service would be
>started and stopped at boot or logon and controlled by Windows, as opposed to
>the program being started and stopped solely by the user.)
>
>Hal
>
>--__--__--
>
>Message: 4
>From: Hal Vaughan <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>Organization: Threshold Digital, Ltd.
>To: [email protected]
>Subject: Re: Stopping RealVNC
>Date: Fri, 23 Dec 2005 09:56:09 -0500
>
>On Friday 23 December 2005 08:14 am, William Hooper wrote:
>> Hal Vaughan wrote:
>> > Is it possible to stop a RealVNC server on Linux from the command line,
>> > or any other way without "kill -9 $(pidof vncserver)" ?
>>
>> man vncserver
>> "-kill :display#
>> This kills a VNC desktop previously started with vncserver."
>
>I see what happened. When I first was asking about VNC, on the tightVNC list,
>that is when someone told me to try RealVNC. In the same post, he said to
>use vncconfig to communicate with the existing server, so I got it in my head
>that all commands for the server go through vncconfig -- and was looking
>there. I tried it, and it works fine. There's a good chance, when I set
>this up, that I'll make sure I'm always using a higher number display most
>people won't use, so I can be sure to start and stop the same server each
>time.
>
>> > And is it
>> > possible to stop a running server on Windows from the console as well?
>>
>> winvnc4 --help
>> " -stop - Stop the WinVNC server system
>> service."
>
>Tried this. It does seem to work only with a service, and has no effect on a
>running server if it isn't setup through Windows to run as a service.
>
>I'm still looking it all over.
>
>Hal
>
>--__--__--
>
>Message: 5
>Date: Fri, 23 Dec 2005 16:00:30 +0100
>From: Mark Ceulemans <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: "Luptak, Miroslav" <[EMAIL PROTECTED]>
>Cc: [email protected]
>Subject: Re: vnc proxy
>
>Wow, thanks.
>The problem is that there are many machines in the second cloud, and
>this means opening a port for every single machine in this cloud.
>
>I also found a simple workaround.
>
>1. On the central machine, install FreeProxy (a simple HTML proxy
>server), and have it reroute requests from NIC1 to machines in the local
>network
>
>2. on your local desktop, install ProxySwitcher (a proxy switching
>tool), and define a proxy for the central machine.
>
>3. From your browser, connect to the ipaddress in the local subnet, and
>this request will be routed via the central machine to the manager.
>(connect to the port 5800).
>
>This works fine (as far as I can see)
>
>Thanks for your support,
>
>Cheers,
>
>I also
>Luptak, Miroslav wrote:
>
>>Hello, Mark.
>>
>>You don't need a special VNC proxy. Any TCP forwarder will do, try
>>rinetd from http://www.boutell.com/rinetd.
>>
>>Here is how it could work:
>>
>>1. let's suppose this:
>> - Nic1 on the Windows Server is 192.168.1.1
>> - vncviewer will be running on a host on the {company network}
>> - you want to open a VNC session to a server on the {local network}
>> with IP 10.10.10.10 and VNC Server running on the default port
>>
>>2. on the Windws Server, create rinetd.ini containing the following
>>line:
>>192.168.1.1 5901 10.10.10.10 5900
>>
>>3. on the Windows server execute "rinetd.exe -c rinetd.ini"
>>
>>4. on any machine on the {company network}, execute "vncviewer
>>192.168.1.1:1".
>> This will connect you to the VNC Server on machine 10.10.10.10 on
>>the
>> {local network}
>>
>>Best regards,
>>
>>Miro
>>
>>
>>
>>>-----Original Message-----
>>>From: [EMAIL PROTECTED]
>>>[mailto:[EMAIL PROTECTED] On Behalf Of Mark Ceulemans
>>>Sent: Friday, December 23, 2005 09:07
>>>To: [email protected]
>>>Subject: vnc proxy
>>>
>>> Hi All,
>>> I am trying to setup a rather complex environment.
>>> { company network }<-> tcpip< -> ( Nic1 Windows
>>>Server Nic2) <->
>>> tcpip <-> { local network }
>>> The server in the middle has 2 network cards (with no
>>>routing). The
>>> local network is in a local tcpip range (f.e. 10.x addresses).
>>> Now, I want from within the company network to open a
>>>session to a
>>> machine in the local network.
>>> Can this be done?
>>> Is there f.e. a vnc proxy that can reroute the vnc
>>>request from a
>>> server within the company network to a machine in the
>>>local network?
>>> Any help will be greatly appreciated.
>>> Cheers,
>>> --
>>>Kind regards,
>>>Mark Ceulemans
>>>_______________________________________________
>>>VNC-List mailing list
>>>[email protected]
>>>To remove yourself from the list visit:
>>>http://www.realvnc.com/mailman/listinfo/vnc-list
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>--
>Kind regards,
>Mark Ceulemans
>
>--__--__--
>
>Message: 6
>From: John Aldrich <[EMAIL PROTECTED]>
>To: "'Patrick Stoddart'" <[EMAIL PROTECTED]>, [email protected]
>Subject: RE: Connection problem
>Date: Fri, 23 Dec 2005 10:27:06 -0500
>
>Is your IP address 192.168.1.64? If so, that's not a routeable IP address.
>You'll need to find out what your "real" IP address is, by visiting
>http://www.gotomyvnc.com or http://www.whatismyip.com or
>http://www.showmyip.com, etc. Then you should be able to connect over the
>internet, provided you've taken care of forwarding the ports in your router
>and/or opening the appropriate ports in your firewall software (if any.)
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Behalf Of Patrick Stoddart
>Sent: Thursday, December 22, 2005 8:51 PM
>To: [email protected]
>Subject: Connection problem
>
>
>When I open the VNC Viewer and type in the address that I want to connect to
>(***.168.1.64:0), and click OK, it says that it is attempting to connect to
>the server and then says that connection failed (timed out). I have also
>tried doing this through my browser by typing in http://***.168.1.64:5800/
>and I get the Java applet but again it times out. I would like to connect to
>my computer remotely, and this is starting to get frustrating. Both of my
>computers (server and viewer) run on DSL or Broadband and are both connected
>now. I am running Windows XP Home SP2 on both computers, and any assistance
>would be greatly appreciated. Thank You.
> PS - the *** that I put in in the connection addresses replaces the actual
>first 3 digits of the VNC Server address; NOT my IP address.
>_______________________________________________
>VNC-List mailing list
>[email protected]
>To remove yourself from the list visit:
>http://www.realvnc.com/mailman/listinfo/vnc-list
>
>--__--__--
>
>Message: 7
>From: John Aldrich <[EMAIL PROTECTED]>
>To: "'Kristine Keller'" <[EMAIL PROTECTED]>, [email protected]
>Subject: RE: Cant Connect
>Date: Fri, 23 Dec 2005 10:28:57 -0500
>
>http://www.portforward.com is your friend. They may have instructions there
>for your specific router, or one very similar. You should NOT need to use
>port "triggering" just port-forwarding. I used to use a Linksys router
>(until it died) and I was able to access my PC at home from remote no
>problems.
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Behalf Of Kristine Keller
>Sent: Friday, December 23, 2005 12:55 AM
>To: [email protected]
>Subject: Cant Connect
>
>
>I have a Linksys router and I cant connect i have tried everything. Called
>linksys and they tried all. I disabled my firewall that didnt help.
>Running xp on all computers that i am trying to connect with?
>
>Help please
>
>[demime 1.01d removed an attachment of type image/gif which had a name of
>IMSTP.gif]
>
>[demime 1.01d removed an attachment of type Image/gif which had a name of
>BackGrnd.gif]
>_______________________________________________
>VNC-List mailing list
>[email protected]
>To remove yourself from the list visit:
>http://www.realvnc.com/mailman/listinfo/vnc-list
>
>--__--__--
>
>Message: 8
>From: John Aldrich <[EMAIL PROTECTED]>
>To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>,
> [email protected]
>Subject: RE: Stopping RealVNC
>Date: Fri, 23 Dec 2005 10:31:06 -0500
>
>Under linux, it should be as simple as "vncserver -kill <display>" Under
>Windows NT, 2000 or XP, I do not know of any way to stop a server from the
>command-line only. I'm sure there's a way, but I don't know what it is,
>never having looked into it.
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Behalf Of Hal Vaughan
>Sent: Friday, December 23, 2005 3:17 AM
>To: [email protected]
>Subject: Stopping RealVNC
>
>
>I've asked this before, but never got an answer.
>
>I know that on Linux that once a RealVNC server is running, I can
>communicate
>with it with vncconfig. It seems that on Windows, I can communicate with the
>
>running RealVNC server with winvnc4.exe (like telling it to connect with a
>listening system).
>
>What I have not found is a way to get a RealVNC server, on Linux or Windows,
>
>to exit without killing the process. On Windows it is possible to do it by
>right clicking on the icon, but neither seems easily stopped from the
>console. In Linux this is important because each time the server is run and
>
>killed, the user has to delete lock files to avoid problems with which
>display the server is running.
>
>Is it possible to stop a RealVNC server on Linux from the command line, or
>any
>other way without "kill -9 $(pidof vncserver)" ? And is it possible to stop
>
>a running server on Windows from the console as well?
>
>Thank you for any help on this!
>
>Hal
>_______________________________________________
>VNC-List mailing list
>[email protected]
>To remove yourself from the list visit:
>http://www.realvnc.com/mailman/listinfo/vnc-list
>
>--__--__--
>
>Message: 9
>From: Hal Vaughan <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>Organization: Threshold Digital, Ltd.
>To: [email protected]
>Subject: Re: Stopping RealVNC
>Date: Fri, 23 Dec 2005 12:06:36 -0500
>
>On Friday 23 December 2005 10:31 am, John Aldrich wrote:
>> Under linux, it should be as simple as "vncserver -kill <display>" Under
>> Windows NT, 2000 or XP, I do not know of any way to stop a server from the
>> command-line only. I'm sure there's a way, but I don't know what it is,
>> never having looked into it.
>
>As mentioned in another thread, I tried winvnc4 -stop, but that only stops the
>service. Part of my concern here is that I don't want to start a server with
>another running, and another part is I'd like to make sure the one that gets
>started to connect to me is stopped -- without depending on the user to
>remember to close it.
>
>Hal
>
>--__--__--
>
>Message: 10
>Subject: AllowShutdown registry key in WinVNC v4 & 4.1.1
>Date: Fri, 23 Dec 2005 12:35:48 -0500
>From: "Raper, Jonathan" <[EMAIL PROTECTED]>
>To: <[email protected]>
>
>I'm a system admin for a medium-sized healthcare organization. I am
>considering upgrading my systems from VNC 3.3.7 to the current version
>4.1.1. Upon testing the import of my existing registry settings, I got
>the notification that AllowShutdown is no longer supported. Is there not
>any way to be able to prevent the users from shutting down VNC in the
>new version? Why was this taken away?
>
>Thanks,
>
>Jonathan
>
>WARNING: Any medical information contained in this electronic message is
>CONFIDENTIAL and privileged. It is unlawful for unauthorized persons to view,
>copy, disclose, or disseminate CONFIDENTIAL information. This electronic
>message may contain information that is confidential and/or legally
>privileged. It is intended only for the use of the individual(s) and/or entity
>named as recipients in the message. If you are not an intended recipient of
>this message, please notify the sender immediately and delete this material
>from your computer. Do not deliver, distribute or copy this message, and do
>not disclose its contents or take any action in reliance on the information
>that it contains.
>
>--__--__--
>
>Message: 11
>Reply-To: <[EMAIL PROTECTED]>
>From: "Mickey Shekdar" <[EMAIL PROTECTED]>
>To: <[email protected]>
>Subject: General configuration
>Date: Fri, 23 Dec 2005 14:33:28 -0500
>Organization: CatPlus, Inc.
>
>I was referred to RealVNC by a friend who is using TightVNC and will be
>buying Enterprise Edition
>
>
>
>My questions are:
>
>
>
>Question 1: Is the Port TCP or UDP
>
>Question 2: Is the port number 5800 or 5900
>
>Question 3: Will I make a connection if host's OS is MS Windows XP
>Professional and is stand alone plugged directly to the DSL modem?
>
>Question 4: How do I open port TCP 5800 or TCP 5900 or UDP 5800 or UDP 5900
>on my system?
>
>Question 5: Can I just enter public IP, for example 69.22.199.076:5800 in
>the viewer to connect
>
>
>
>Thanks for your help
>
>
>
>Mickey
>
>--__--__--
>
>Message: 12
>Subject: RE: vnc proxy
>Date: Fri, 23 Dec 2005 21:27:54 +0100
>From: "Luptak, Miroslav" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Cc: <[email protected]>
>
>Hello, Mark.
>
>The idea is great! However, I am surprised it works if the central
>machine really does not route.
>
>I thought that the browser would only download the java vncviewer from
>port 5800, and then the java vncviewer connects directly to port 5900 on
>the VNC server.
>
>Wez @ RealVNC, isn't java vncviewer working this way? Is it connecting
>to the VNC Server directly or via the http proxy?
>
>Mark, are you sure the central machine does not route? On your local
>desktop on the company network, try to telnet to port 5900 on a VNC
>server on the local network to see whether you don't get a response.
>
>Merry Christmas and Happy New Year,
>
>Miro
>
>> -----Original Message-----
>> From: Mark Ceulemans [mailto:[EMAIL PROTECTED]
>> Sent: Friday, December 23, 2005 16:01
>> To: Luptak, Miroslav
>> Cc: [email protected]
>> Subject: Re: vnc proxy
>>
>> Wow, thanks.
>> The problem is that there are many machines in the second cloud, and
>> this means opening a port for every single machine in this cloud.
>>
>> I also found a simple workaround.
>>
>> 1. On the central machine, install FreeProxy (a simple HTML proxy
>> server), and have it reroute requests from NIC1 to machines
>> in the local
>> network
>>
>> 2. on your local desktop, install ProxySwitcher (a proxy switching
>> tool), and define a proxy for the central machine.
>>
>> 3. From your browser, connect to the ipaddress in the local
>> subnet, and
>> this request will be routed via the central machine to the manager.
>> (connect to the port 5800).
>>
>> This works fine (as far as I can see)
>>
>> Thanks for your support,
>>
>> Cheers,
>>
>> I also
>> Luptak, Miroslav wrote:
>>
>> >Hello, Mark.
>> >
>> >You don't need a special VNC proxy. Any TCP forwarder will do, try
>> >rinetd from http://www.boutell.com/rinetd.
>> >
>> >Here is how it could work:
>> >
>> >1. let's suppose this:
>> > - Nic1 on the Windows Server is 192.168.1.1
>> > - vncviewer will be running on a host on the {company network}
>> > - you want to open a VNC session to a server on the
>> {local network}
>> > with IP 10.10.10.10 and VNC Server running on the default port
>> >
>> >2. on the Windws Server, create rinetd.ini containing the following
>> >line:
>> >192.168.1.1 5901 10.10.10.10 5900
>> >
>> >3. on the Windows server execute "rinetd.exe -c rinetd.ini"
>> >
>> >4. on any machine on the {company network}, execute "vncviewer
>> >192.168.1.1:1".
>> > This will connect you to the VNC Server on machine 10.10.10.10 on
>> >the
>> > {local network}
>> >
>> >Best regards,
>> >
>> >Miro
>> >
>> >
>> >
>> >>-----Original Message-----
>> >>From: [EMAIL PROTECTED]
>> >>[mailto:[EMAIL PROTECTED] On Behalf Of Mark Ceulemans
>> >>Sent: Friday, December 23, 2005 09:07
>> >>To: [email protected]
>> >>Subject: vnc proxy
>> >>
>> >> Hi All,
>> >> I am trying to setup a rather complex environment.
>> >> { company network }<-> tcpip< -> ( Nic1 Windows
>> >>Server Nic2) <->
>> >> tcpip <-> { local network }
>> >> The server in the middle has 2 network cards (with no
>> >>routing). The
>> >> local network is in a local tcpip range (f.e. 10.x addresses).
>> >> Now, I want from within the company network to open a
>> >>session to a
>> >> machine in the local network.
>> >> Can this be done?
>> >> Is there f.e. a vnc proxy that can reroute the vnc
>> >>request from a
>> >> server within the company network to a machine in the
>> >>local network?
>> >> Any help will be greatly appreciated.
>> >> Cheers,
>> >> --
>> >>Kind regards,
>> >>Mark Ceulemans
>> >>_______________________________________________
>> >>VNC-List mailing list
>> >>[email protected]
>> >>To remove yourself from the list visit:
>> >>http://www.realvnc.com/mailman/listinfo/vnc-list
>> >>
>> >>
>> >>
>> >
>> >
>> >
>> >
>>
>>
>> --
>> Kind regards,
>> Mark Ceulemans
>
>--__--__--
>
>Message: 13
>Subject: AllowShutdown registry key in WinVNC v4 & 4.1.1
>Date: Fri, 23 Dec 2005 17:37:59 -0500
>From: "Raper, Jonathan" <[EMAIL PROTECTED]>
>To: <[email protected]>
>
>Well, after a little more digging, it turns out that the AllowShutdown
>key was replaced by the DisableClose key. both do the same thing: grey
>out the Close option from the icon on the system tray, it just depends
>on whether you're running version 3.3.x or 4.x as to which key you use!
>
>Now, here's the next part of the question:
>
>Under VNC version 3.3.x, you could have different settings depending on
>who was logged in via the registry keys:
>
>Windows Registry Editor Version 5.00
>
>[HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3]
>
>[HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Administrator]
>"SocketConnect"=dword:00000001
>"AutoPortSelect"=dword:00000001
>"InputsEnabled"=dword:00000001
>"LocalInputsDisabled"=dword:00000000
>"IdleTimeout"=dword:00000000
>"QuerySetting"=dword:00000002
>"QueryTimeout"=dword:0000000a
>"Password"=hex:e4,d2,00,e3,g2,0a,39,0e
>"PollUnderCursor"=dword:00000000
>"PollForeground"=dword:00000001
>"PollFullScreen"=dword:00000001
>"OnlyPollConsole"=dword:00000001
>"OnlyPollOnEvent"=dword:00000000
>"AllowProperties"=dword:00000001
>"AllowShutdown"=dword:00000001
>
>[HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default]
>"SocketConnect"=dword:00000001
>"AutoPortSelect"=dword:00000001
>"InputsEnabled"=dword:00000001
>"LocalInputsDisabled"=dword:00000000
>"IdleTimeout"=dword:00000000
>"QuerySetting"=dword:00000002
>"QueryTimeout"=dword:0000000a
>"Password"=hex:e4,d2,00,e3,g2,0a,39,0e
>"PollUnderCursor"=dword:00000000
>"PollForeground"=dword:00000001
>"PollFullScreen"=dword:00000001
>"OnlyPollConsole"=dword:00000001
>"OnlyPollOnEvent"=dword:00000000
>"AllowProperties"=dword:00000000
>"AllowShutdown"=dword:00000000
>
>[HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\esmith]
>"SocketConnect"=dword:00000001
>"AutoPortSelect"=dword:00000001
>"InputsEnabled"=dword:00000001
>"LocalInputsDisabled"=dword:00000000
>"IdleTimeout"=dword:00000000
>"QuerySetting"=dword:00000002
>"QueryTimeout"=dword:0000000a
>"Password"=hex:e4,d2,00,e3,g2,0a,39,0e
>"PollUnderCursor"=dword:00000000
>"PollForeground"=dword:00000001
>"PollFullScreen"=dword:00000001
>"OnlyPollConsole"=dword:00000001
>"OnlyPollOnEvent"=dword:00000000
>"AllowProperties"=dword:00000001
>"AllowShutdown"=dword:00000001
>
>In the above example, the anyone logged in other than esmith or
>administrator, would have the settings that appear under the Default
>key. In this particular case, esmith and administrator both can view the
>VNC properties page as well as shutdown the client, but the average user
>would not be able to. Is there any way to do this under version 4?
>
>Thanks,
>
>Jonathan L. Raper, A+, MCSA, MCSE
>Technology Coordinator
>Eagle Physicians & Associates, PA
>[EMAIL PROTECTED]
>
>
>_____________________________________________
>From: Raper, Jonathan
>Sent: Friday, December 23, 2005 12:36 PM
>To: '[email protected]'
>Subject: AllowShutdown registry key in WinVNC v4 & 4.1.1
>
>I'm a system admin for a medium-sized healthcare organization. I am
>considering upgrading my systems from VNC 3.3.7 to the current version
>4.1.1. Upon testing the import of my existing registry settings, I got
>the notification that AllowShutdown is no longer supported. Is there not
>any way to be able to prevent the users from shutting down VNC in the
>new version? Why was this taken away?
>
>Thanks,
>
>Jonathan
>
>WARNING: Any medical information contained in this electronic message is
>CONFIDENTIAL and privileged. It is unlawful for unauthorized persons to view,
>copy, disclose, or disseminate CONFIDENTIAL information. This electronic
>message may contain information that is confidential and/or legally
>privileged. It is intended only for the use of the individual(s) and/or entity
>named as recipients in the message. If you are not an intended recipient of
>this message, please notify the sender immediately and delete this material
>from your computer. Do not deliver, distribute or copy this message, and do
>not disclose its contents or take any action in reliance on the information
>that it contains.
>
>--__--__--
>
>Message: 14
>Subject: RE: AllowShutdown registry key in WinVNC v4 & 4.1.1
>Date: Fri, 23 Dec 2005 17:41:10 -0500
>From: "Raper, Jonathan" <[EMAIL PROTECTED]>
>To: <[email protected]>
>
> test
>
>WARNING: Any medical information contained in this electronic message is
>CONFIDENTIAL and privileged. It is unlawful for unauthorized persons to view,
>copy, disclose, or disseminate CONFIDENTIAL information. This electronic
>message may contain information that is confidential and/or legally
>privileged. It is intended only for the use of the individual(s) and/or entity
>named as recipients in the message. If you are not an intended recipient of
>this message, please notify the sender immediately and delete this material
>from your computer. Do not deliver, distribute or copy this message, and do
>not disclose its contents or take any action in reliance on the information
>that it contains.
>
>--__--__--
>
>Message: 15
>Date: Sat, 24 Dec 2005 01:11:09 +0100
>From: [EMAIL PROTECTED]
>To: [email protected]
>Subject: xterm is not running
>
>Dear all VNC users,
>
>I have VNC server installed on Solaris 9 and Viewer on Windows XP. Everything
>works fine except of xterm. in the <display>.log file a line appears telling
>that "Could not find font path element /usr/openwin/lib/fonts/CID/, removing
>from list!
>xterm: unable to locate a suitable font".
>
>When I check processes running then xterm does not appear on the list. The
>directory /usr/openwin/lib/fonts/CID/ does not exists in the system, so that I
>suspect it causes the problem.
>
>When I put into xstartup lines launching other graphical applications, for
>example xclock, then they appear correctly in the viewer.
>
>Any hints how to workaround this problem will be greatly appreciated.
>
>Regards,
>Greg
>
>--__--__--
>
>Message: 16
>Date: Fri, 23 Dec 2005 16:16:58 -0800 (PST)
>Subject: 2 dsl connections one problem!
>From: [EMAIL PROTECTED]
>To: [email protected]
>
>my office has two dsl connections. i want to set up one computer on dsl A
>as the vnc server. since the company is using dsl B, what is the proper
>ip address to be able to control the one server on the other connection?
>I tried entering the local IP (obviously didn't work) and the external IP.
>
>It's probably a simple answer but I can't figure it out. Connection A is a
>static IP and connected to a netgear router if this info helps.
>
>
>--__--__--
>
>_______________________________________________
>
>
>VNC-List mailing list
>
>
>[email protected]
>
>
>http://www.realvnc.com/mailman/listinfo/vnc-list
>
>
>
>
>End of VNC-List Digest
= = = = = = = = = = = = = = = = = = = =
!!!!!!!!!!!!!!!!VB
@q#!
!!!!!!!!!!!!!!!!lipinsheng
[EMAIL PROTECTED]
!!!!!!!!!!!!!!!!!!!!2005-12-26
[demime 1.01d removed an attachment of type image/gif which had a name of
face-1.gif]
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
