Jim O'Brien wrote:
I downloaed the lastest version of the Free VNC.
The server is installed on Windows Vista Home Premium.
The client is installed on Windows XP Pro
When I attempt to connect I get a message box with "read: Connection
aborted(10053) Do you wish to reconnec
I downloaed the lastest version of the Free VNC.
The server is installed on Windows Vista Home Premium.
The client is installed on Windows XP Pro
When I attempt to connect I get a message box with "read: Connection
aborted(10053) Do you wish to reconnect to :5900"
If I click &quo
bonjour
Ce message pour priciser que j'ai bien cochi, comme dit, dans le Viewer l'option
Rate-limit mouse move events" sans que ga apporte de solution ` mon problhme
dicrit par ailleurs.
Merci de votre aide dont j'ai bien besoin.
Francois
___
VNC-List
hello
I am back with this ugly connection problem which is still there, now that I can
run the connection again.
Allow me to draw again the complete picture; I run 2 VNC connections :
- a + remote ; connection
- a + local ; connection
The remote one goes between my own PC and my mothers PC via
hello James
Thank you first for your long and complete answers.
To draw a quick picture of my VNC connexions:
- my PC: on a WiFi local network, down to a WiFi router, down via Ethernet to a
DSL box, a ZoneAlarm firewall
- my wife's PC: on the same WiFi network, the WinXP fw
- my mother's PC: beyo
Just an idea: is there any energy saving stuffs activated in that
computer? Well, normally, that's not a problem. My remotely controlled
PC's all have screen-savers activated and monitors shut off after n
minutes. However, none of them has the hard-drive stop after a period
of time. Do you
s at fault. In these situations we find that the "Rate-limit mouse move
events" works around the problem.
Cheers,
Wez @ RealVNC Ltd.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
> Sent: 30 January 2007 21:
Sent: 29 January 2007 19:13
> To: vnc-list@realvnc.com
> Subject: Read: connection aborted (10053)
>
> hello Mick
>
> Thank you very much for your long documented message; let me
> try to move the
> subject forward again.
>
> I would like to start by saying tha
[EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
> Sent: 29 January 2007 18:18
> To: vnc-list@realvnc.com
> Subject: Read: connection aborted (10053)
>
> hello James
>
> A quick question related to your post: in my VNC Server
> Properties Input
hello
Here is one more info on this problem.
I just set up another remote VNC connection between my PC with a another PC
(different from the one I usually connect to) with this result (so far):
- the connection is alive after more than an hour (while my usual remote VNC
connection does not last m
hello James
A quick question related to your post: in my VNC Server Properties Input tab, I
don't have the "Pointer event rate-limiting" you talk about.
The nearest I have is "accept pointer events from clients"; my VNC version is a
4.1.2 Windows one.
Thank you for your help.
Francois
_
hello Mick
Thank you very much for your long documented message; let me try to move the
subject forward again.
I would like to start by saying that my testing capabilities are not that great
since I can't really count on my 88 year old mother (the VNC Server micro) to
help me out; things tend to
On Wednesday 24 January 2007 20:39, [EMAIL PROTECTED] wrote:
> hello Mick
>
> Port below 1024: I read somewhere that some providers, at least in France,
> tend to squeeze ports above 1024 for traffic control reasons, thus I tried
> doing so to avoid being sqeezed.
All your internet applications op
PROTECTED] On Behalf Of [EMAIL PROTECTED]
> Sent: 24 January 2007 20:39
> To: vnc-list@realvnc.com
> Subject: Read: connection aborted (10053)
>
> hello Mick
>
> Port below 1024: I read somewhere that some providers, at
> least in France, tend
> to squeeze ports above 1024
hello Mick
Port below 1024: I read somewhere that some providers, at least in France, tend
to squeeze ports above 1024 for traffic control reasons, thus I tried doing so
to avoid being sqeezed.
Question: how does this relate with your remark about open ports and admin
rights?
Restart every hour:
hello
Let me add that I looked into the Line speed estimate for my 2 VNC connections:
- the remote DSL connection: 770 kbits/s (has the 10053 problems)
- the WiFi connection: 1370 kbit/s (works perfectly)
found into the VNC Connection Info panel.
Would anyone see any clue relating the 770 kbit/s
; scheme.
>
> The message is always the same : Read: Connection aborted (10053)
There's a setting dis/allowing multiple connections to the server - check that
it has been set correctly for your needs.
--
Regards,
Mick
[demime 1.01d removed an attachment of type application/pgp-signa
another PC on my WiFi network, with no trouble at all, for
a long time.
On the reverse, my remote VNC connection keeps breaking down every hour after a
duration between 10-12 minutes and 30-35 minutes with no identified scheme.
The message is always the same : Read: Connection aborted (10053
On Friday 12 January 2007 16:45, [EMAIL PROTECTED] wrote:
> hello
>
> Here is my answer to the asked question:
> my 2 PC's are connected via a DSL link.
>
> If you happened to know this, the DSL boxes are Free boxes; at one end,
> there is a router.
Which end, server or client? If it is on the se
hello
Here is my answer to the asked question:
my 2 PC's are connected via a DSL link.
If you happened to know this, the DSL boxes are Free boxes; at one end, there is
a router.
On one side, the Fireawall is WinXP's, and ZoneAlarm on the other side.
Hope this help.
F
__
t; Subject: read: connection aborted (10053)
>
> hello
>
> I am starting getting a VNC connection to run between two
> WinXP PCs, in
> Listening mode for some good reason of mine.
>
> The connection establishes OK and then breakdowns after a
> little with the
> messag
hello
I am starting getting a VNC connection to run between two WinXP PCs, in
Listening mode for some good reason of mine.
The connection establishes OK and then breakdowns after a little with the
message VNC Read connection aborted (10053).
I am trying to figure out where the problem might be
Hy,
We use in LAN VNC4.0 Server on Win2000 and VNC4.0 Client on WinXP.
Cannot connect, if screensaver on Win2000 server has a password to resume.
Win2000 Sever terminate screensaver and prompt the win2000-login window.
Client gets error message: read connection aborted (10053).
No problem, if
23 matches
Mail list logo