ary 01 16:52
Subject: Re: integrated remote control front end for VNC, pcAnywhere,
RDP, Citrix
: On Thu, Jan 31, 2002 at 01:06:58AM -0500, Alex Angelopoulos wrote:
: >
: > I also am on a hunt for "other" remote control clients and tools
which
: > have an ActiveX control ava
I hate to politicize things, but re the ZoneAlarm stuff there's
something I've been thinking of. Products which are not commercial
(such as VNC) tend to be neglected by any software OEMs I think,
possibly due to the fact that there isn't another corporate entity which
will say nasty things on it'
I don't have all the info on this handy, and I'm working from memory of
how the process works in theory, but I can supply you with something to
get started on I think.
I believe what actually has to happen is that the remote client will
connect to the Linux host using the standard SSH port, then
Per what Tim says, I can confirm that they message you are getting
translates into "there is no VNC service talking to me on that port."
- Original Message -
From: "Tim Waugh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday/2002 February 03 17:56
Subject: Re: vncviewer doesn't pr
It's a Linux system, and the keys are different from Windows VNC it
turns out.
Normally it appears that he should be using the "vncserver" script to
start it up. You should change the vncserver launch to:
vncserver -localhost
to require connections come from localhost only.
- Original Mes
Here's what the Platforms list reports:
ftp://bfs.riken.go.jp/pub/vnc/
ftp://unixos2.org/pub/unix/internet/vnc/
If that fails, you may want to do a Google search using both "OS2" and
"VNC"; there are lots of projects that work but never get around to
having themselves added to the VNC website. A
You might try logging the connection, also - on both ends. Details are
in the documentation for Windows VNCViewer and WinVNC server if you
follow the "intouch" link at bottom and go to the Documentation page.
- Original Message -
From: "Peter Woo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTE
Bruno - could you post the registry key you changed, just as a
double-check?
Here's what I see checking the documentation - which I think you already
did.
RemoveWallpaper
Indicates whether or not WinVNC should remove the user's background
wallpaper when an incoming connection is made. It is nece
don't have this information.
:
: As I know the "Policy: DontDispBackground" (that has been set to 1)
: has been restored to value 0 (before the test).
:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Sys
tem\DontDispBackground
:
: Bruno
:
: Alex Angelopoulos wr
After having gone through the documentation a few times, Michael, I would have
to say that the method currently used for configuring many things in WinVNC is
internally self-consistent and logical - and in practice is difficult enough
to apply that as you say, " Sometimes it works, mostly it does
I think SSH is the best route to go in general, for a few reasons.
(1) If you set up application A to run over SSH, when people start worrying
about B through Z it's simple to plug in.
(2) From what I understand, you make almost anything run over SSH. (Take that
with a chunk of salt, though - I'
ling a 'howto'. As I mentioned before, I would
: love to document this process, but I, as many others before me, have not
: much of a clue as to where to begin on this journey.
:
: Thanks
:
: Jeff
:
: Alex Angelopoulos wrote:
:
: > I think SSH is the best route to go in general, for
You get a real blue-screen crash? What is the faulty driver shown?
- Original Message -
From: "fd.brouwer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday/2002 February 06 08:09
Subject: NT crash when no user is logged in
: We use VNC in a NT4 network. When we try to connec
It means:
The VNC server version they have appears to work more efficiently - it makes
use of resources (such as MMX capabilities) for encoding video being sent
which should make it a little lighter. The JPEG compression means it should
take up less bandwidth on the wire. The rest of it sounds l
All of which goes to underscore my astonishment that an essentially
cross-platform client and server together weigh in sizewise at about a quarter
of what typical "competitive" products do...
- Original Message -
From: "James ''Wez'' Weatherall" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
What is the OS of the server? Assuming it's a Windows system, the answer is in
the documentation (although I had to have it shoved in my face before I
noticed...)
This is from the WinVNC server documentation page -
http://www.uk.research.att.com/vnc/winvnc.html
(1) Find this registry key on the
Rob,
could you double-check the setting in your registry again?
The reason I ask is that I *have* seen cases where some registry settings are
not correctly preserved (and theoretically I suppose there might even be cases
where VNC might not have permission to read it).
In any case, if it isn't w
You can also usually do this via an added . I don't expect to see it
"fixed" since it isn't really "broken". The problem is that your local
system typically hooks events from special key combinations, and passing
keystrokes has to depend on various workarounds.
You can pass Ctl-Alt-Del on Wind
What's the video driver setup you have?
I would say that your problem is the SiS 6326 off the top of my head, but I
can't claim to have "Regression-tested" the idea - just had a couple of bad
experiences with that series of SIS cards. On reboot, what kind of error
mesages do you have in the log
- Original Message -
From: "Adrian Umpleby" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday/2002 March 05 09.01
Subject: Re: Right-clicks from a Mac
: >I'm VNCing to a Windows machine from a Mac, and can't find a way of
: >sending right-clicks.
:
: It depends which VNC client y
:
: I would have only thought it would be a problem if the VNC window was on
the
: SIS card? Also I haven't had any other trouble with the card with other
: apps. (Plus it worked in 98)
:
: > On reboot, what kind of error
: > mesages do you have in the log (if any prior to the generic "unexpected
Please, do Stacy.
- Original Message -
From: "Stacy D. Coil" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday/2002 March 05 11.15
Subject: Re: Hardware Version of VNC
: FYI,
:
: I will be taking a look at this product today to see if this will be a good
: fit for our "lights
One of the annoyances of VNC is what it is.
The issue goes back to the fact that implementing a central password system
for Windows systems (or a remotely changeable one) would have required all
sorts of (potentially unreliable) additions. So the same issue applies across
the board to standard VN
saved, so I don't think it can be done with a policy editor.
:
: Jake
:
: -Original Message-
: From: Alex Angelopoulos [mailto:[EMAIL PROTECTED]]
: Sent: Tuesday, March 05, 2002 1:47 PM
: To: [EMAIL PROTECTED]
: Subject: Re: tightvnc vs "loose" vnc
:
:
: One of the annoya
Unfortunately, I believe that is Windows refusing the connection when you
shutdown - and you are right, it is incredibly annoying.
- Original Message -
From: "Matt Swift" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday/2002 March 05 17.46
Subject: shutdown gotcha with Win32 hos
??!!
I see what you're saying; I'm checking this out now.
- Original Message -
From: "Rob Kenyon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday/2002 March 05 20.21
Subject: RE: WinVNC & -nevershared
: I did.
:
: I can honestly state that I actually read the docs before post
Yep.
I can confirm.
Registry setting ConnectPriority 2 on the server.
Client A connects.
Client B attempts to connect, and has the connection instantly closed.
Client B then attempts to connect AGAIN, specifying the /shared switch - and
successfully connects, making it a shared session.
---
I did another run, attempting a /noshared switch on Client A, setting loglevel
to 11.
Client B can still connect by specifying /shared. A's client log shows no
traces of anything - not even any bobbles that could be used as a *clue* that
another session was attempted.
- Original Message
elf.
:
: It's funny that given all the security concerns that are flowing around
: VNC (tunnelling and handshaking and all that) that something that is so
: easy to do on WinVNC isn't seen as a risk.
:
: I guess I could probably pull the source and look for myself to see...
:
: Rob
:
: ---
One of the joys of free enterprise. :)
- Original Message -
From: "Rob Kenyon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday/2002 March 06 08.34
Subject: RE: WinVNC & -nevershared
: Thanks for your help and analysis on this, Alex. Time to talk to my
: customer and see wha
That explains something I've seen, I think. Comments on the shutdown process
would be appreciated...
I have noted a couple of systems which have had historical problems with
shutdown; after VNC is installed on them, I've had some confusing experiences
where I attempt to connect after a (failed)
I think the "big" depends on context. What it *does* do is underscore the
issues in the current security model of VNC as it is implemented on Windows.
I think if Rob can come up with a patch to make it accept a -nevershared it
_will_ shut down a significant vulnerability in the current model. T
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 Windows admin
he best thing is that Group Policy can be an afterthought - I've
: included an ADM file that shows the basic idea. It doesn't work just yet
: (I need to figure out why), but you should get the idea.
:
: Andrew
:
: -Original Message-
: From: [EMAIL PROTECTED]
: [mailto:[EMAIL PROTECTE
n VS.Net was going to be
: useful for something.
:
: Andrew
:
: -Original Message-
: From: [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
:
Ah - you're just thinking about VNC COMability...
Thong's implementation is a really good starting point, I think. He exposed
darned near every element of VNC to automation; not just the connection
process, but screen positioning, etcetera. I'm including the
methods/properties/events list at th
I don't know about that, Rich. After all, if you know that you can use telnet
for anything, what else do you need to know? :)
- Original Message -
From: "Richard Clegg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday/2002 March 07 04.11
Subject: RE: connect to vnc via internet
: From: [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
I have an ADM from Andrew and I've pulled Daniel Quinlan's ADM file from the
Internet and have started messing with those to see what pieces may need to be
added to cover everything that is in the documentation.
Is there anything anyone would like to point out that I should be aware (or
beware) o
DUH! You can't set a binary value from Poledit. And Jacob politely resisted
contradicting me...
- Original Message -
From: "Alex Angelopoulos" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday/2002 March 05 16.07
Subject: Re: tightvnc vs "lo
with the repercussions of "tattooing" the registry.
You can't "undo" policy changes done via NT4-level ADM files per se.
- Original Message -
From: "Alex Angelopoulos" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday/2002 March 08 04.1
FYI -
If you try the test Andrew shows, the real question is: do you get the Web
logon screen? If there is a problem with port 5900, you would still not be
able to connect to the server, since the applet "switches" you to 5900 after
being served.
- Original Message -
From: "Andrew Crowe"
Unfortunately, the judge in New England didn't want the full argument either
:(.
:
: They're both "Open Source" licences, but they're different in
: intent and philosophy. GPL'd stuff can't be closed off, BSD'd
: stuff can. You don't want the full argument
:
: --
: Illtud Daniel
boot process.
: >
: > I use this fairly often to reboot machines when pcanywhere chokes and
: > won't let anyone connect.
: >
: > I don't remember any good reason why vnc can't shut down last but there
: > was some discussion of it here a while ago.
:
: Andrew
:
: -Original Message-
: From: [EMAIL PROTECTED]
: [mailto:[EMAIL PROTECTED]] On Behalf Of Alex
: Angelopoulos
: Sent: Friday, 8 March 2002 9:46 PM
: To: [EMAIL PROTECTED]
: Subject: Complete NT4-level WinVNC policy template now available
:
: Almost 600 lines that covers everything
I used to have to deal with Netgear routers (primarily ISDN) on a regular
basis, but I don't recall ever doing precisely that.
One thing I *do* remember, though, is that Netgear tech support is (or was)
available 24/7, so if you don't get a better answer, you can probably call and
get a walkthrou
101 - 146 of 146 matches
Mail list logo
