t; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, 2002-03-27 14:18
Subject: Windows VNC
> I have read the FAQ's and understand the NO multi user function, my
> questions:
>
> 1. Could the VNC Server Service be modified to run similar to Citrix?
>
On Wed, Mar 27, 2002 at 01:18:19PM -0600, Roger Mihalko wrote:
>
> 1. Could the VNC Server Service be modified to run similar to Citrix?
In theory, yes. The following post ("Shared WTS Sessions Using VNC" by
Bill Anglea) is the state of the art:
http://www.uk.research.att.com/vnc/archives/20
I have read the FAQ's and understand the NO multi user function, my
questions:
1. Could the VNC Server Service be modified to run similar to Citrix?
2. Or could or are there plans to Modify the VNC server service to run off a
webbrowser, which
might be setup to run a desktop, similar to the UROA
WinVNC service I get errors.
I have not completed my testing, so maybe I will get it to work someday...
Chris Tesla
>
> - Original Message -
> From: "Steve Bostedor" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday/2002 March 07 12.18
&g
/2002 March 07 12.18
Subject: RE: RFC - Windows VNC server configuration issues
: Alex, do you mind testing something for me? I have a MSI file that I put
: together that does a silent install of VNC on a Windows 2000 computer. You
: could possibly deploy it with group policies. Do you want to giv
Message-
From: Andrew van der Stock [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 06, 2002 9:11 PM
To: [EMAIL PROTECTED]
Subject: RE: RFC - Windows VNC server configuration issues
Alex,
Group policy and make the product deployable using assigned software
policies.
This is how you can
ED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday/2002 March 07 04.27
Subject: RE: RFC - Windows VNC server configuration issues
: I wasn't really aiming at making a .NET framework conversion - the
: WinVNC source is not written in MFC, so there's only a minor amount of
: benefit to a
nd, but many on here would.
Andrew
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Alex
Angelopoulos
Sent: Thursday, 7 March 2002 7:33 PM
To: [EMAIL PROTECTED]
Subject: Re: RFC - Windows VNC server configuration issues
I'm dabbling in .NET, but I h
Andrew van der Stock" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday/2002 March 07 03.14
Subject: RE: RFC - Windows VNC server configuration issues
: Are you thinking of exposing VNC to COM+ automation?
:
: Please say yes! :-)
:
: I knew that shiny new ATL Project wizard i
useful...
- Original Message -
From: "Andrew van der Stock" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday/2002 March 06 21.10
Subject: RE: RFC - Windows VNC server configuration issues
: Alex,
:
: Group policy and make the product deployable using as
: Thursday, 7 March 2002 11:44 AM
To: [EMAIL PROTECTED]
Subject: RFC - Windows VNC server configuration issues
[snip]
What I would like to do is develop a simple scripted front-end method of
easing VNC tasks for Windows admins. Although some things cannot be
addressed easily via scripted solutions, I do
om: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Alex
Angelopoulos
Sent: Thursday, 7 March 2002 11:44 AM
To: [EMAIL PROTECTED]
Subject: RFC - Windows VNC server configuration issues
I'm not using RFC in the colloquial sense, here. I just want to get a
concept
about the issues that
I'm not using RFC in the colloquial sense, here. I just want to get a concept
about the issues that others see with configuring Windows VNC servers -
deployment, securing, and maintaining.
What I would like to do is develop a simple scripted front-end method of
easing VNC tasks for Wi
]
Subject: RE: Providing (Windows) VNC support to clients that have strict
corporate firewalls
Thanks. The "permitopen" option works really well on the sshd. The only
way I seem to be able to get around the loopback restriction is by running
the ssh client on an intermediate mac
PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Providing (Windows) VNC support to clients that have
strict...
Chuck:
Heya. You've probably already discovered this, but there's
a registry setting you need to make to your VNC server machine to
allow loopback:
al Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael Ossmann
Sent: Wednesday, January 16, 2002 3:26 PM
To: [EMAIL PROTECTED]
Subject: Re: Providing (Windows) VNC support to clients that have strict
corporate firewalls
On Wed, Jan 16, 2002 at 02:40:16PM -0500
Chuck:
Heya. You've probably already discovered this, but there's
a registry setting you need to make to your VNC server machine to
allow loopback:
http://www.uk.research.att.com/vnc/winvnc.html
Down at the bottom, AllowLoopback. Or, even more aggressive,
try LoopbackOnly
of
dword: loopbackonly and set it to 1.
Steve
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Chuck Renner
Sent: Wednesday, January 16, 2002 2:40 PM
To: [EMAIL PROTECTED]
Subject: RE: Providing (Windows) VNC support to clients that have strict
corporate
On Wed, Jan 16, 2002 at 12:46:54PM -0800, [EMAIL PROTECTED] wrote:
> There is a documented setting in the VNC Server to allow internal loopback
> connections. I don't remember what it is offhand, but it is described in
> the section detailing how to create a secure connection.
The problem he ran
ED]]
> Sent: Wednesday, January 16, 2002 12:26
> To: [EMAIL PROTECTED]
> Subject: Re: Providing (Windows) VNC support to clients that
> have strict
> corporate firewalls
>
>
> On Wed, Jan 16, 2002 at 02:40:16PM -0500, Chuck Renner wrote:
> >
> > Since VNCviewer st
On Wed, Jan 16, 2002 at 02:40:16PM -0500, Chuck Renner wrote:
>
> Since VNCviewer states, "Internal loopback connections are not allowed", the
> implication is that there is a setting that WILL allow them, either in the
> source, or in the GUI settings. Is this the case?
I wasn't expecting this
ED]]On Behalf Of Michael Ossmann
Sent: Tuesday, January 15, 2002 12:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Providing (Windows) VNC support to clients that have strict
corporate firewalls
On Tue, Jan 15, 2002 at 10:10:18AM -0500, Chuck Renner wrote:
>
> WinVNC on ClientWS1 ---> SSH o
On Tue, Jan 15, 2002 at 10:10:18AM -0500, Chuck Renner wrote:
>
> WinVNC on ClientWS1 ---> SSH on ClientWS1 port 5500 --> Internet --> sshd on
> MYFirewall port 443 --> VNCviewer on MyWS1 port 5500
>
> Have I got the idea right? If so, I should be able to do this without
> recompiling VNC at al
f Michael Ossmann
Sent: Monday, January 14, 2002 3:36 PM
To: [EMAIL PROTECTED]
Subject: Re: Providing (Windows) VNC support to clients that have strict
corporate firewalls
On Mon, Jan 14, 2002 at 02:34:16PM -0500, Chuck Renner wrote:
>
> There needs to be a way to change ALL Ports used by VNC, not
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Michael Ossmann
Sent: Monday, January 14, 2002 3:36 PM
To: [EMAIL PROTECTED]
Subject: Re: Providing (Windows) VNC support to clients that have strict
corporate firewalls
On Mon, Jan 14, 2002 at 02:34:16PM -0500, Chuck Renner wrote:
>
>
On Mon, Jan 14, 2002 at 02:34:16PM -0500, Chuck Renner wrote:
>
> There needs to be a way to change ALL Ports used by VNC, not just the ports
> it listens on. Ports used for outgoing connections should be able to be
> changed both on the command-line, and through the GUI interface. Since this
>
I wish to document both a problem with WinVNC, and a solution (even though a
better solution needs to be made).
The problem:
There needs to be a way to change ALL Ports used by VNC, not just the ports
it listens on. Ports used for outgoing connections should be able to be
changed both on the co
Please send me a copy. Thanks a lot!
>From: Colin Caughie <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
>Subject: Windows VNC Viewer mod to hook Alt Tab
>Date: Tue, 13 Nov 2001 12:57:16 -
>
&
Is the patch against AT&T VNC or TightVNC? (Or will it apply cleanly to
either?) If it will apply to TightVNC, I'm interested.
-Original Message-
From: Colin Caughie [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 13, 2001 7:57 AM
To: '[EMAIL PROTECTED]'
Subject:
Attachments can not be sent through this list, but a link to download works
great.
Patrick.
>In case anyone's interested, I've made a modification to the Windows VNC
>Viewer to hook Alt-Tab keypresses and send them through to the VNC server,
>instead of letting Windows h
| In case anyone's interested, I've made a modification to the Windows VNC
| Viewer to hook Alt-Tab keypresses and send them through to the VNC server,
| instead of letting Windows handle them. This is useful when running KDE
| under VNC, since it means you can use Alt-Tab to switch b
Hello,
In case anyone's interested, I've made a modification to the Windows VNC
Viewer to hook Alt-Tab keypresses and send them through to the VNC server,
instead of letting Windows handle them. This is useful when running KDE
under VNC, since it means you can use Alt-Tab to switch b
liche Nachricht-
> Von: Jeff Koenig [SMTP:[EMAIL PROTECTED]]
> Gesendet am: Freitag, 12. Oktober 2001 18:54
> An: [EMAIL PROTECTED]
> Betreff: Windows VNC server stops taking connections after first
> session disconnects
>
> Hi,
>
> Info:
> Windows
original
port.
Hope this helps,
Cheers
Pramodh
> -Urspr|ngliche Nachricht-
> Von: Jeff Koenig [SMTP:[EMAIL PROTECTED]]
> Gesendet am: Freitag, 12. Oktober 2001 18:54
> An: [EMAIL PROTECTED]
> Betreff: Windows VNC server stops taking connections after first
> s
client will never connect to
the server anymore. I am able to ping the server but not connect to it via
vncviewer anymore.
How can I troubleshoot this? Is there a windows VNC log file to see what is
going wrong. The service on the Windows 2000 box shows that it is currently
running still.
Any
> it compiles right on CygWin, but when I try to use it against a NT4 TSE
> (pc-tse), no connection is possible, the result is :
>
> $ rdp2vnc -n My-PC -l -4 -Z 1 pc-tse
> rdp2vnc: VNC adaptor for RDP services.
> Version 1.0.0-pl19-5-10beta. Copyright (C) 1999-2000 Matt Chapman.
> See http://www.r
E-Mail : [EMAIL PROTECTED] | )
. \---/
.(_) (_)
- Original Message -
From: "Francis VIVAT" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "James ''Wez'' Weatherall" <[EMAIL PROTECTED]>
Sent: mercredi 11 juillet 2001 20:01
S
ECTED] | )
. \---/
.(_) (_)
- Original Message -
From: "James ''Wez'' Weatherall" <[EMAIL PROTECTED]>
To: "VNC-LIST" <[EMAIL PROTECTED]>
Sent: mercredi 11 juillet 2001 13:03
Subject: Re: Multiuser Windows VNC
> > Of sorts - see http://services.simac.be/vnc
> Of sorts - see http://services.simac.be/vnc - the page is slow loading for
> me right now. Also, I think someone made a proxy server of sorts that
> proxies VNC to RDP, useful if you already have a Metaframe server, but
> ultimately want to use VNC clients. Sorry, can't find the link right
now
Right on the money, thanks. I hope they fix this. I do not notice the
problem with Win9X clients. Just the Win2K.
-Original Message-
From: Howlett, Simon (NESL-IT)
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 16, 2001 4:15 AM
To: '[EMAIL PROTECTED]'
Subject: RE: windows
PROTECTED]
Subject:windows vnc kills wallpaper
Hi, I tried everywhere to find the solution to this. I am running Win2k
Pro as a VNC server. If I connect to this computer the wallpaper is
displayed in the remote window, but is killed after disconnect. I need
the wallpaper to remain unchanged. I use
Hi, I tried everywhere to find the solution to this. I am running Win2k
Pro as a VNC server. If I connect to this computer the wallpaper is
displayed in the remote window, but is killed after disconnect. I need
the wallpaper to remain unchanged. I use VNC to shadow sessions that are
not WTS and I
The VNC 3.3.3R8 Windows package introduced version 3.3.3R3 of the Viewer. I
cannot find any information about the changes from the 3.3.3R2 Viewer. If
anyone knows, please enlighten me.
Thanks in advance!
-
To unsubscribe, send
AT&T Laboratories Cambridge is pleased to announce release 3.3.3r9 of the
Windows VNC package.
This release includes some important bug fixes introduced in the R8 WinVNC
server, and fixes the AuthHosts bug introduced in that release.
For more details please see the VNC web pages at
At 04:30 PM 3/15/01 -0800, you wrote:
>AuthHosts filter now behaves correctly. I wonder will this now work like
>entering this 192.168.1.1, but matching 192.168.1.1, 192.168.1.10, and 100
>or just .1? I wish I could enter masking too like 192.168.1.64/26 (26 =
>255.255.255.192 right?). This may no
The 3.3.3r8 Windows binary zipfile on the website should now have the
correct version of vncviewer, which is 3.3.3R3, not R2a. The source package
always had this version.
I'm sure people will let us know of any other problems :-)
Cheers
Tristan
-
"James
- Original Message -
From: "Freddy Jensen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, March 16, 2001 6:08 AM
Subject: Re: Windows VNC package updated to 3.3.3r8
> I didn't see any response to the question about
el : 766513
AT&T Labs Cambridge, UK - Tel : 343000
- Original Message -
From: "Freddy Jensen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, March 16, 2001 6:08 AM
Subject: Re: Windows VNC package upd
I didn't see any response to the question about the
viewer version. The old viewer version is 3.3.3 R2
and the new version is 3.3.3 R2a.
Should we stick with the old version or use the new
one?
Thanks
Freddy
-
To unsubscribe,
security everywhere, maybe too much sometimes, got to let people work too I
guess.
-Original Message-
From: Tristan Richardson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 15, 2001 11:50 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Windows VNC package updated to
A minor nit?
The previous Win32 vncclient reports 3.3.3R3.
This new version reports 3.3.3R2a.
FYI.
Raye.
> AT&T Laboratories Cambridge is pleased to announce release 3.3.3r8 of the
> Windows VNC package.
>
> This release has some important bug fixes to the WinVNC server, p
AT&T Laboratories Cambridge is pleased to announce release 3.3.3r8 of the
Windows VNC package.
This release has some important bug fixes to the WinVNC server, plus some
minor enhancements.
For more details please see the VNC web pages at
http://www.uk.research.att.com/vnc
in partic
52 matches
Mail list logo
