vnc-list-digest V1 #1422

Gale, Bill bgale "at" chi.navtech.com
Thu, 24 Jan 2002 22:44:53 +0000


Hi,
I was thinking how nice it would be if the digest could be distributed
in HTML format, with hyperlinks for navigation.  For example, there could
be hyperlinks from each entry in the table of contents to each article.
After each article could be links for TOC, Previous, and Next articles.
Anything sound interesting or possible?  I'm sure there is some sort
of list server software for this, it seems like a natural.
Regards,
Bill Gale


-----Original Message-----
From: owner-vnc-list-digest "at" uk.research.att.com
[mailto:owner-vnc-list-digest "at" uk.research.att.com]
Sent: Thursday, January 24, 2002 4:20 PM
To: vnc-list-digest "at" uk.research.att.com
Subject: vnc-list-digest V1 #1422



vnc-list-digest      Thursday, January 24 2002      Volume 01 : Number 1422



............................
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:

	AW: many connections modifications
	Re: starting the vncserver - be kind, i've read the FAQs
	Re: SUMMARY - starting the vncserver - found a perl book!!
	Re:  VNC dies and requires reconnection every few minutes (Win NT -
AT T Extranet - Cable Modem)
	AW: Make an VNC-Connection visible
	RE: DOS VNC
	Re:  MTU
	Re: ConnectPriority - Registry info
	MAC PPC Server
	Shift Key problems with VNC
	RE: MTU - VNC dies and requires reconnection every few minutes (W in
NT - AT T Extranet - Cable Modem)
	Re: ConnectPriority - Registry info
	RE: ConnectPriority - Registry info
	Re: ConnectPriority - Registry info
	RE: ConnectPriority - Registry info
	RE: SUMMARY - starting the vncserver - found a perl book!!
	Re: java.net.socketException:  SocketThread Failed
	Connection refused
	RE: Shift Key problems with VNC
	Re: SUMMARY - starting the vncserver - found a perl book!!
	Re: DOS VNC
	Re: DOS VNC
	Re: java.net.socketException:  SocketThread Failed
	Re: Connection refused
	Re: Connection refused
	Re: Re: Tight 1.2.2: big slowdown?
	Re: DOS VNC
	RE: MTU - VNC dies and requires reconnection every few minutes (W in
NT - AT T Extranet - Cable Modem)
	winvnc w/xp and mult users
	Re: winvnc w/xp and mult users
	Connection closed
	Re: Tools like VNC Commander 
............................

----------------------------------------------------------------------

Date: Thu, 24 Jan 2002 08:27:41 +0100
From: =?iso-8859-1?Q?Claus_M=FCller?= <cm "at" m-b-soft.de>
Subject: AW: many connections modifications

Hello,

the problem is, that VNC uses ports 5800 - 5899 for the java-client
and ports 5900 - 5999 for the normal client.
to make more connections then 100 the sources must be changed to use
other and more ports.

Cheers,
Claus M|ller

MB-Software
e-mail: m-soft.de
internet: www.m-b-soft.de

- -----Urspr|ngliche Nachricht-----
Von: owner-vnc-list "at" uk.research.att.com
[mailto:owner-vnc-list "at" uk.research.att.com]Im Auftrag von Lonnie
Cumberland
Gesendet: Dienstag, 22. Januar 2002 18:26
An: vnc-list "at" uk.research.att.com
Cc: Shashi.Sharma "at" brooks.com
Betreff: RE: many connections modifications


Hello Sharma,

Actually I was talking about Xvnc when I run it as a daemon in my
xinetd.

I seem to remember that someone wanted to be able to make somewhere
around 500 - 1000 connections and there was the question of how Xvnc
could handle the ports as the usual setting was to put it on port
5900.

Cheers,
Lonnie



> I am not aware if there are any restriction on the number of
> connection in the code. Are you talking about WinVNC or Xvnc ?
> Thanks
> -shashi
>
> -----Original Message-----
> From: Lonnie Cumberland [mailto:lonnie "at" outstep.com]
> Sent: Tuesday, January 22, 2002 7:06 AM
> To: vnc-list "at" uk.research.att.com
> Subject: many connections modifications
>
>
> Hello All,
>
> I seem to remember someone asking about being able to make many
> connections (on the order of 100 or more) to a server through VNC
> and was wondering what modifications I needed to make to the
> sources to handle this?
>
> Any help would be greatly appreciated.
> Cheers,
> Lonnie Cumberland
> OutStep Technologies Incorporated
> (313) 832-7366
>
> URL: http://www.outstep.com
> EMAIL: Lonnie "at" OutStep.com
>      : Lonnie_Cumberland "at" yahoo.com
> --------------------------------------------------------------------
- -
> To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
> 'unsubscribe vnc-list' in the message BODY
> See also: http://www.uk.research.att.com/vnc/intouch.html
> --------------------------------------------------------------------
- -
> --------------------------------------------------------------------
- -
> To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
> 'unsubscribe vnc-list' in the message BODY
> See also: http://www.uk.research.att.com/vnc/intouch.html
> --------------------------------------------------------------------
- -


- --
 Lonnie Cumberland
 OutStep Technologies Incorporated
 (313) 832-7366

 URL: http://www.outstep.com
 EMAIL: Lonnie "at" OutStep.com
      : Lonnie_Cumberland "at" yahoo.com


- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 10:00:01 +0000
From: Illtud Daniel <illtud.daniel "at" llgc.org.uk>
Subject: Re: starting the vncserver - be kind, i've read the FAQs

Thanks for reading the FAQs first!

Bobby Ramirez wrote:
> 
> # ./vncserver :13 -pn -localhost
> vncserver: couldn't find "xauth" on your PATH.

> Shouldn't "$ENV{HOME}/ be looking in / (root) for .Xauthority?
> I don't know Perl, so I don't understand the systax.

...but it's 'xauth' it can't find, not .Xauthority. xauth is a
program to manipulate the .Xauthority file.

I've no idea about Solaris 8, but on our Solaris 6 boxen, xauth
lives in /usr/X/bin. This needs to be added to root's PATH.
Or that's my best guess, anyway.

- -- 
Illtud Daniel                                 illtud.daniel "at" llgc.org.uk
Uwch Ddadansoddwr Systemau                       Senior Systems Analyst
Llyfrgell Genedlaethol Cymru                  National Library of Wales
Yn siarad drosof fy hun, nid LlGC   -  Speaking personally, not for NLW

------------------------------

Date: Thu, 24 Jan 2002 10:00:58 +0000
From: Illtud Daniel <illtud.daniel "at" llgc.org.uk>
Subject: Re: SUMMARY - starting the vncserver - found a perl book!!

Bobby Ramirez wrote:
> 
> i just added /usr/openwin/bin to my path, and the system
> function could then find the xauth command.

Ooops, didn't see this follow-up. Glad you got it working,
ignore my post!

- -- 
Illtud Daniel                                 illtud.daniel "at" llgc.org.uk
Uwch Ddadansoddwr Systemau                       Senior Systems Analyst
Llyfrgell Genedlaethol Cymru                  National Library of Wales
Yn siarad drosof fy hun, nid LlGC   -  Speaking personally, not for NLW

------------------------------

Date: Thu, 24 Jan 2002 22:35:20 +1100
From: Chris Jaecker <cjaecker "at" illustratednetworks.com>
Subject: Re:  VNC dies and requires reconnection every few minutes (Win NT -
AT T Extranet - Cable Modem)

A shot in the dark here, but it may be that you've got an MTU problem.

Both your client and server are connected to Ethernet so they're assuming 
1500 bytes of payload in the frame. But, you're going through some kind of 
security filter, which may be adding bytes to each packet.

If the packets are leaving as 1500 and the security process adds say 60 
bytes, then the payload is too large for the frame, so it get's fragmented, 
doubling the number of packets and putting the overhead of packet 
reassembly onto the client, and creating a congestive collapse at layer 3 
(because tcp will order a retransmit if it doesn't get it's acknowledgement 
in time). Hence the blank/dead screen.

To test for this try sending out pings with 1500 mtu and df set (client to 
server or vice versa). If it is the problem, try this:

The solution was to reduce the MTU of the VNC host. This can be done in the 
registry permanently with:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\<adapter>\Tcpip\Paramet

ers\MTU

which should be set to 1400

The NT server can also be forced to discover the MTU of a path by setting:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Enable

PMTUBHDetect

which is a REG_DWORD value. Setting it to 1 forces the NT server to 
discover the MTU of the path to the target system (in this case the VNC 
viewer). If you set the value to 0, it forces the MTU down to 576, and 
doesn't attempt to discover the MTU at all.

The other possibility is if you have any kind of NAT or PAT running and 
it's aging out the ports too quickly. I don't think this is likely unless 
the TCP "hello"s are too widely spaced. You'd fix this on the router.

Hope this is useful

Chris Jaecker
At 06:00  24/01/02 +0000, you wrote:
>Date: Wed, 23 Jan 2002 09:51:56 -0500
>From: mpatient "at" att.com
>Subject: VNC dies and requires reconnection every few minutes (Win NT - AT 
>T Extranet - Cable Modem)
>
>Audience,
>
>When in a VNC viewer session, after a few minutes my viewer cursor detaches
>from my host cursor, indicating that I have lost the session.
>I am unable to type anything on the host display. My connection appears to
>still be on, and I can often start another viewer, type in the password, be
>connected, and resume mouseing and typing right where I left off. This
>happens frequently during most sessions.
>
> > The host is a PC running Windows NT and VNC is loaded during boot-up.
> > The viewer is a PC running Windows NT.
> > I am working through a cable modem connected to Time Warner
Communications
>(Road Runner).
> > I am using AT&T's Extranet security interface.
> > I have 2 PCs connected to a Linksys 5-port Workgroup Hub, which is
>connected to the TWC Cable Modem
>
>Note: When VNC dies, I am not loosing the AT&T Extranet connection and AT&T
>technical support says "it's not them".
>
>??? Do anyone know about this behavior and what might be causing it ???
>
>Mike Patient
>Solution Engineer
> > *     Email : mpatient "at" ems.att.com
> > *     Phone:          407.805.1558

------------------------------

Date: Thu, 24 Jan 2002 11:38:52 -0000
From: "Imani, Paykan" <paykan.imani "at" eds.com>
Subject: AW: Make an VNC-Connection visible

Hi Miachel,

thanks for your answer and excuse me for my too late mail.

thanks, PI


- -----Ursprungliche Nachricht-----
Von: Michael Milette [mailto:tng "at" cyberus.ca]
Gesendet: Sa, 15. Dezember 2001 06:43
An: vnc-list "at" uk.research.att.com
Betreff: Re: Make an VNC-Connection visible


Assuming you are using Windows, the white VNC icon that appears on the task 
bar will change from white to black while someone is connected. 
Unfortunately I don't know of any way, without modifying the source code to 
show that someone connected and then disconnected from your screen while 
you were away from your PC.

The only work around might be to enable the option which pops-up a dialog 
box asking the user on the host machine for permission to allow a guest to 
connect to their screen. This feature is not included in the standard 
WinVNC but is available if you are using TightVNC and possibly TridiaVNC.

                                 Michael

At 03:58 AM 2001-12-14, you wrote:
>Hi,
>
>is there possible to make a connection visible so that a user can see if an
>Admin already connected to him?
>
>Thanks to all
>
>Paykan


- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 09:44:51 -0300
From: Martin.Guillen "at" siemens.com.ar
Subject: RE: DOS VNC

I don't know about VNC but you can use PCAnywhere that has DOS control
software.


- -----Original Message-----
From: Daniel Tan [mailto:danieltan "at" shopnsave.com.sg]
Sent: Wednesday, January 23, 2002 10:54 PM
To: VNC
Subject: DOS VNC


Hi all,
        is there any programs available for DOS? just curious, if have,
think it will help in my job to control and troubleshoot POS machines
currently still using DOS 6.22

Thanks

Daniel


- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 13:00:28 +0000
From: Mark.Reeder "at" reuters.com
Subject: Re:  MTU

Chris,
can you clarify your reply  please.

On 24/01/2002 11:35:20 Chris Jaecker wrote:

> To test for this try sending out pings with 1500 mtu and df set (client to
server or vice versa).

#ping -?

Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
            [-r count] [-s count] [[-j host-list] | [-k host-list]]
            [-w timeout] destination-list

Options:
    -t             Ping the specifed host until interrupted.
    -a             Resolve addresses to hostnames.
    -n count       Number of echo requests to send.
    -l size        Send buffer size.
    -f             Set Don't Fragment flag in packet.
    -i TTL         Time To Live.
    -v TOS         Type Of Service.
    -r count       Record route for count hops.
    -s count       Timestamp for count hops.
    -j host-list   Loose source route along host-list.
    -k host-list   Strict source route along host-list.
    -w timeout     Timeout in milliseconds to wait for each reply.



...so that would be
                                            ping -l 1500 -f  remote_host
      -  correct ?

>If it is the problem, try this:
>
> The solution was to reduce the MTU of the VNC host. This can be done in
the registry permanently with:
>
>
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\<adapter>\Tcpip\Paramet
ers\MTU
>
> which should be set to 1400

[Under NT4 system] I couldn't find any Tcpip\Parameter names under Services
and couldn't really match <adapter> to my actual adapter
can you advise how to create an appropriate "<adapter>" name please.

> The NT server can also be forced to discover the MTU of a path by setting:
>
>
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Enable
PMTUBHDetect
>
On my system, this did not exist, so presumably requires creation.
a) what is the behaviour when entry does not exist?
b) can you confirm that "discover" means "discover and use"
c) As a normal "end-user", when would you NOT want "discover and use" ?
 I assume it is useful when investigating performance and setting up a
network.

> which is a REG_DWORD value. Setting it to 1 forces the NT server to
> discover the MTU of the path to the target system (in this case the VNC
> viewer). If you set the value to 0, it forces the MTU down to 576, and
> doesn't attempt to discover the MTU at all.

thanks for your advice, Mark



- ------------------------------------------------------------- ---
        Visit our Internet site at http://www.reuters.com

Any views expressed in this message are those of  the  individual
sender,  except  where  the sender specifically states them to be
the views of Reuters Ltd.

------------------------------

Date: Thu, 24 Jan 2002 10:08:31 EST
From: <tmillar "at" idrc.ca> (Tracy Millar)
Subject: Re: ConnectPriority - Registry info

Hi there,

I actually made the changes on my server to reflect what Alex has and still 
the same results, the VNC server connection gets dumped when a second 
connection is attempted.

Tracy

- ---------- Original Text ----------

From: "Alex Angelopoulos" <alex "at" bittnet.com>, on 2002/01/23 1:23 PM:
To: iSMTP "at" HQNT11@Servers[<vnc-list "at" uk.research.att.com>],Tracy Millar "at" MIS 
SIG "at" IDRC CRDI

COMPARISON OF REGISTRY VALUES

(SUMMARY NOTE: Tracy is having an issue with having a VNC server connection 
dumped when someone else connects to the same system.
She has, as can be seen, created the ConnectPriority DWORD with a value of 
"2", restarted the server, etc.)

Just a quick note - I am going to try checking this out on my system, but I 
did a quick check on the registry values.  The only
differences in our setups were the following values:

"AutoPortSelect" - mine was 1 as opposed to your "0" - but see next item
"PortNumber" - you had this which I didn't, but yours is set to
0x170c(5900), 
the default
"IdleTimeout" - Yours is "0"; I didn't have this setting
"ConnectPriority" - I had this set to "1"from checking your problem last 
week, and I *did* connect successfully from 2 locations
simultaneously.





- ---- Original Message -----
From: "Tracy Millar" <tmillar "at" idrc.ca>
To: <vnc-list "at" uk.research.att.com>
Sent: Wednesday/2002 January 23 12:38
Subject: Re: ConnectPriority - Registry info


: As requested, here are the registry files as per below...
:
: *********
: REGEDIT4
:
: [HKEY_CURRENT_USER\Software\ORL\WinVNC3]
: "SocketConnect"=dword:00000001

: "AutoPortSelect"=dword:00000000
Mine is 1; obviously you have a custom port setting

: "PortNumber"=dword:0000170c
Which is here...and is set to 5900 manually

: "InputsEnabled"=dword:00000001
: "LocalInputsDisabled"=dword:00000000

: "IdleTimeout"=dword:00000000
I don't even have this

: "QuerySetting"=dword:00000002
: "QueryTimeout"=dword:0000000a
: "PollUnderCursor"=dword:00000000
: "PollForeground"=dword:00000001
: "PollFullScreen"=dword:00000000
: "OnlyPollConsole"=dword:00000001
: "OnlyPollOnEvent"=dword:00000000

: "ConnectPriority"=dword:00000002
I set this to "1" for a test earlier and was able to do 2 simultaneous
connects

: *******************
: REGEDIT4
:
: [HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default]
: "SocketConnect"=dword:00000001
: "AutoPortSelect"=dword:00000000
Didn't have this here

: "PortNumber"=dword:0000170c
Again, didn't have this

: "InputsEnabled"=dword:00000001
: "LocalInputsDisabled"=dword:00000000

: "IdleTimeout"=dword:00000000
Didn't have this here either

: "QuerySetting"=dword:00000002
: "QueryTimeout"=dword:0000000a
: "PollUnderCursor"=dword:00000000
: "PollForeground"=dword:00000001
: "PollFullScreen"=dword:00000000
: "OnlyPollConsole"=dword:00000001
: "OnlyPollOnEvent"=dword:00000000

: "ConnectPriority"=dword:00000002
Again, had a test setting of 1
: Attachment(s):
: HKCU.REG
: HKLM.REG


- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 10:05:57 -0500 (EST)
From: Sasha McLaughlin <samclau "at" wccnet.org>
Subject: MAC PPC Server

Howdy all.
New to the list...I'm trying the Mac Beta.  If anyone else is using it,
please let me know if there is a way to prevent users from closing it OR
is there a way to make it run in the background so it's (almost)
undectable.  We want to implement this, so any help would be a life saver.
Sasha

------------------------------

Date: Thu, 24 Jan 2002 07:16:18 -0800 (PST)
From: brian man <diligent_ly "at" yahoo.com>
Subject: Shift Key problems with VNC

Hi,

I'm using a certain application which requires me to
press the right shift key four times in order to bring
up the management console.
However when I attempt to do this remotely through VNC
nothing happens. It appears as if VNC recognises the
first press down on the shift key and ignores
everything after that. Has anybody experienced
something similar ?
Even better if somebody knows of a workaround to this
it would be a lifesaver as I've been banging my head
off a wall with this one.....

__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com

------------------------------

Date: Thu, 24 Jan 2002 10:30:27 -0500
From: mpatient "at" att.com
Subject: RE: MTU - VNC dies and requires reconnection every few minutes (W
in NT - AT T Extranet - Cable Modem)

Chris and Mark,

Regarding MTUs. I'm not working at that knowledge level, so I asked our
technical support people...

They said we are not using TCP/IP for transport. Instead, we are using
"IPSEC" and the data is both encrypted and encapsulated for transport. 

Thanks for the "shot in the dark". I'm still looking for the light switch...

Mike Patient
Solutions Engineer
> *	Email :	mpatient "at" ems.att.com
> *	Phone:		407.805.1558

- -----Original Message-----
From: Mark.Reeder "at" reuters.com [mailto:Mark.Reeder "at" reuters.com]
Sent: Thursday, January 24, 2002 8:00 AM
To: vnc-list "at" uk.research.att.com
Subject: Re: MTU - VNC dies and requires reconnection every few minutes
(Win NT - AT T Extranet - Cable Modem)


Chris,
can you clarify your reply  please.

On 24/01/2002 11:35:20 Chris Jaecker wrote:

> To test for this try sending out pings with 1500 mtu and df set (client to
server or vice versa).

#ping -?

Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
            [-r count] [-s count] [[-j host-list] | [-k host-list]]
            [-w timeout] destination-list

Options:
    -t             Ping the specifed host until interrupted.
    -a             Resolve addresses to hostnames.
    -n count       Number of echo requests to send.
    -l size        Send buffer size.
    -f             Set Don't Fragment flag in packet.
    -i TTL         Time To Live.
    -v TOS         Type Of Service.
    -r count       Record route for count hops.
    -s count       Timestamp for count hops.
    -j host-list   Loose source route along host-list.
    -k host-list   Strict source route along host-list.
    -w timeout     Timeout in milliseconds to wait for each reply.



...so that would be
                                            ping -l 1500 -f  remote_host
      -  correct ?

>If it is the problem, try this:
>
> The solution was to reduce the MTU of the VNC host. This can be done in
the registry permanently with:
>
>
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\<adapter>\Tcpip\Paramet
ers\MTU
>
> which should be set to 1400

[Under NT4 system] I couldn't find any Tcpip\Parameter names under Services
and couldn't really match <adapter> to my actual adapter
can you advise how to create an appropriate "<adapter>" name please.

> The NT server can also be forced to discover the MTU of a path by setting:
>
>
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Enable
PMTUBHDetect
>
On my system, this did not exist, so presumably requires creation.
a) what is the behaviour when entry does not exist?
b) can you confirm that "discover" means "discover and use"
c) As a normal "end-user", when would you NOT want "discover and use" ?
 I assume it is useful when investigating performance and setting up a
network.

> which is a REG_DWORD value. Setting it to 1 forces the NT server to
> discover the MTU of the path to the target system (in this case the VNC
> viewer). If you set the value to 0, it forces the MTU down to 576, and
> doesn't attempt to discover the MTU at all.

thanks for your advice, Mark



- ------------------------------------------------------------- ---
        Visit our Internet site at http://www.reuters.com

Any views expressed in this message are those of  the  individual
sender,  except  where  the sender specifically states them to be
the views of Reuters Ltd.


- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 10:50:13 -0500
From: "Alex Angelopoulos" <alex "at" bittnet.com>
Subject: Re: ConnectPriority - Registry info

I still see the exact same results throughout my testing.

I experimented with the following settings for the DWORD ConnectPriority
value: 0,1,2,3 (just in case there was something incorrect in the docs).

When using "1" I am able to successfully do connection sharing.

For any other value, I always have the first connection dropped when the
2nd one attempts to connect.  Can anyone shed some light on this?

I have found some references to -shared and -noshared switches in the
archives, but nothing that documents exact usage requirements - and I
have been unable to make any use of those switches work.  Note that one
combination I have *not* tried is to have the 2nd connecting client use
the -noshared switch; requiring this seems to defeat the purpose anyway.

- ----- Original Message -----
From: "Tracy Millar" <tmillar "at" idrc.ca>
To: <vnc-list "at" uk.research.att.com>
Sent: Thursday/2002 January 24 10:08
Subject: Re: ConnectPriority - Registry info


: Hi there,
:
: I actually made the changes on my server to reflect what Alex has and
still
: the same results, the VNC server connection gets dumped when a second
: connection is attempted.
:
: Tracy
:
: ---------- Original Text ----------
:
: From: "Alex Angelopoulos" <alex "at" bittnet.com>, on 2002/01/23 1:23 PM:
: To: iSMTP "at" HQNT11@Servers[<vnc-list "at" uk.research.att.com>],Tracy
Millar "at" MIS
: SIG "at" IDRC CRDI
:
: COMPARISON OF REGISTRY VALUES
:
: (SUMMARY NOTE: Tracy is having an issue with having a VNC server
connection
: dumped when someone else connects to the same system.
: She has, as can be seen, created the ConnectPriority DWORD with a
value of
: "2", restarted the server, etc.)
:
: Just a quick note - I am going to try checking this out on my system,
but I
: did a quick check on the registry values.  The only
: differences in our setups were the following values:
:
: "AutoPortSelect" - mine was 1 as opposed to your "0" - but see next
item
: "PortNumber" - you had this which I didn't, but yours is set to
0x170c(5900),
: the default
: "IdleTimeout" - Yours is "0"; I didn't have this setting
: "ConnectPriority" - I had this set to "1"from checking your problem
last
: week, and I *did* connect successfully from 2 locations
: simultaneously.
:
:
:
:
:
: ---- Original Message -----
: From: "Tracy Millar" <tmillar "at" idrc.ca>
: To: <vnc-list "at" uk.research.att.com>
: Sent: Wednesday/2002 January 23 12:38
: Subject: Re: ConnectPriority - Registry info
:
:
: : As requested, here are the registry files as per below...
: :
: : *********
: : REGEDIT4
: :
: : [HKEY_CURRENT_USER\Software\ORL\WinVNC3]
: : "SocketConnect"=dword:00000001
:
: : "AutoPortSelect"=dword:00000000
: Mine is 1; obviously you have a custom port setting
:
: : "PortNumber"=dword:0000170c
: Which is here...and is set to 5900 manually
:
: : "InputsEnabled"=dword:00000001
: : "LocalInputsDisabled"=dword:00000000
:
: : "IdleTimeout"=dword:00000000
: I don't even have this
:
: : "QuerySetting"=dword:00000002
: : "QueryTimeout"=dword:0000000a
: : "PollUnderCursor"=dword:00000000
: : "PollForeground"=dword:00000001
: : "PollFullScreen"=dword:00000000
: : "OnlyPollConsole"=dword:00000001
: : "OnlyPollOnEvent"=dword:00000000
:
: : "ConnectPriority"=dword:00000002
: I set this to "1" for a test earlier and was able to do 2 simultaneous
connects
:
: : *******************
: : REGEDIT4
: :
: : [HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default]
: : "SocketConnect"=dword:00000001
: : "AutoPortSelect"=dword:00000000
: Didn't have this here
:
: : "PortNumber"=dword:0000170c
: Again, didn't have this
:
: : "InputsEnabled"=dword:00000001
: : "LocalInputsDisabled"=dword:00000000
:
: : "IdleTimeout"=dword:00000000
: Didn't have this here either
:
: : "QuerySetting"=dword:00000002
: : "QueryTimeout"=dword:0000000a
: : "PollUnderCursor"=dword:00000000
: : "PollForeground"=dword:00000001
: : "PollFullScreen"=dword:00000000
: : "OnlyPollConsole"=dword:00000001
: : "OnlyPollOnEvent"=dword:00000000
:
: : "ConnectPriority"=dword:00000002
: Again, had a test setting of 1
: : Attachment(s):
: : HKCU.REG
: : HKLM.REG
: ---------------------------------------------------------------------
: To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
: 'unsubscribe vnc-list' in the message BODY
: See also: http://www.uk.research.att.com/vnc/intouch.html
: ---------------------------------------------------------------------
: ---------------------------------------------------------------------
: To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
: 'unsubscribe vnc-list' in the message BODY
: See also: http://www.uk.research.att.com/vnc/intouch.html
: ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 10:51:50 -0500
From: "St Jean, Denis" <Denis.StJean "at" Compaq.com>
Subject: RE: ConnectPriority - Registry info

Hello Tracy,

I've had the same problem w/ Wintel based connections. it seems like the
only way around this is when you connect via the VNCviewer, is to go
into "options", and click on "Request shared session" under misc.

That works ok, the only problem is the default setting is "off" so
people have to remember to click it on before proceeding with the
connection.

Good luck,

Denis.

- -----Original Message-----
From: Tracy Millar [mailto:tmillar "at" idrc.ca]
Sent: Thursday, January 24, 2002 10:09 AM
To: vnc-list "at" uk.research.att.com
Subject: Re: ConnectPriority - Registry info


Hi there,

I actually made the changes on my server to reflect what Alex has and
still
the same results, the VNC server connection gets dumped when a second
connection is attempted.

Tracy

- ---------- Original Text ----------

From: "Alex Angelopoulos" <alex "at" bittnet.com>, on 2002/01/23 1:23 PM:
To: iSMTP "at" HQNT11@Servers[<vnc-list "at" uk.research.att.com>],Tracy
Millar "at" MIS
SIG "at" IDRC CRDI

COMPARISON OF REGISTRY VALUES

(SUMMARY NOTE: Tracy is having an issue with having a VNC server
connection
dumped when someone else connects to the same system.
She has, as can be seen, created the ConnectPriority DWORD with a value
of
"2", restarted the server, etc.)

Just a quick note - I am going to try checking this out on my system,
but I
did a quick check on the registry values.  The only
differences in our setups were the following values:

"AutoPortSelect" - mine was 1 as opposed to your "0" - but see next item
"PortNumber" - you had this which I didn't, but yours is set to
0x170c(5900),
the default
"IdleTimeout" - Yours is "0"; I didn't have this setting
"ConnectPriority" - I had this set to "1"from checking your problem last

week, and I *did* connect successfully from 2 locations
simultaneously.





- ---- Original Message -----
From: "Tracy Millar" <tmillar "at" idrc.ca>
To: <vnc-list "at" uk.research.att.com>
Sent: Wednesday/2002 January 23 12:38
Subject: Re: ConnectPriority - Registry info


: As requested, here are the registry files as per below...
:
: *********
: REGEDIT4
:
: [HKEY_CURRENT_USER\Software\ORL\WinVNC3]
: "SocketConnect"=dword:00000001

: "AutoPortSelect"=dword:00000000
Mine is 1; obviously you have a custom port setting

: "PortNumber"=dword:0000170c
Which is here...and is set to 5900 manually

: "InputsEnabled"=dword:00000001
: "LocalInputsDisabled"=dword:00000000

: "IdleTimeout"=dword:00000000
I don't even have this

: "QuerySetting"=dword:00000002
: "QueryTimeout"=dword:0000000a
: "PollUnderCursor"=dword:00000000
: "PollForeground"=dword:00000001
: "PollFullScreen"=dword:00000000
: "OnlyPollConsole"=dword:00000001
: "OnlyPollOnEvent"=dword:00000000

: "ConnectPriority"=dword:00000002
I set this to "1" for a test earlier and was able to do 2 simultaneous
connects

: *******************
: REGEDIT4
:
: [HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default]
: "SocketConnect"=dword:00000001
: "AutoPortSelect"=dword:00000000
Didn't have this here

: "PortNumber"=dword:0000170c
Again, didn't have this

: "InputsEnabled"=dword:00000001
: "LocalInputsDisabled"=dword:00000000

: "IdleTimeout"=dword:00000000
Didn't have this here either

: "QuerySetting"=dword:00000002
: "QueryTimeout"=dword:0000000a
: "PollUnderCursor"=dword:00000000
: "PollForeground"=dword:00000001
: "PollFullScreen"=dword:00000000
: "OnlyPollConsole"=dword:00000001
: "OnlyPollOnEvent"=dword:00000000

: "ConnectPriority"=dword:00000002
Again, had a test setting of 1
: Attachment(s):
: HKCU.REG
: HKLM.REG


- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------
- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 11:05:40 -0500
From: "Alex Angelopoulos" <alex "at" bittnet.com>
Subject: Re: ConnectPriority - Registry info

I found the fix, Tracy.  It doesn't make sense, either.

I created the DWORD value under

HKEY_LOCAL_MACHINE/Software/ORL/WinVNC3/

as well as

HKEY_LOCAL_MACHINE/Software/ORL/WinVNC3/Default

And it now disconnects any secondary connection attempts.

I found the following reference in the "History.txt" file accompanying
the Windows source files, which seems to suggest that this value should
be read from the top-level key instead of "Default".


"HKEY_LOCAL_MACHINE/Software/ORL/WinVNC3/ConnectPriority
 setting can take one of three values:
  0 - new, non-shared incoming connections kick off existing ones.
  1 - all incoming connections are treated as shared, regardless of
the -shared viewer option.
  2 - new, non-shared incoming connections will be refused if a current
connection exists."



What this doesn't explain is why setting ConnectPriority to 1 within the
.Default key successfully allows shared connections.



- ----- Original Message -----
From: "Tracy Millar" <tmillar "at" idrc.ca>
To: <vnc-list "at" uk.research.att.com>
Sent: Thursday/2002 January 24 10:08
Subject: Re: ConnectPriority - Registry info


: Hi there,
:
: I actually made the changes on my server to reflect what Alex has and
still
: the same results, the VNC server connection gets dumped when a second
: connection is attempted.
:
: Tracy
:
: ---------- Original Text ----------
:
: From: "Alex Angelopoulos" <alex "at" bittnet.com>, on 2002/01/23 1:23 PM:
: To: iSMTP "at" HQNT11@Servers[<vnc-list "at" uk.research.att.com>],Tracy
Millar "at" MIS
: SIG "at" IDRC CRDI
:
: COMPARISON OF REGISTRY VALUES
:
: (SUMMARY NOTE: Tracy is having an issue with having a VNC server
connection
: dumped when someone else connects to the same system.
: She has, as can be seen, created the ConnectPriority DWORD with a
value of
: "2", restarted the server, etc.)
:
: Just a quick note - I am going to try checking this out on my system,
but I
: did a quick check on the registry values.  The only
: differences in our setups were the following values:
:
: "AutoPortSelect" - mine was 1 as opposed to your "0" - but see next
item
: "PortNumber" - you had this which I didn't, but yours is set to
0x170c(5900),
: the default
: "IdleTimeout" - Yours is "0"; I didn't have this setting
: "ConnectPriority" - I had this set to "1"from checking your problem
last
: week, and I *did* connect successfully from 2 locations
: simultaneously.
:
:
:
:
:
: ---- Original Message -----
: From: "Tracy Millar" <tmillar "at" idrc.ca>
: To: <vnc-list "at" uk.research.att.com>
: Sent: Wednesday/2002 January 23 12:38
: Subject: Re: ConnectPriority - Registry info
:
:
: : As requested, here are the registry files as per below...
: :
: : *********
: : REGEDIT4
: :
: : [HKEY_CURRENT_USER\Software\ORL\WinVNC3]
: : "SocketConnect"=dword:00000001
:
: : "AutoPortSelect"=dword:00000000
: Mine is 1; obviously you have a custom port setting
:
: : "PortNumber"=dword:0000170c
: Which is here...and is set to 5900 manually
:
: : "InputsEnabled"=dword:00000001
: : "LocalInputsDisabled"=dword:00000000
:
: : "IdleTimeout"=dword:00000000
: I don't even have this
:
: : "QuerySetting"=dword:00000002
: : "QueryTimeout"=dword:0000000a
: : "PollUnderCursor"=dword:00000000
: : "PollForeground"=dword:00000001
: : "PollFullScreen"=dword:00000000
: : "OnlyPollConsole"=dword:00000001
: : "OnlyPollOnEvent"=dword:00000000
:
: : "ConnectPriority"=dword:00000002
: I set this to "1" for a test earlier and was able to do 2 simultaneous
connects
:
: : *******************
: : REGEDIT4
: :
: : [HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default]
: : "SocketConnect"=dword:00000001
: : "AutoPortSelect"=dword:00000000
: Didn't have this here
:
: : "PortNumber"=dword:0000170c
: Again, didn't have this
:
: : "InputsEnabled"=dword:00000001
: : "LocalInputsDisabled"=dword:00000000
:
: : "IdleTimeout"=dword:00000000
: Didn't have this here either
:
: : "QuerySetting"=dword:00000002
: : "QueryTimeout"=dword:0000000a
: : "PollUnderCursor"=dword:00000000
: : "PollForeground"=dword:00000001
: : "PollFullScreen"=dword:00000000
: : "OnlyPollConsole"=dword:00000001
: : "OnlyPollOnEvent"=dword:00000000
:
: : "ConnectPriority"=dword:00000002
: Again, had a test setting of 1
: : Attachment(s):
: : HKCU.REG
: : HKLM.REG
: ---------------------------------------------------------------------
: To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
: 'unsubscribe vnc-list' in the message BODY
: See also: http://www.uk.research.att.com/vnc/intouch.html
: ---------------------------------------------------------------------
: ---------------------------------------------------------------------
: To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
: 'unsubscribe vnc-list' in the message BODY
: See also: http://www.uk.research.att.com/vnc/intouch.html
: ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 11:08:19 EST
From: <tmillar "at" idrc.ca> (Tracy Millar)
Subject: RE: ConnectPriority - Registry info

Denis,

Thank you for your reply..."option" in the VNCviewer Properties?  There's no

such thing...or am I missing something?

Tracy Millar
ITMD/DGTI
IDRC/CRDI
(613) 236-6163 ext 2581
tmillar "at" idrc.ca
http://intra1.idrc.ca/mis-sig
- ---------- Original Text ----------

From: "St Jean, Denis" <Denis.StJean "at" Compaq.com>, on 2002/01/24 11:02 AM:
To: iSMTP "at" HQNT11@Servers[<vnc-list "at" uk.research.att.com>],Tracy Millar "at" MIS 
SIG "at" IDRC CRDI

Hello Tracy,

I've had the same problem w/ Wintel based connections. it seems like the
only way around this is when you connect via the VNCviewer, is to go
into "options", and click on "Request shared session" under misc.

That works ok, the only problem is the default setting is "off" so
people have to remember to click it on before proceeding with the
connection.

Good luck,

Denis.

- -----Original Message-----
From: Tracy Millar [mailto:tmillar "at" idrc.ca]
Sent: Thursday, January 24, 2002 10:09 AM
To: vnc-list "at" uk.research.att.com
Subject: Re: ConnectPriority - Registry info


Hi there,

I actually made the changes on my server to reflect what Alex has and
still
the same results, the VNC server connection gets dumped when a second
connection is attempted.

Tracy

- ---------- Original Text ----------

From: "Alex Angelopoulos" <alex "at" bittnet.com>, on 2002/01/23 1:23 PM:
To: iSMTP "at" HQNT11@Servers[<vnc-list "at" uk.research.att.com>],Tracy
Millar "at" MIS
SIG "at" IDRC CRDI

COMPARISON OF REGISTRY VALUES

(SUMMARY NOTE: Tracy is having an issue with having a VNC server
connection
dumped when someone else connects to the same system.
She has, as can be seen, created the ConnectPriority DWORD with a value
of
"2", restarted the server, etc.)

Just a quick note - I am going to try checking this out on my system,
but I
did a quick check on the registry values.  The only
differences in our setups were the following values:

"AutoPortSelect" - mine was 1 as opposed to your "0" - but see next item
"PortNumber" - you had this which I didn't, but yours is set to
0x170c(5900),
the default
"IdleTimeout" - Yours is "0"; I didn't have this setting
"ConnectPriority" - I had this set to "1"from checking your problem last

week, and I *did* connect successfully from 2 locations
simultaneously.





- ---- Original Message -----
From: "Tracy Millar" <tmillar "at" idrc.ca>
To: <vnc-list "at" uk.research.att.com>
Sent: Wednesday/2002 January 23 12:38
Subject: Re: ConnectPriority - Registry info


: As requested, here are the registry files as per below...
:
: *********
: REGEDIT4
:
: [HKEY_CURRENT_USER\Software\ORL\WinVNC3]
: "SocketConnect"=dword:00000001

: "AutoPortSelect"=dword:00000000
Mine is 1; obviously you have a custom port setting

: "PortNumber"=dword:0000170c
Which is here...and is set to 5900 manually

: "InputsEnabled"=dword:00000001
: "LocalInputsDisabled"=dword:00000000

: "IdleTimeout"=dword:00000000
I don't even have this

: "QuerySetting"=dword:00000002
: "QueryTimeout"=dword:0000000a
: "PollUnderCursor"=dword:00000000
: "PollForeground"=dword:00000001
: "PollFullScreen"=dword:00000000
: "OnlyPollConsole"=dword:00000001
: "OnlyPollOnEvent"=dword:00000000

: "ConnectPriority"=dword:00000002
I set this to "1" for a test earlier and was able to do 2 simultaneous
connects

: *******************
: REGEDIT4
:
: [HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default]
: "SocketConnect"=dword:00000001
: "AutoPortSelect"=dword:00000000
Didn't have this here

: "PortNumber"=dword:0000170c
Again, didn't have this

: "InputsEnabled"=dword:00000001
: "LocalInputsDisabled"=dword:00000000

: "IdleTimeout"=dword:00000000
Didn't have this here either

: "QuerySetting"=dword:00000002
: "QueryTimeout"=dword:0000000a
: "PollUnderCursor"=dword:00000000
: "PollForeground"=dword:00000001
: "PollFullScreen"=dword:00000000
: "OnlyPollConsole"=dword:00000001
: "OnlyPollOnEvent"=dword:00000000

: "ConnectPriority"=dword:00000002
Again, had a test setting of 1
: Attachment(s):
: HKCU.REG
: HKLM.REG


- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------
- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------
- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 08:34:32 -0800
From: Bobby Ramirez <BobbyR "at" belkin.com>
Subject: RE: SUMMARY - starting the vncserver - found a perl book!!

any ideas on my recent post? see a recap below.

after starting the vnc server like this: ./vncserver :13 -pn -localhost

i get the following messages in the vnc server log.

Xlib: Client is not authorizAUDIT
1 reXlib: connection to "unAUDIT: Wed Jan 23 15:59:05 2002: 13009 Xvnc:
client 1
 rejected from local host
1 reXlib: connection to "unAUDIT: Wed Jan 23 15:59:05 2002: 13009 Xvnc:
client 1
 rejected from local host
twm:  unable to open display ":13"

Xlib: connection to "unix:13.0" refused by server

Xlib: Client is not authorized to connect to Server

xterm Xt error: Can't open display: :13

the connection is refused by the server, what's Up!!

how can i tell vnc server is running? is there a process id?


Bobby Ramirez
Belkin Components
Information Systems
310-604-2068


- -----Original Message-----
From: Illtud Daniel [mailto:illtud.daniel "at" llgc.org.uk]
Sent: Thursday, January 24, 2002 2:01 AM
To: vnc-list "at" uk.research.att.com
Subject: Re: SUMMARY - starting the vncserver - found a perl book!!


Bobby Ramirez wrote:
> 
> i just added /usr/openwin/bin to my path, and the system
> function could then find the xauth command.

Ooops, didn't see this follow-up. Glad you got it working,
ignore my post!

- -- 
Illtud Daniel                                 illtud.daniel "at" llgc.org.uk
Uwch Ddadansoddwr Systemau                       Senior Systems Analyst
Llyfrgell Genedlaethol Cymru                  National Library of Wales
Yn siarad drosof fy hun, nid LlGC   -  Speaking personally, not for NLW



Confidential
This e-mail and any files transmitted with it are the property
of Belkin Components and/or its affiliates, are confidential,
and are intended solely for the use of the individual or
entity to whom this e-mail is addressed.  If you are not one
of the named recipients or otherwise have reason to believe
that you have received this e-mail in error, please notify the
sender and delete this message immediately from your computer.
Any other use, retention, dissemination, forwarding, printing
or copying of this e-mail is strictly prohibited.
- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 10:41:39 -0600
From: "Network Helpme" <HELPME "at" des.uwm.edu>
Subject: Re: java.net.socketException:  SocketThread Failed

yes she was just using the web browser applet.  Ill suggest she try the
viewer.  what do you mean by loopback in this context? (sorry im a bit
new to this)

thanks again

Brian Jahns
Assistant Network Administrator
Department of Enrollment Services
University of Wisconsin - Milwaukee
(414) 229-4574
bjahns "at" des.uwm.edu

------------------------------

Date: Thu, 24 Jan 2002 10:48:18 -0600
From: W T Meyer <meyer "at" iastate.edu>
Subject: Connection refused

When I try to use screen sharing with VRVS the client machines give the 
message "java.net.ConnectException: Connection Refused".

I've tried it on three machines:
    Win NT4 using both Netscape 4.5 and I.E. 5.0
    Win2000 Pro using both Netscape 4.7 and I.E.  5.0
    Linux Red Hat 7.1 using Netscape 4.76

All three machines do the same thing.  The server says it's just fine, but 
the clients can't connect.
There is no firewall and I'm not using proxies.

In a test from another institution, the Win2000 machine was able to connect 
as the client just fine.

What am I doing wrong?

Tom Meyer
Iowa State University

------------------------------

Date: Thu, 24 Jan 2002 11:39:18 -0500
From: Glenn Mabbutt <gmabbutt "at" quartetservice.com>
Subject: RE: Shift Key problems with VNC

Usually vncviewer will only pass local function keys (CTRL, ALT, SHIFT) to
the remote side if you hold down the SHIFT key first - try holding down your
left SHIFT key, and then press your right SHIFT key 4 times (or vice-versa).

- -----Original Message-----
From: brian man [mailto:diligent_ly "at" yahoo.com]
Sent: Thursday, January 24, 2002 10:16 AM
To: vnc-list "at" uk.research.att.com
Subject: Shift Key problems with VNC


Hi,

I'm using a certain application which requires me to
press the right shift key four times in order to bring
up the management console.
However when I attempt to do this remotely through VNC
nothing happens. It appears as if VNC recognises the
first press down on the shift key and ignores
everything after that. Has anybody experienced
something similar ?
Even better if somebody knows of a workaround to this
it would be a lifesaver as I've been banging my head
off a wall with this one.....

__________________________________________________
Do You Yahoo!?
Great stuff seeking new owners in Yahoo! Auctions! 
http://auctions.yahoo.com


- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 17:01:38 +0000
From: Illtud Daniel <illtud.daniel "at" llgc.org.uk>
Subject: Re: SUMMARY - starting the vncserver - found a perl book!!

Bobby Ramirez wrote:
 
> any ideas on my recent post? see a recap below.

> Xlib: Client is not authorizAUDIT
> 1 reXlib: connection to "unAUDIT: Wed Jan 23 15:59:05 2002: 13009 Xvnc:
client 1
>  rejected from local host

That's an xauth problem. You need to give your clients
authorisation to access the Xvnc server (careful with the
client/server terminology when using X or Xvnc - the clients
are the programs that appear on your Xserver, including the
window manager - if that can't start, you get only a grey
screen). What uid is your Xvnc running as? It might be running
as root, and your Xclients won't be allowed to connect to it.
You should be running Xvnc as your own uid. See below:

> how can i tell vnc server is running? is there a process id?

You can do:

ps -aef | grep vnc

which should give you something like:

$ ps -aef | grep vnc
user1     467     1  0  2001 ?        00:14:34 Xvnc :1 -desktop X -httpd
/usr/s
user2     490     1  0  2001 ?        00:01:27 Xvnc :2 -desktop X -httpd
/usr/s
user3   30536     1  0 Jan15 ?        00:00:00 Xvnc :3 -desktop X -httpd
/usr/s

Which should give you the process id's for any Xvnc server sessions, and
(first column) the UIDs they're running under. If you must run
Xvnc as root for some reason, have a search for 'xauth' in the
archives for answers on getting the authorisation for your clients
(or do 'man xauth'!).

- -- 
Illtud Daniel                                 illtud.daniel "at" llgc.org.uk
Uwch Ddadansoddwr Systemau                       Senior Systems Analyst
Llyfrgell Genedlaethol Cymru                  National Library of Wales
Yn siarad drosof fy hun, nid LlGC   -  Speaking personally, not for NLW

------------------------------

Date: Thu, 24 Jan 2002 12:08:48 -0500
From: Michael Milette <tng "at" cyberus.ca>
Subject: Re: DOS VNC

Hi there,

Check out PCREMOTE by PC Magazine. It was first published (as far as I 
know) on January 16th, 1990 and can be found on the web by searching for 
V9N01.ZIP.

The only drawback is that it only works over a COM port. If you can work 
this into your system, this might just be what you have been looking for.

On the plus side, it is free. Hope this helps...

                                 Michael

At 08:54 PM 2002-01-23, you wrote:
>Hi all,
>         is there any programs available for DOS? just curious, if have,
>think it will help in my job to control and troubleshoot POS machines
>currently still using DOS 6.22
>
>Thanks
>
>Daniel

------------------------------

Date: Thu, 24 Jan 2002 17:08:59 +0000
From: Illtud Daniel <illtud.daniel "at" llgc.org.uk>
Subject: Re: DOS VNC

> From: Daniel Tan [mailto:danieltan "at" shopnsave.com.sg]

>         is there any programs available for DOS? just curious, if have,
> think it will help in my job to control and troubleshoot POS machines
> currently still using DOS 6.22

There's (more than one, IIRC) telnetd's for DOS. Here's one:

 http://www.simtel.net/pub/pd/48905.html

But I'm not sure it'll run your app - depends on the terminal
emulation & how DOS does curses-style stuff. Assuming, of
course that your app isn't VGA or something. I wouldn't try
and use this across any unsecured network (same goes for telnet
on any platform), but you could have a VPN gateway or something
both ends... dunno - rather you than me!

(you could run the POS app in a DOSemu (http://www.dosemu.org/)
 instance under linux, and use VNC on linux.... but that's probably
 being a bit silly...)

- -- 
Illtud Daniel                                 illtud.daniel "at" llgc.org.uk
Uwch Ddadansoddwr Systemau                       Senior Systems Analyst
Llyfrgell Genedlaethol Cymru                  National Library of Wales
Yn siarad drosof fy hun, nid LlGC   -  Speaking personally, not for NLW

------------------------------

Date: Thu, 24 Jan 2002 12:20:43 -0500
From: "Alex Angelopoulos" <alex "at" bittnet.com>
Subject: Re: java.net.socketException:  SocketThread Failed

I wasn't using the term loopback formally.  It sounded like you went out
to the machine in your test, then "looped back" into your network.

Re-reading your message, I'm not sure you did that exact test - namely,
connecting to her machine then trying an outbound connection to
somewhere else. Is the WinMe machine the one FROM which she is using the
java viewer? or was she connecting TO the WinMe box from somewhere else?

- ----- Original Message -----
From: "Network Helpme" <HELPME "at" des.uwm.edu>
To: <vnc-list "at" uk.research.att.com>
Sent: Thursday/2002 January 24 11:41
Subject: Re: java.net.socketException: SocketThread Failed


: yes she was just using the web browser applet.  Ill suggest she try
the
: viewer.  what do you mean by loopback in this context? (sorry im a bit
: new to this)
:
: thanks again
:
: Brian Jahns
: Assistant Network Administrator
: Department of Enrollment Services
: University of Wisconsin - Milwaukee
: (414) 229-4574
: bjahns "at" des.uwm.edu
: ---------------------------------------------------------------------
: To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
: 'unsubscribe vnc-list' in the message BODY
: See also: http://www.uk.research.att.com/vnc/intouch.html
: ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 12:22:14 -0500
From: "Alex Angelopoulos" <alex "at" bittnet.com>
Subject: Re: Connection refused

Just wanted some clarification: every single one of those tests was done
with the Java viewer?  Including the successful one?

- ----- Original Message -----
From: "W T Meyer" <meyer "at" iastate.edu>
To: <vnc-list "at" uk.research.att.com>
Sent: Thursday/2002 January 24 11:48
Subject: Connection refused


: When I try to use screen sharing with VRVS the client machines give
the
: message "java.net.ConnectException: Connection Refused".
:
: I've tried it on three machines:
:     Win NT4 using both Netscape 4.5 and I.E. 5.0
:     Win2000 Pro using both Netscape 4.7 and I.E.  5.0
:     Linux Red Hat 7.1 using Netscape 4.76
:
: All three machines do the same thing.  The server says it's just fine,
but
: the clients can't connect.
: There is no firewall and I'm not using proxies.
:
: In a test from another institution, the Win2000 machine was able to
connect
: as the client just fine.
:
: What am I doing wrong?
:
: Tom Meyer
: Iowa State University
: ---------------------------------------------------------------------
: To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
: 'unsubscribe vnc-list' in the message BODY
: See also: http://www.uk.research.att.com/vnc/intouch.html
: ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 12:10:19 -0600
From: W T Meyer <meyer "at" iastate.edu>
Subject: Re: Connection refused

Yes, I tried to do the same thing every time.

At 12:22 PM 1/24/2002 -0500, you wrote:
>Just wanted some clarification: every single one of those tests was done
>with the Java viewer?  Including the successful one?
>
>----- Original Message -----
>From: "W T Meyer" <meyer "at" iastate.edu>
>To: <vnc-list "at" uk.research.att.com>
>Sent: Thursday/2002 January 24 11:48
>Subject: Connection refused
>
>
>: When I try to use screen sharing with VRVS the client machines give
>the
>: message "java.net.ConnectException: Connection Refused".
>:
>: I've tried it on three machines:
>:     Win NT4 using both Netscape 4.5 and I.E. 5.0
>:     Win2000 Pro using both Netscape 4.7 and I.E.  5.0
>:     Linux Red Hat 7.1 using Netscape 4.76
>:
>: All three machines do the same thing.  The server says it's just fine,
>but
>: the clients can't connect.
>: There is no firewall and I'm not using proxies.
>:
>: In a test from another institution, the Win2000 machine was able to
>connect
>: as the client just fine.
>:
>: What am I doing wrong?
>:
>: Tom Meyer
>: Iowa State University
>: ---------------------------------------------------------------------
>: To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
>: 'unsubscribe vnc-list' in the message BODY
>: See also: http://www.uk.research.att.com/vnc/intouch.html
>: ---------------------------------------------------------------------
>---------------------------------------------------------------------
>To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
>'unsubscribe vnc-list' in the message BODY
>See also: http://www.uk.research.att.com/vnc/intouch.html
>---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 10:16:06 -0800
From: Frank Evan Perdicaro <frank "at" dsea.com>
Subject: Re: Re: Tight 1.2.2: big slowdown?

> Have you checked to see if any of the encoding option defaults are
> different?  Turning up compression too far can cause overhead that slows
> things down, for example.

The client is run with the exact same command line, requesting maximum
compression, minimum fidelty, and minimum color space.  Since the
client controls the compression, yes, I have made sure nothing is
different simply by not changing the command line that invokes the
client.

Server overhead, as viewed by the performance meter, is low.  The
screen is small (SVGA) and 256 colors.  Client overhead rounds out to
zero: I am running a fast dual CPU Sun with 512 Mb and Creator
graphics.

------------------------------

Date: Thu, 24 Jan 2002 13:34:27 -0500
From: "Alex Angelopoulos" <alex "at" bittnet.com>
Subject: Re: DOS VNC

I found a link for it right away, too - this one is still good.

http://asciidownload.uni-hd.de/ftp/pub/simtelnet/msdos/pcmag/


- ----- Original Message -----
From: "Michael Milette" <tng "at" cyberus.ca>
To: <vnc-list "at" uk.research.att.com>
Sent: Thursday/2002 January 24 12:08
Subject: Re: DOS VNC


: Hi there,
:
: Check out PCREMOTE by PC Magazine. It was first published (as far as I
: know) on January 16th, 1990 and can be found on the web by searching
for
: V9N01.ZIP.
:
: The only drawback is that it only works over a COM port. If you can
work
: this into your system, this might just be what you have been looking
for.
:
: On the plus side, it is free. Hope this helps...
:
:                                  Michael
:
: At 08:54 PM 2002-01-23, you wrote:
: >Hi all,
: >         is there any programs available for DOS? just curious, if
have,
: >think it will help in my job to control and troubleshoot POS machines
: >currently still using DOS 6.22
: >
: >Thanks
: >
: >Daniel
: ---------------------------------------------------------------------
: To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
: 'unsubscribe vnc-list' in the message BODY
: See also: http://www.uk.research.att.com/vnc/intouch.html
: ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 13:45:11 -0500
From: Glenn Mabbutt <gmabbutt "at" quartetservice.com>
Subject: RE: MTU - VNC dies and requires reconnection every few minutes (W
in NT - AT T Extranet - Cable Modem)

Minor confusion here - "IPsec" is an encrypted packet protocol that MAKES
USE OF tcp/ip.  In fact, as I recall, there was a thread on this last some
months ago about someone have this very same issue (VNC over IPsec tunnel
would disconnect, user adjusted MTU values, and it worked just fine).
Search the mailing list archives and you should find what I mean.

Glenn

- -----Original Message-----
From: mpatient "at" att.com [mailto:mpatient "at" att.com]
Sent: Thursday, January 24, 2002 10:30 AM
To: vnc-list "at" uk.research.att.com
Subject: RE: MTU - VNC dies and requires reconnection every few minutes
(W in NT - AT T Extranet - Cable Modem)


Chris and Mark,

Regarding MTUs. I'm not working at that knowledge level, so I asked our
technical support people...

They said we are not using TCP/IP for transport. Instead, we are using
"IPSEC" and the data is both encrypted and encapsulated for transport. 

Thanks for the "shot in the dark". I'm still looking for the light switch...

Mike Patient
Solutions Engineer
> *	Email :	mpatient "at" ems.att.com
> *	Phone:		407.805.1558

- -----Original Message-----
From: Mark.Reeder "at" reuters.com [mailto:Mark.Reeder "at" reuters.com]
Sent: Thursday, January 24, 2002 8:00 AM
To: vnc-list "at" uk.research.att.com
Subject: Re: MTU - VNC dies and requires reconnection every few minutes
(Win NT - AT T Extranet - Cable Modem)


Chris,
can you clarify your reply  please.

On 24/01/2002 11:35:20 Chris Jaecker wrote:

> To test for this try sending out pings with 1500 mtu and df set (client to
server or vice versa).

#ping -?

Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
            [-r count] [-s count] [[-j host-list] | [-k host-list]]
            [-w timeout] destination-list

Options:
    -t             Ping the specifed host until interrupted.
    -a             Resolve addresses to hostnames.
    -n count       Number of echo requests to send.
    -l size        Send buffer size.
    -f             Set Don't Fragment flag in packet.
    -i TTL         Time To Live.
    -v TOS         Type Of Service.
    -r count       Record route for count hops.
    -s count       Timestamp for count hops.
    -j host-list   Loose source route along host-list.
    -k host-list   Strict source route along host-list.
    -w timeout     Timeout in milliseconds to wait for each reply.



...so that would be
                                            ping -l 1500 -f  remote_host
      -  correct ?

>If it is the problem, try this:
>
> The solution was to reduce the MTU of the VNC host. This can be done in
the registry permanently with:
>
>
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\<adapter>\Tcpip\Paramet
ers\MTU
>
> which should be set to 1400

[Under NT4 system] I couldn't find any Tcpip\Parameter names under Services
and couldn't really match <adapter> to my actual adapter
can you advise how to create an appropriate "<adapter>" name please.

> The NT server can also be forced to discover the MTU of a path by setting:
>
>
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Enable
PMTUBHDetect
>
On my system, this did not exist, so presumably requires creation.
a) what is the behaviour when entry does not exist?
b) can you confirm that "discover" means "discover and use"
c) As a normal "end-user", when would you NOT want "discover and use" ?
 I assume it is useful when investigating performance and setting up a
network.

> which is a REG_DWORD value. Setting it to 1 forces the NT server to
> discover the MTU of the path to the target system (in this case the VNC
> viewer). If you set the value to 0, it forces the MTU down to 576, and
> doesn't attempt to discover the MTU at all.

thanks for your advice, Mark



- ------------------------------------------------------------- ---
        Visit our Internet site at http://www.reuters.com

Any views expressed in this message are those of  the  individual
sender,  except  where  the sender specifically states them to be
the views of Reuters Ltd.


- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------
- ---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
- ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 14:50:24 -0500
From: David Rothman <drothman "at" optonline.net>
Subject: winvnc w/xp and mult users

i'm still not clear why this isn't working for me.

i installed xp-home on a machine which i previously used 98 & vnc on.

there are 5 users on the xp machine.  i installed vnc as the administrator
and
it 'works' (meaning i can  load & see that machine remotely from a w2000
machine).  it doesn't load when i log on as one of the sub (limited) users.
i
have tried to install the vnc service as the limited user, but i get the scm
error. i can load it manually and it will work.  i guess i can add it to the
startup folder as opposed to it being called from the registry upon logon,
but
i'd rather not.  is there something else i can do? thanks

------------------------------

Date: Thu, 24 Jan 2002 14:59:55 -0500
From: David Rothman <drothman "at" optonline.net>
Subject: Re: winvnc w/xp and mult users

let me amend that.  it doesn't work when i load winvnc manually as a limited
user.  i can connect, from the w2000 machine, but i only see a black
screen...


- ----- Original Message -----
From: "David Rothman" <drothman "at" optonline.net>
To: <vnc-list "at" uk.research.att.com>
Sent: Thursday, January 24, 2002 2:50 PM
Subject: winvnc w/xp and mult users


> i'm still not clear why this isn't working for me.
>
> i installed xp-home on a machine which i previously used 98 & vnc on.
>
> there are 5 users on the xp machine.  i installed vnc as the administrator
and
> it 'works' (meaning i can  load & see that machine remotely from a w2000
> machine).  it doesn't load when i log on as one of the sub (limited)
users.  i
> have tried to install the vnc service as the limited user, but i get the
scm
> error. i can load it manually and it will work.  i guess i can add it to
the
> startup folder as opposed to it being called from the registry upon logon,
but
> i'd rather not.  is there something else i can do? thanks
> ---------------------------------------------------------------------
> To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
> 'unsubscribe vnc-list' in the message BODY
> See also: http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------

------------------------------

Date: Thu, 24 Jan 2002 21:57:33 +0100
From: "crackjack" <crackjack "at" crackjack.8m.com>
Subject: Connection closed

I get this all the time i want to logon to my P150
I just installed winvnc-server on it and it has approximately all standard
values
only 192.168.0.* is allowed and must be confirmed on the server

here is a piece of the logfile where the trouble is

The password is correct (as you can see in the log)

if anyone knows a solution..
BTW: i know its a crappy pc but a friend of me has it running smoothly on a
P133

-
----------------------------------------------------------------------------
-
- ----------
Thu Jan 24 21:22:03 2002
D:\ORL\vss\winvnc\vncSockConnect.cpp : accepted connection from
192.168.0.160
D:\ORL\vss\winvnc\vncClient.cpp : vncClient() executing...
D:\ORL\vss\winvnc\WinVNC.cpp : message 1026 recieved
D:\ORL\vss\winvnc\vncServer.cpp : AddClient() done
D:\ORL\vss\winvnc\vncClient.cpp : client connected : 192.168.0.160 (1)
D:\ORL\vss\winvnc\vncClient.cpp : negotiated version
D:\ORL\vss\winvnc\vncPasswd.h : PASSWD : ToText called
Thu Jan 24 21:22:05 2002
D:\ORL\vss\winvnc\WinVNC.cpp : message 275 recieved
D:\ORL\vss\winvnc\WinVNC.cpp : message 84 recieved
D:\ORL\vss\winvnc\vncMenu.cpp : usernames : old="", new=""
Thu Jan 24 21:22:10 2002
D:\ORL\vss\winvnc\WinVNC.cpp : message 275 recieved
D:\ORL\vss\winvnc\WinVNC.cpp : message 84 recieved
D:\ORL\vss\winvnc\vncMenu.cpp : usernames : old="", new=""
Thu Jan 24 21:22:15 2002
D:\ORL\vss\winvnc\WinVNC.cpp : message 275 recieved
D:\ORL\vss\winvnc\vncClient.cpp : non-shared connection - disconnecting old
clients
D:\ORL\vss\winvnc\vncServer.cpp : KillAuthClients() done
D:\ORL\vss\winvnc\vncDesktop.cpp : initialising desktop handler
D:\ORL\vss\winvnc\vncDesktop.cpp : KillScreenSaver...
D:\ORL\vss\winvnc\vncDesktop.cpp : bitmap dimensions are 640 x 480
D:\ORL\vss\winvnc\vncDesktop.cpp : created memory bitmap
D:\ORL\vss\winvnc\vncDesktop.cpp : got bitmap format
D:\ORL\vss\winvnc\vncDesktop.cpp : DBG:display context has 1 planes!
D:\ORL\vss\winvnc\vncDesktop.cpp : DBG:memory context has 1 planes!
D:\ORL\vss\winvnc\vncDesktop.cpp : DBG:used/bits/planes/comp/size =
0/4/1/0/153600
D:\ORL\vss\winvnc\vncDesktop.cpp : attempting to enable DIBsection blits
D:\ORL\vss\winvnc\vncDesktop.cpp : unable to enable fast blits
D:\ORL\vss\winvnc\vncService.cpp : SelectHDESK to Default (40) from
40D:\ORL\vss\winvnc\vncService.cpp : SelectHDESK failed to close old desktop
40 (Err=170)
D:\ORL\vss\winvnc\VSocket.cpp : closing socket
D:\ORL\vss\winvnc\vncDesktop.cpp : killing screen server
D:\ORL\vss\winvnc\vncDesktop.cpp : failed to ReleaseDC
D:\ORL\vss\winvnc\vncServer.cpp : Authenticated() done
D:\ORL\vss\winvnc\vncServer.cpp : RemoveClient() done
D:\ORL\vss\winvnc\vncClient.cpp : ~vncClient() executing...
D:\ORL\vss\winvnc\vncClient.cpp : deleting socket
D:\ORL\vss\winvnc\WinVNC.cpp : message 84 recieved
D:\ORL\vss\winvnc\vncMenu.cpp : usernames : old="", new=""
D:\ORL\vss\winvnc\WinVNC.cpp : message 1027 recieved
D:\ORL\vss\winvnc\WinVNC.cpp : message 1028 recieved
Thu Jan 24 21:22:20 2002


-
----------------------------------------------------------------------------
-
- -------------------------

------------------------------

Date: Thu, 24 Jan 2002 22:16:12 +0000 (GMT)
From: "Scott C. Best" <sbest "at" best.com>
Subject: Re: Tools like VNC Commander 

Alex:
	Heya. Yes, I've something very much like ActiveX on my
things-to-do list. I want to move Kaboodle out of its tight
MFC ties, though, and into wxWindows so it's portable to, well,
anywhere. This means I'd approach it more like VNC, by having
Kaboodle deliver a signed applet.

	That is, of course, presuming you're not an ActiveX
coder with lotsa time on his hands. :) The developer links on
www.kaboodle.org should be all working.

	Thanks for the suggestion in any case. I tell ya, this
software support stuff is a lotta work...

- -Scott

> Looks interesting.
>
> ANy possibility of implementing some sort of ActiveX support so it can
> be used via a control embedded in a web page or HTA?
>
> - ----- Original Message -----
> From: "Scott C. Best" <sbest "at" best.com>
> To: <vnc-list "at" uk.research.att.com>
> Cc: <Jean-Pierre.Verheecke "at" chru-strasbourg.fr>;
<kaboodle-user "at" lists.sourceforge.net>
> Sent: Tuesday/2002 January 22 03:09
> Subject: Re: Tools like VNC Commander
>
>
> : JPV:
> : Hello! Please have a look here:
> :
> : http://kaboodle.sourceforge.net
> :
> : Just posted a beta release, version 0.75 of Kaboodle, a
> : LAN management app with a "personal VPN" capability. It's got
> : VNC-Commander-like oversight of VNC servers on your LAN, and
> : includes the auto-detection and icon-support you asked about
> : (version 0.76 will have 6 more device icons types added).
> :
> : I've only been working on this app for about 2 years,
> : so be gentle with any feedback. :) Eager for any suggestions,
> : of course.
> :
> : cheers,
> : Scott

------------------------------

End of vnc-list-digest V1 #1422
*******************************

To stop receiving this digest, mail majordomo "at" uk.research.att.com
with the line 'unsubscribe vnc-list-digest' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
To unsubscribe, mail majordomo "at" uk.research.att.com with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------