Sorry, syntax error. Should be "-:+127.0.01"
-Original Message-
From: Glenn Mabbutt [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 27, 2002 3:40 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Vnc connection loop-back only
I have also had this not work. My work arou
Make sure that you are doing the SSH port forward like this:
5900:127.0.0.1:5900
and not like this:
5900:hostname:5900
--
Mike Ossmann, Tarantella/UNIX Engineer/Instructor
Alternative Technology, Inc. http://www.alttech.com/
---
I have also had this not work. My work around was to set "allow loopback
connections", as you have done, and set AuthHosts to "-:127.0.0.1", which
means VNC will only accept connections on localhost. Works just fine.
See the docs for more info on AuthHosts.
Glenn
-Original Message-
Fr
It's possible this is the second time I'm sending this, if so apologies...
Pete M
Original Message -
From: "W. Brian Blevins" <[EMAIL PROTECTED]>
> Glyn,
>
> You are not the first to report this strange behavior on Win2K. I am
> unable to reproduce the problem in our Q/A lab so far. C
On Thu, Feb 14, 2002 at 08:27:44AM -0800, Ken Dreger: Dr. D" wrote:
> Is anybody using VNC to connect to a OS/2 system ???
> and if so, HOW PLEASE ??
Xvnc works on OS/2. You can remote access OS/2 via X based programs.
There's no PM VNC server yet. I heard WinVNC works as PM VNC server
under
Glyn,
You are not the first to report this strange behavior on Win2K. I am
unable to reproduce the problem in our Q/A lab so far. Could you provide
some more details?
1- What OS are you using? Win2K Server, Advanced Server, Pro?
2- Do you have terminal services installed? Running?
3-
: "Richard Clegg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 14, 2002 8:23 AM
Subject: RE: VNC connection dies
> It's well documented that if you run ZoneAlarm on a W2K machine, then this
> can cause blue screen of death (which is incredibl
Okay I have found the link to sort it all out now
http://www.zonelabs.com/services/support_programs.htm#5program
Thanks again
Glyn
- Original Message -
From: "Richard Clegg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 14, 2002 8:
It's well documented that if you run ZoneAlarm on a W2K machine, then this
can cause blue screen of death (which is incredibly annoying when you remote
to it). There seems to be no cure for it, but I've not had your problem
yet.
I would suggest (just as a trial to be absolutely sure) disabling
IL PROTECTED]>
Sent: Thursday/2002 January 17 15:47
Subject: RE: vnc connection problem
: You made an excellent point I never thought of... Video Driver. It's
: an older PC with integrated video, and while Win 98 was able to supply a
: nice video driver, Win 2k does not. I have an error i
ric driver that I could use that would work with VNC???
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Alex
Angelopoulos
Sent: Thursday, January 17, 2002 12:19 PM
To: [EMAIL PROTECTED]
Subject: Re: vnc connection problem
The thanks is a bit prematu
;Paul W. Mittan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday/2002 January 17 11:32
Subject: RE: vnc connection problem
: HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default
: AutoPortSelect 0x0001 (1)
: InputsEnabled 0x0001 (1)
: LocalInputsDisabled 0x (0)
]
[mailto:[EMAIL PROTECTED]] On Behalf Of Alex
Angelopoulos
Sent: Thursday, January 17, 2002 7:36 AM
To: [EMAIL PROTECTED]
Subject: Re: vnc connection problem
Not sure about this - it sounds like it accepts your password, then sees
another problem.
Could you please post the following two registry keys
Not sure about this - it sounds like it accepts your password, then sees another
problem.
Could you please post the following two registry keys from the Win2K server which
disconnects you?
HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default
HKEY_CURRENT_USER\SOFTWARE\ORL\WinVNC3
They will both be
Hi Graham,
Are you running WinVNC on a Windows 2000 Workstation or Server?
I have no problems running it off a Windows 2000 Workstation but when
run off a Windows 2000 Server, I get the "Connection Closed" message.
The service "VNC Server" starts without a hitch on this Windows 2000
Server.
Re
>I'm running Windows 2000 sp 2 as the vnc server with v3.3.3 r9.
>
>Other machines can connect fine using the viewer, however if I lock the
>computer every connect attempt gets the following:
>
>VNC authentication succeeded
>vncviewer: VNC server closed connection
>
>Is this a known issue and i
fyi
I did not see this come through the list the other day, so I thought I
would resend it. This code snippet corrects the vnc hand freeze on
the windoze viewer.
James,
One of the folks in our lab, John Fuenning, fixed this problem by adding
an additional line
You are running the server in application mode. You must run it as a
service. It will never have worked this way as an application.
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T
l : 766513
AT&T Labs Cambridge, UK - Tel : 343000
- Original Message -
From: "David Lankford" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 30, 2001 10:10 PM
Subject: RE: VNC Connection Freezes / Drops
> Ja
;'Wez'' Weatherall [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 7:27 AM
To: [EMAIL PROTECTED]
Subject: Re: VNC Connection Freezes / Drops
OK. Is it possible for you to configure the VNCviewer to output its debug
information to a console window? (As documented on the VNC do
James says,
"This is very useful to know, but not entirely trivial to fix."
---
One, possibly trivial, way to fix this would be to change the behavior
(or display) of the 'fullscreen' checkbox on the viewer popup menu that
results from a right click on the toolbar host session icon.
Here a
- Tel : 343000
- Original Message -
From: "Mark Harris" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 29, 2001 11:43 PM
Subject: Re: VNC Connection Freezes / Drops
> hi James,
>
> We can reproduce this problem. This not
/2001
05:02 PM ---
Mark Harris
05/23/2001 01:41 PM
To: [EMAIL PROTECTED]
cc:
From: Mark Harris/Rochester/IBM@IBMUS
Subject: Re: VNC Connection Freezes / Drops (Document link: Mark Harris)
> Over some time, something happens between the viewer and the server,
On Fri, 25 May 2001, David Lankford wrote:
> Update: I am now getting the Runtime Error even when I use the non-shared
> re-initiation of the session.
>
> Other Information:
>
> I didn't state this before, but the runtime error is a Microsoft Visual C++
> Runtime Library error message.
Ca
Jason says,
"Double click on the VNC server icon in the system tray. Check the box that
states "poll full screen".
---
I checked the "poll full screen" box and am testing now.What other
boxes do you have checked.I have unchecked all other polling boxes and
only have the "poll full sc
error message, an
similar error message is encountered.
David
-Original Message-
From: David Lankford [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 25, 2001 12:45 PM
To: '[EMAIL PROTECTED]'
Subject: RE: VNC Connection Freezes / Drops
Ok,
Connection Freezes, Reopen Shared M
ves more clarification to the situation.
Thanks for your help,
David Lankford
-Original Message-
From: James ''Wez'' Weatherall [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 7:24 AM
To: [EMAIL PROTECTED]
Subject: Re: VNC Connection Freezes / Drops
OK. What affect
That has been done.
-Original Message-
From: Jason Hatter [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 24, 2001 11:46 AM
To: [EMAIL PROTECTED]
Subject: RE: VNC Connection Freezes / Drops
> Jason,
> Where do you check "poll full window" ?
Double click on the VNC se
> Jason,
> Where do you check "poll full window" ?
Double click on the VNC server icon in the system tray. Check the box that
states "poll full screen".
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [E
t;David Lankford" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 23, 2001 7:58 PM
Subject: RE: VNC Connection Freezes / Drops
> VNCviewer is running on a WinNT4 machine and the WinVNC (App Mode) is
> running on a Win2k Pro system.
>
> Version 3.3.3r9
Sent: Wednesday, May 23, 2001 8:07 PM
Subject: RE: VNC Connection Freezes / Drops
> James,
>
> The VNCviewer that freezes (in our case) is a Windows 2000 box.
> VNCserver is running on an NT box.The symptom is that the cursor
> (mouse) freezes on the vncviewer window, onl
James,
The VNCviewer that freezes (in our case) is a Windows 2000 box.
VNCserver is running on an NT box.The symptom is that the cursor
(mouse) freezes on the vncviewer window, only allowing us to move the dot.
We can move up and close the vncviewer window and restart the viewer and
continue
longest time before a freeze has been 3 minutes.
David
-Original Message-
From: James ''Wez'' Weatherall [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 23, 2001 1:27 PM
To: [EMAIL PROTECTED]
Subject: Re: VNC Connection Freezes / Drops
> In my initial request, I sta
Jason,
Where do you check "poll full window" ?
Thanks
Mark H. Harris <><
Staff Software Engineer
Software Tools Development - IBM Rochester, MN
iSeries Dept EL8Y/664-3 E115
[EMAIL PROTECTED] (8) 456-6910 1-507-286-6910
-
> Over some time, something happens between the viewer and the server,
and
> one or the other will hang. In our case, closing the windows and
> reestablishing the connection gets us going again. Time before the hang
> varies, but is definitely not network related. Something else is going
> o
I have seen this happen when using vnc between win2k boxes. I am controlling
a dozen or so servers from a laptop w/ wireless lan connectivity. Anytime a
new server is put into place I will tweak it and monitor it using vnc. After
it is in production for a couple of days we will send it to its dest
> In my initial request, I stated the paragraph below. In this instance,
the
> connection does not automatically cause the viewer to close, it just
freezes
> the connection requiring that the connection be manually closed.
>
> " 2. Frequently, the cusor will freeze and the connection will nee
y 23, 2001 12:58 PM
To: [EMAIL PROTECTED]
Subject: Re: VNC Connection Freezes / Drops
> From: "James ''Wez'' Weatherall"
> > This sounds like an issue with your network.
>
> you can call these "network issues" but it is tcp after all and packets
> Over some time, something happens between the viewer and the server, and
> one or the other will hang. In our case, closing the windows and
> reestablishing the connection gets us going again. Time before the hang
> varies, but is definitely not network related. Something else is going
>
> From: "James ''Wez'' Weatherall"
> > This sounds like an issue with your network.
>
> you can call these "network issues" but it is tcp after all and packets do
> get lost.
TCP is designed to retransmit lost packets and to drop connections if packet
loss prevents data being transferred, which
James says,
"This sounds like an issue with your network."
-
Nope. We have reproduced this behavior between two boxes (NT W2K) that are
on the same ring... that is, we aren't even making two hops; we never hit
a router or bridge.
In our case the machines are using token ring; however, t
>you can call these "network issues" but it is tcp after all and packets do
>get lost.
Ummm... UDP is the unreliable protocol family. TCP has guaranteed in-order delivery
of all packets. If that guarantee is broken, the connection is supposed to be
severed. If you are actually losing TCP pa
From: "James ''Wez'' Weatherall"
> This sounds like an issue with your network.
Sorry James, it does happen. especialy in the followings:
if there is high CPU load on the server,
if the server side is very low memory,
if the connection speed is 56k and below.
if there are more than about 20 hoops
On Tue, 22 May 2001, David Lankford wrote:
> Relatively new to VNC (great product) and I am not sure if this is the
> correct place to ask this question, but I am experiencing the following
> problems.
>
> VNC Version: 3.3.3r9
> Connection: WinNT4 SP6 to Win2K
>
> 1. Periodically the connecti
We also have noticed this same behavior between NT and W2K. I am
interested in the feedback. Thanks.
Mark H. Harris <><
Staff Software Engineer
Software Tools Development - IBM Rochester, MN
iSeries Dept EL8Y/664-3 E115
[EMAIL PROTECTED] (8) 456-6910 1-507-286
The solution to my problem with Connection Refused under Windows 2000:
I was using Jeremy Peaks amended version of WinVNC 3.3.3r7, release 3.
When I had the system set up and logged in (1024x768 with 16 bit color
resolution, no wallpaper, WinVNC running as a service with default password
set)
You must not have read the message completely. I did set the default
password, and make sure the current user settings in the registry where
located in the local machine settings.
But I did find the answer and will be posting it to the list.
At 08:50 PM 3/5/2001, you wrote:
> >Both servers ru
>Both servers run VNC as a service and I have set the default password for
>the service. The app and service was installed under the Administrator
>account and function fine when a user is logged into the system. If no one
>is logged in, I get a "Connection Refused" message after attempting to
>
I had the same problem after installing -
I don't know how - but after rebooting and making sure it was installed as a
service - it worked ? Maybe try a reboot ? Don't know - If you find the real
answer - let me know !
Thanks.
-Original Message-
From: Shawn Gimbert [mailto:[EMAIL PROTE
If you want to set up a modem or ISDN based firewall/router solution, check
out Smoothwall. Its idiot proof to set up, and will run on a basic 486, or
indeed a laptop (thats a good idea that!). Its Linux based, and you get a
web front end, which you access from the rest of your network, to dial ou
Avishay & Orna wrote:
>
> Hi
> I would like to control my mother's WIN ME machine from my WIN NT machine.
> Our computers are not connected.
> I understand that a TCP/IP connection should be established in order to use
> VNC.
> If both machines will be connected to the internet on the same time w
Yes as logon WinVNC is running in server mode on one of the machines and the
person who is running in server mode tells the other their IP address you
should be able to connect over the internet. WinVNC will run a little slow
over a phone modem connection though.
-Original Message-
From:
You'll be able to use VNC as long as you know the IP address of the target
machine, and as long as it's not behind some weird firewall at your ISP.
Hover the mouse over the VNC Server system tray icon, get the IP from the
tooltip that pops up, and you should be away.
--
Ian Cowley
Comp. Service
53 matches
Mail list logo
