RE: Windows 7 laptop will not accept connection

[Philip Herlihy]

Note that the free version of RealVNC server doesn't work with Vista or W7 -
you'd need the Personal edition, which isn't free.  UVNC is a free
alternative, if you can pick your way through the misleading download
adverts and find the right link.  Otherwise, check the Connection tab allows
connections from the right subnet (allowing 192.168.0.0/255.255.0.0 is a
safe bet) and check your firewall allows the port through.  If you have some
baroque Security Suite you'll need to fathom out the procedure for opening
ports.

Philip Herlihy

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of john scholl
Sent: 29 May 2012 03:19
To: vnc-list@realvnc.com
Subject: Windows 7 laptop will not accept connection

I have an HP desktop running Windows 7 Home Premium. I have the VNC Viewer
installed on it. I have a Compaq laptop running Windows XP on which I have
the VNC Server installed.  I am able to connect from the HP to the laptop
without a problem.  I purchased a Toshiba laptop running Windows 7 Home
Premium. I installed VNC Server on it. Every time I try to connect from the
desktop to the Toshiba I get a connection was reset by peer error. I
checked that the configuration on the Toshiba matches the one on the Compaq.

I checked to see that port 5900 on the Toshiba is not in use by another
service.

Can anyone help me?

John Scholl 


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Set an environment variable for an app.

[Philip Herlihy]

I'm extremely rusty with all things Unix, and I've never played with Linux,
but this might help.

https://www.ccs.uky.edu/docs/cluster/env.html

Philip Herlihy   
Email:   phi...@herlihy.eu.com   

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Karen Thompson
Sent: 21 May 2012 20:41
To: vnc-list@realvnc.com
Subject: Set an environment variable for an app.

Hi, 
I need to set an environemt variable for a program running via
vncviewer.  It requires a env. variable JAVA_HOME=/usr/java/jre1.6.0_31.  I
have tried looking up on the web for hours and have had no luck.  I am sure
this is something very easy, if I just knew how.

Thanks,

Karen


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Good news!!!

[Philip Herlihy]

That's great.  Well done.

I use the Sun Java, from www.java.com, but that's just through following
links that have been offered at various times.  Never had a problem.  In
Firefox, I believe Java is a separate plug-in.

Philip Herlihy   
Email:   phi...@herlihy.eu.com   
Tel: 020 8521 9157  
Mobile:  07931 546660
Fax: 0870 0511055

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of John Cunniff
Sent: 05 April 2012 03:53
To: 'Philip Herlihy'; vnc-list@realvnc.com
Subject: Good news!!!

Hello, Philip!!

 

I got a good news for you!! I went to the kitchen to access my laptop via my
local Wi-Fi. I tried http://10.0.0.4:5800 http://10.0.0.4:5800/  and it
worked OK, however, Firefox showed nothing. I tried Internet Explorer, it
requested me to get Java since my laptop doesn't have Java yet.

 

I have a question, though.

 

My laptop is running on Windows 7. I need to know which is the best so far
my XP system uses Sun Micro System's Java that I downloaded off of
www.sun.com http://www.sun.com/  . Which is the best, the Sun's or
Microsoft's Java?

 

Let me know.

 

Thanks!

 

Johnny :-)

 

 

 

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC v4.1.2 and XFINITY Modem

[Philip Herlihy]

Well, you still haven't told us what you are trying to do with VNC, so it's
still hard to advise.  With VNC, you have a 'server', which is the machine
you wish to view remotely, and a 'client', which is the machine you're
sitting at to view the remote machine.  If both are on the local network,
you don't need to worry about port-forwarding.  If either is somewhere else
and you're traversing the Internet, then you're going to need to set up port
forwarding either on the router where the server is, or on the router where
the client is if you're using a 'listening' client and connecting from the
server to the client (instead of the other way round as normal).

You need a certain amount of networking knowledge to set up both VNC and
port forwarding.  It's often helpful to try to get things working with both
server and client on the same local network first, so that you don't have to
worry about port forwarding.  You need to make sure you've set a connection
password on the server, and that the server is configured to allow
connections from the relevant addresses (subnet or individual machine IP
address).  Plus you have to make sure any firewall on the server is
configured to allow the connection through.

Then if you want to traverse the Internet you'll need to set up port
forwarding.  Best thing to do is to get hold of the modem/router's user
guide, and look up port forwarding or virtual server.  

You may find that Xfinity customer support are able to help if you are
eligible for phone support perhaps.

Philip Herlihy   
Email:   phi...@herlihy.eu.com   
Tel: 020 8521 9157  
Mobile:  07931 546660
Fax: 0870 0511055


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of John Cunniff
Sent: 03 April 2012 02:08
To: 'Philip Herlihy'; vnc-list@realvnc.com
Subject: RE: VNC v4.1.2 and XFINITY Modem

Dear Phillip,

Thank you for your information.

Sorry if you didn't get my post clear. Let me tell you. I went to
www.portforward.com, you gave me. That is what I needed information. I went
to Router List, unfortunately, I cannot seem to find XFINITY but, I do see
Comcast routers, but they seem not to match me, I think. I haven't get my
magnifying glass to read the model number yet. I came home from my friend's
home and got busy to do business first. But, I visited Port Forward website.
The really nice thing is to use FPConfigure. Unfortunately, it is not free,
I must purchase it for $29.95 a copy. It is not helpful, I have to disagree
with you. I tried to look for software list, but, it is not easy for me. I
am a blind user. Not easy for me, either.

Did you use FPConfigure from there, if not, what should I do step-by-step
how I can follow better?

By the way, I logged onto http://10.0.0.1 which is my router's address. I
got the logo that says 'XFINITY Login' and I entered my router username 
password then, Log in. I can see Port Forwarding so, I need to find out
how I can do with VNC since I think that www.portforward.com does not list
this router. I also tried Google to find out, unfortunately, no luck,
either! Sigh.

Any suggestion?

Thanks,
Johnny :)

-Original Message-
From: Philip Herlihy [mailto:phi...@herlihy.eu.com]
Sent: Monday, April 02, 2012 6:37 AM
To: 'John Cunniff'; vnc-list@realvnc.com
Subject: RE: VNC v4.1.2 and XFINITY Modem

You haven't said exactly what you're trying to do with VNC, so it's hard to
advise.  If you're trying to access a machine on that network from
elsewhere, you'll need to set up port forwarding.  www.portforward.com is a
big help.  I assume everything on the local network picks up an IP address
from the router, so they should all be on the same subnet.  The 5800 port is
for the Java viewer, so you'd type http://ip address::5800 in a browser's
address bar (not a search box).  For the VNC client the port to forward is
5900, with 5500 if you want to make a reverse connection out to a
'listening' client.  Watch out for firewalls!

Philip Herlihy   
Email:   phi...@herlihy.eu.com   
Tel: 020 8521 9157  
Mobile:  07931 546660
Fax: 0870 0511055

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of John Cunniff
Sent: 31 March 2012 02:06
To: vnc-list@realvnc.com
Subject: VNC v4.1.2 and XFINITY Modem

Hello, Everybody!

I am a new user, but actually, I was an old subscriber back in 2000's.
Anyway, I got a new XFINITY modem, it was messed up including my Videophone
[VP] by Sorenson Communications. Yesterday, my tech guy came. He fixed the
wires. It is much better also, he reconfigured my VP for XFINITY modem. It
works great for now.

Unfortunately, my VNC cannot be connected from my laptop's end. I've tried
ip-address:5800 and I got Connection Timed out. I checked the settings, I
got the router so, I don't understand the settings yet.

I am running on:

Windows XP x86
Comcast high-speed internet using XFINITY modem VNC

RE: VNC v4.1.2 and XFINITY Modem

[Philip Herlihy]

Ok - that's clear.

A router is a bit like a transformer.  While a transformer has high voltage
on one side, and low voltage on the other, a router has 'public' (or
'external') Internet addresses on one side (accessible from anywhere) and
'private' ('local' or 'internal') addresses on the other (accessible only
within the local network).  So when you connect from the kitchen, you need
to use the 'local' address beginning 10.0.0.whatever, and when you're in the
coffee shop or school campus, you'll need to know the 'public' address (and
have port-forwarding working).  The problem is, that your public address
usually changes from time to time (look up DHCP or Dynamic Addressing if you
want to know more about this).  When you're at home, try running ipconfig in
a command window, to see the local address that the computer has (it will
begin 10.0.0.something on your network).  Then visit the website
www.whatismyip.com, and you'll see the current public IP address.
Different!  To solve the problem of changing public addresses, you can get
your service provider to give you a fixed or static address (charges usually
apply) or you can use a dynamic dns service, like no-ip.com.  All these
things take a while to get your head around, so if you can get a
knowledgeable friend to fix it up for you then you can concentrate more on
the stuff you care about!  But I hope that's given you something to be going
on with.

If you really want to understand all this, it'll be important to get your
head around dynamic addressing.  The computers on your local network will be
issued with an address by the router, so they will all have related
addresses (probably starting 10.0.0.*  - some routers use 192.168.1.* or
192.168.0.*  - these specific address ranges are *only* used for private
local networks).  On the public-facing side, your router will (usually) be
issued with an address, in broadly the same way, by your service provider,
but this is likely to change every time you restart your router.  These
leases last for a certain amount of time.  On the local side, the lease
may be an hour or a day (although most routers let you adjust this period,
or even fix the address a particular machine gets every time).  On the
public side, the service provider will usually give only a very short lease
- zero minutes, even.  So you need to get them to assign a static address
(for a few dollars a month, £5 in the uk is typical) or use a Dynamic DNS
service to help you keep track of that changing address.

There are other systems, some of them free for home users, which use a smart
server up there in the cloud to avoid all this complexity.  Logmein is one
such, I believe, and there are others (GoToMyPC?).  Might suit you well,
perhaps.

Good luck!

Philip Herlihy   
Email:   phi...@herlihy.eu.com   
Tel: 020 8521 9157  
Mobile:  07931 546660
Fax: 0870 0511055


-Original Message-
From: John Cunniff [mailto:johncunn...@gmail.com] 
Sent: 03 April 2012 20:50
To: 'Philip Herlihy'; vnc-list@realvnc.com
Subject: RE: VNC v4.1.2 and XFINITY Modem

Hello, Phillip,

I am very sorry if I didn't give you clear information. I am happy to
explain better system for you to understand.

Here is what my system look like:

Desktop runs on VNC version 4.1.3 through an Xfinity modem [with a built-in
router.] It's located in my bedroom.

I bring my laptop to a WI-FI available such as kitchen table, front porch or
a coffee shop or school campus and then, I'd type
http://desktop_ip_address:5800 from wi-fi connection.

I am glad that you suggested me about Xfinity. I can ask my neighbor to help
me since I am Deaf-Blind, she can assist me with port-forwarding issues. She
may know how to contact Comcast with the complexity of the recording since I
cannot follow the relay's instructions very well since I am a legally blind.
So, she can deal with the stuff for me related to phone support. Thank you
for your suggestion.

I want to apologize for not being clear. I have been hectic and stress from
work and work on the committees. I am having a little problem with the
members lately so, please accept my apology for not giving you prompt
answers.

Ask me if you want to know more about what I need. I think you get the
better answer now. Thank you.

Johnny :)

-Original Message-
From: Philip Herlihy [mailto:phi...@herlihy.eu.com]
Sent: Tuesday, April 03, 2012 12:01 PM
To: 'John Cunniff'; vnc-list@realvnc.com
Subject: RE: VNC v4.1.2 and XFINITY Modem

Well, you still haven't told us what you are trying to do with VNC, so it's
still hard to advise.  With VNC, you have a 'server', which is the machine
you wish to view remotely, and a 'client', which is the machine you're
sitting at to view the remote machine.  If both are on the local network,
you don't need to worry about port-forwarding.  If either is somewhere else
and you're traversing the Internet, then you're going to need to set up port
forwarding either on the router where the server

RE: VNC v4.1.2 and XFINITY Modem

[Philip Herlihy]

A couple of clarifications are needed:

Your modem/router has an internal address and an external address, as I
explained last time.  The whole local network shares the external address,
and the router works out who sent what for the purpose of delivering replies
from the Internet.

On the internal side, most routers take for themselves the address ending in
'1', so if your local addresses all begin 10.0.0.something, then the router
will usually have 10.0.0.1  (although there are some which take 10.0.0.254,
just to be different).  That means that the machine running the VNC server
probably isn't 10.0.0.1, because that's (probably) the address of the
router.  The router dishes out to other machines addresses on demand in that
range, usually (but not always) starting with 10.0.0.2, 10.0.0.3, etc.  So,
the address of the machine running VNC needs to be established before you
can connect to it.

To find out the IP address of the machine running the VNC server, you can
put the mouse over the VNC icon in the system tray (bottom right) and
usually a tool-tip will pop up showing the address.  Alternatively, you can
start a command window on that machine, and type:
ipconfig
... and look for a line beginning IP Address or IPV4 Address.  Look for
addresses starting 10.0.0.   and you'll soon spot what you need.

HTH



Philip Herlihy   
Email:   phi...@herlihy.eu.com   
Tel: 020 8521 9157  
Mobile:  07931 546660
Fax: 0870 0511055

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of John Cunniff
Sent: 04 April 2012 02:16
To: 'Philip Herlihy'; vnc-list@realvnc.com
Subject: RE: VNC v4.1.2 and XFINITY Modem

Phillip,

Finally! My explanation worked out for you!!! Thank you for your lengthy
message. I totally understand now what the requirement is with the
Port-Forwardings. That is why they recommended a static IP address. You
explained why - now, I understand your description very long message. Ohh, I
got it, if I need to do a 'local' address, I should do -- I know, it is
10.0.0.1 so, it will be: http://10.0.0.1:5800 :)

I don't need to worry anything with 'public address' someone told me if I
want a static IP address from Comcast, they gonna charge me some more money.
Someone is the Network Administrator, also is on Comcast, too. Oh well. I
will just do a 'local' address for now.

Thank you very much for a good explanation.

Cheers,
Johnny :)

-Original Message-
From: Philip Herlihy [mailto:phi...@herlihy.eu.com]
Sent: Tuesday, April 03, 2012 5:23 PM
To: 'John Cunniff'; vnc-list@realvnc.com
Subject: RE: VNC v4.1.2 and XFINITY Modem

Ok - that's clear.

A router is a bit like a transformer.  While a transformer has high voltage
on one side, and low voltage on the other, a router has 'public' (or
'external') Internet addresses on one side (accessible from anywhere) and
'private' ('local' or 'internal') addresses on the other (accessible only
within the local network).  So when you connect from the kitchen, you need
to use the 'local' address beginning 10.0.0.whatever, and when you're in the
coffee shop or school campus, you'll need to know the 'public' address (and
have port-forwarding working).  The problem is, that your public address
usually changes from time to time (look up DHCP or Dynamic Addressing if you
want to know more about this).  When you're at home, try running ipconfig in
a command window, to see the local address that the computer has (it will
begin 10.0.0.something on your network).  Then visit the website
www.whatismyip.com, and you'll see the current public IP address.
Different!  To solve the problem of changing public addresses, you can get
your service provider to give you a fixed or static address (charges usually
apply) or you can use a dynamic dns service, like no-ip.com.  All these
things take a while to get your head around, so if you can get a
knowledgeable friend to fix it up for you then you can concentrate more on
the stuff you care about!  But I hope that's given you something to be going
on with.

If you really want to understand all this, it'll be important to get your
head around dynamic addressing.  The computers on your local network will be
issued with an address by the router, so they will all have related
addresses (probably starting 10.0.0.*  - some routers use 192.168.1.* or
192.168.0.*  - these specific address ranges are *only* used for private
local networks).  On the public-facing side, your router will (usually) be
issued with an address, in broadly the same way, by your service provider,
but this is likely to change every time you restart your router.  These
leases last for a certain amount of time.  On the local side, the lease
may be an hour or a day (although most routers let you adjust this period,
or even fix the address a particular machine gets every time).  On the
public side, the service provider will usually give only a very short lease
- zero minutes, even.  So

RE: VNC v4.1.2 and XFINITY Modem

[Philip Herlihy]

You haven't said exactly what you're trying to do with VNC, so it's hard to
advise.  If you're trying to access a machine on that network from
elsewhere, you'll need to set up port forwarding.  www.portforward.com is a
big help.  I assume everything on the local network picks up an IP address
from the router, so they should all be on the same subnet.  The 5800 port is
for the Java viewer, so you'd type http://ip address::5800 in a browser's
address bar (not a search box).  For the VNC client the port to forward is
5900, with 5500 if you want to make a reverse connection out to a
'listening' client.  Watch out for firewalls!

Philip Herlihy   
Email:   phi...@herlihy.eu.com   
Tel: 020 8521 9157  
Mobile:  07931 546660
Fax: 0870 0511055

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of John Cunniff
Sent: 31 March 2012 02:06
To: vnc-list@realvnc.com
Subject: VNC v4.1.2 and XFINITY Modem

Hello, Everybody!

I am a new user, but actually, I was an old subscriber back in 2000's.
Anyway, I got a new XFINITY modem, it was messed up including my Videophone
[VP] by Sorenson Communications. Yesterday, my tech guy came. He fixed the
wires. It is much better also, he reconfigured my VP for XFINITY modem. It
works great for now.

Unfortunately, my VNC cannot be connected from my laptop's end. I've tried
ip-address:5800 and I got Connection Timed out. I checked the settings, I
got the router so, I don't understand the settings yet.

I am running on:

Windows XP x86
Comcast high-speed internet using XFINITY modem VNC 4.1.2 Server/Viewer

My router's IP address starts with 10.0.0.x... I think so.

When I got into router, it says XFINITY - Login so, I did logged on. I got
the main screen:

HOME  At A Glance

Home Networking Network Connection

It listed the hardware stuff. It is very basic.

Can someone tell me how do I set my VNC to go through to the internet?

Let me know.

Thank you very much!

John Cunniff
President,
Deaf-Blind Contact Center
E-mail: jo...@shellworld.net
Phone: 866-350-7482 voice or VP





___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Installing VNC on an LAN

[Philip Herlihy]

Unless you have a crossover cable between the two machines the connection
*will* be going through the router, as in the vast majority of home networks
it's the router which establishes the LAN by issuing related IP addresses to
the connected computers.

Checklist:
* Can you ping one machine from another (may need to enable echo under the
ICMP section of the firewall) or see one from another in any way?
* Have you set up the 'connections' tab in the server to allow connections
from the other machine?  (tip: try adding 192.168.0.0/255.255.0.0 to the
list of networks)
* Is your firewall set to allow winvnc4.exe to allow incoming connections?


Philip Herlihy   


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Dan Riebs
Sent: 19 January 2012 20:05
To: vnc-list@realvnc.com
Subject: Installing VNC on an LAN

I'm installing VNC between two computers at home on my LAN. There is no need
for either machine to be able to pass through the router, much less access
the Internet.

I'm getting a 10060 error. What do I do?


--
There is only one basic human right, the right to do as you damn well
please. And with it comes the only basic human duty, the duty to take the
consequences. -- PJ O'Rourke

When the facts change, I change my mind. What do you do, sir? - John
Maynard Keynes

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC server stops responding after a few days

[Philip Herlihy]

I've missed a few episodes of this drama, so hope I'm not going over old
ground.  I don't think you're doing enough to distinguish problems with VNC
server from general network problems.  When the machine(s) are not
responding are you able to ping them?  (You may need to allow echo on the
server firewall's ICMP tab, and you may be able to ping directly from the
router's diagnostic interface, if you can access that externally.)  However,
you can test just as well with a VNC viewer on a machine on the same local
network.  Is the network interface set to wake the machine if a connection
is made?  Turning off standby might be a good option.

If you run ipconfig /all in a command window you'll see useful DHCP stats,
including the date/time any DHCP lease was obtained.  For anything acting as
a server you're better off with a static IP (or a reserved DHCP address).
Reduce the DHCP range or scope to leave room at either end for a few
static IPs, and use one of those for this type of machine.  Netscan.exe from
softperfect.com is a good free network scanner which might help you spot
issues.

You're not using wireless, are you?  To be avoided if possible.

Check in Task Manager - if Peak Commit Charge becomes greater than Physical
Memory, the machine will have been paging out idle processes, and this might
include VNC server or maybe (?) networking components.


Philip Herlihy   

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of James Wheaton
Sent: 21 November 2011 14:50
To: vnc-list@realvnc.com
Subject: Re: VNC server stops responding after a few days

The uncommented line in the hosts file is simply:
127.0.0.1   localhost

The default gateway is setup in the Windows IP properties (along with the
other static settings) to be 192.168.0.254, which is our modem/router/DHCP
server. The modem has an external static IP that we would be connecting to
with VNC. I can connect to it on that address and the internal 192.168.0.99
... The command line on the VNC Viewer shortcut is just the default
vncviewer.exe with no options.

I just woke up one of the VNC servers/desktops that stopped working over the
weekend. I opened the web browser and it took a bit to load; was it asking
for an IP renewal? Maybe it's just the power saving options that are at
fault:

Turn off harddicks:   1hr
Standby: 1hr
Hibernate: never

James Wheaton
FloSource, Inc.
Phone: 765.342.1360
Fax: 765.342.1361

Visit us on the web: www.flosource.com http://www.flosource.com

On 11/18/2011 5:41 AM, Paul Dunn wrote:
 On 16/11/2011 22:56, Christopher Woods (CustomMade) wrote:

 Surely if a machine has a fixed static IP, it doesn't even enter into 
 discussion with the network's DHCP server to request a lease? Just 
 the usual broadcast traffic...

 I'm not a networking or Windows expert, but this presumably depends on 
 whether the client (XP?) actually has the VNC server's IP address in 
 its hosts file (something like C:\WINDOWS\system32\drivers\etc\hosts).
 If it doesn't, then it will send a request to get the address from the 
 DHCP server. If the client ends up using the IP address supplied by 
 the server, then it will eventually expire. I've had exactly this 
 problem on another X server (not VNC).

 James: what's in your hosts file? And how does the client actually 
 connect to the server? What's the VNC command line?

 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Caps-lock inversion?

[Philip Herlihy]

Why is it that sometimes you have to set Caps-Lock on your local keyboard to
get lower-case characters on the remote machine?  Is there a fix?

Philip Herlihy   




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Cursor disappears in Notepad

[Philip Herlihy]

Might be worth checking your mouse settings - there's an option to hide
cursor when typing that might be responsible for this.  Check server and
viewer.

Philip Herlihy   


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Jon Harris
Sent: 09 March 2011 09:10
To: vnc-list@realvnc.com
Subject: Cursor disappears in Notepad


I am using VNC Viewer Free Edition 4.1.3 on XP and accessing a PC running
VNC Server Free Edition 4.1.3 in Service Mode also on Windows XP.  In many
programs, the locally rendered cursor disappears when in an editable text
field.  A simple example is Notepad.  When hovering over a menu, the arrow
cursor is displayed as expected.  But over the main text editing area, where
you would normally get the I-beam cursor, I see nothing.
 
I know about the Render cursor locally option.  I have had to turn it off
since otherwise the cursor totally disappears in many places as mentioned
above.  But I would like to be able to use this feature as the mouse action
is much smoother with it on, especially with slower connections.
 
Any ideas?
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC to N3 network?

[Philip Herlihy]

Yes it can be blocked.  Any decent firewall can block an outgoing port as
well as an incoming one, and a properly secured system will have blocked
anything not positively known to be needed.

Good luck!

Philip Herlihy   

-Original Message-
From: Paul Dunn [mailto:sa212+...@cyconix.com] 
Sent: 25 November 2010 19:55
To: VNC list
Cc: Philip Herlihy
Subject: Re: VNC to N3 network?

On 25/11/2010 14:40, Philip Herlihy wrote:
 Your best bet is using a listening client and initiating a session from
the
 controlled machine.

This is my fallback plan, but it's so inconvenient that it probably 
wouldn't be worth it. I don't think this could be blocked - could it? 
The surgery computer can always see outside N3 on a browser, so 
presumably tunnelling on 80/443 should be fireproof.

The issue for incoming connections, as you point out, is authorisation. 
It's possible to get authorisation, but it's next to impossible to find 
out *how* to get authorisation. This is what I've been googling for. 
There are half-a-dozen commercial solutions that do exactly this, but I 
can't find anyone at N3, or any technical docs, to tell me what's 
involved or who to apply to. You can apply to use an existing 
third-party commercial solution, but that's it. The third-party 
solutions have various problems, apart from price - some only encrypt 
between the surgery computer and the N3 gateway, some use offshore/US 
servers, and so on. End-to-end vnc/ssh is my preferred solution.

So, what I was hoping was that someone here has already been through the 
pain, and found out how to apply to get through the gateway, or how to 
get through without finding someone to apply to...

-Paul




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC to N3 network?

[Philip Herlihy]

Your best bet is using a listening client and initiating a session from the
controlled machine.  Set your router to route port 5500 to your PC, allow it
through any PC-based firewall, and run the listening client. However, my
guess is that even this will be blocked if the network is really a secure
one.  You won't make any progress on this without authorisation, and that
will be hard to get.  I must say if a VNC client could get access to medical
information simply by Googling for the details, something would be very
wrong.

Philip Herlihy   


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Paul Dunn
Sent: 25 November 2010 11:18
To: VNC list
Subject: VNC to N3 network?

Has anyone managed to set up VNC to allow access into the secure N3 
(NHS) network? I've spent hours on Google, and haven't managed to find 
anything on getting through the gateway, or even on finding IP addresses 
for the surgeries I want to get to.

Thanks -

Paul

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC server on HP, viewer on Win 7

[Philip Herlihy]

I've used RealVNC in mixed environments recently.  It seems you only need to
pay for the software if it contains a server - the viewers can be downloaded
separately and run without charge.  So, you can download whichever viewer is
appropriate for the platform (and run it on 7), and it should interact
successfully with the server on HPUX.

Phil, London

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Norma Jean Sebastian
Sent: 11 February 2010 22:02
To: vnc-list@realvnc.com
Subject: VNC server on HP, viewer on Win 7

Hello,

It has been some time since I have used VNC.

Is it possible to run VNC Server (free or otherwise) on HPUX, and run
VNC Viewer on Windows 7.
Can I do this setup with the Free Edition?
If I need to purchase the server enterprise edition for our HPUX, does
it come with a viewer for Windows 7 or do I still need to download the
free viewer and will it work on Windows 7?

I looked around on the website and saw server support for windows 7, but
I will be running the server on HPUX, and only the viewer on windows 7.

Thank you for your advice.
Norma Jean


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: how to remote to clients PC for troubleshooting?

[Philip Herlihy]

Well, the client machine has to be reachable by some sort of network or you
can forget it!  RealVNC does work reasonably well over dial-up, even;
otherwise, you need to set up a virtual server (other terms are used)
within the broadband router.  See http://www.portforward.com/ for details on
how to do this. (Port 5900).  If the PC connects directly to the Internet
(e.g. by using a USB modem rather than a router) then you can connect from
your end having adjusted any firewall on the machine to allow this.

If your client is not up to configuring the necessary forwarding, then you
can run a viewer in Listening mode at your end and have your client
(person!) initiate the connection from the server at their end - then it's
up to you to do the port-forwarding on your own router (5500 in this
direction).

Of course, you have to have the server installed on the
machine-to-be-controlled and a viewer on your own machine.  The Enterprise
Viewer is free to download and there is a free version for XP and below
which can be run on the PC.  For Vista or 7 (?) you need to buy the Personal
or Enterprise versions, as the free one falls foul of the tighter security
architecture in these later versions of Windows.

Philip Herlihy   

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Chris R. Johnson
Sent: 16 December 2009 19:45
To: vnc-list@realvnc.com
Subject: how to remote to clients PC for troubleshooting?

Hi,

How can I remote into a clients computer (miles away and not on a network)
to troubleshoot it?

Could I operate from a Mac this way into a PC?

Which version will I need? Enterprise?

Thank you.

Chris



  
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Accessing more than one computer

[Philip Herlihy]

Used to be the case, but a single colon works these days.  Try it!

Philip Herlihy   


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of John Aldrich
Sent: 18 November 2009 19:05
To: vnc-list@realvnc.com
Subject: Re: Accessing more than one computer

On Wednesday 18 November 2009, Philip Herlihy wrote:
 Presumably you've successfully routed port 5900 to the one machine
  you're managing now.
 
 You have two options, depending on the capabilities of your router.  My
 router allows me to translate an incoming port, so I can connect using
 port  and the receiving computer sees a connection on .  If your
 router can do this, then you can leave the VNC servers operating on port
 5900, and set the router up to make the translation.  With many routers,
  you set up a named service for the incoming port, and set up the
  translation when you configure the firewall rule.
 
 If your router won't do this, then you need to configure the VNC service
  to use some other port, eg 5091.  Then create additional services in
  your router (you might name one VNC-5901) and set up additional rules
  to route such connections to the desired machines.  You can do this
  many times, for many machines.  To access the machine you want, simply
  append a colon and the port number to the router's IP at the client. 
  So, if you were connecting now to a VNC server at 111.222.333.444 you'd
  instead use 111.222.333.444:5901.
 
I could be mistaken, but I thought if you were entering a *port* number you 
needed to use a DOUBLE-colon, eg ::5901, whereas if you were specifying 
just a screen number, you could do :1, or :2 (for 5902, etc.) Or was this 
one of the things tweaked in more recent releases?

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Accessing more than one computer

[Philip Herlihy]

Presumably you've successfully routed port 5900 to the one machine you're
managing now.

You have two options, depending on the capabilities of your router.  My
router allows me to translate an incoming port, so I can connect using
port  and the receiving computer sees a connection on .  If your
router can do this, then you can leave the VNC servers operating on port
5900, and set the router up to make the translation.  With many routers, you
set up a named service for the incoming port, and set up the translation
when you configure the firewall rule.

If your router won't do this, then you need to configure the VNC service to
use some other port, eg 5091.  Then create additional services in your
router (you might name one VNC-5901) and set up additional rules to route
such connections to the desired machines.  You can do this many times, for
many machines.  To access the machine you want, simply append a colon and
the port number to the router's IP at the client.  So, if you were
connecting now to a VNC server at 111.222.333.444 you'd instead use
111.222.333.444:5901.

Philip Herlihy, London 

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of deangi...@optusnet.com.au
Sent: 18 November 2009 05:20
To: vnc-list@realvnc.com
Subject: Accessing more than one computer


Hi,

How do I configure my router to allow me to view more than one computer in
the same network?  Please provide detailed  instructions as I am not an
expert in computer networking

Regards
Dean

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: cannot configure vncserver 4.1 service-mode on Win Vista Home Premium

[Philip Herlihy]

Have you tried right-clicking the item and picking run as administrator?

Philip Herlihy   

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Leo JB
Sent: 17 October 2009 02:54
To: vnc-list@realvnc.com
Subject: cannot configure vncserver 4.1 service-mode on Win Vista Home
Premium

When arying to configure vncserver 4.1 service-mode on Win Vista Home
Premium, I get the error messeage

you do not have sufficient access rights to run the vnc configuration
applet

The user has admin proviledges.

What to do?

Thanks in advance.
 === 


  
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC in listening mode, connection fails with read: Connection reset by peer (10054)

[Philip Herlihy]

Worth commenting that there are a number of routers which claim to work with
DynDNS while DynDNS say they don't work correctly.

Philip Herlihy   


-Original Message-
From: Kevan Rehm [mailto:kr...@visi.com] 
Sent: 14 October 2009 02:03
To: Philip Herlihy; vnc-list@realvnc.com
Subject: Re: VNC in listening mode, connection fails with read: Connection
reset by peer (10054)

Philip,

Thanks for your reply.  I've managed to work around the problem, but thought

I should give an update just in case anyone else runs into the same thing.

First, I do understand that I shouldn't have to port-forward 5900 and 5800; 
I had simply reached the point where I was willing to try anything.  :-)  I 
have since disabled them again.  Also, my DDNS address is working correctly,

the IP address I get when I ping the hostname matches the address I get when

going to WhatIsMyIP.com.   The Belkin also seems capable of updating the 
DDNS correctly, the Belkin documentation actually tells you to register your

name at DynDns so that it can be automatically updated, so I'm willing to 
believe that they actually tried it before shipping.  :-)

I have come to believe as you do that this is some quirk having to do with 
having one machine on an internal LAN talking to another on the same 
internal LAN but using an external address.  After I read your email, a 
light bulb came on, and I used one of the internal LAN machines to 
SSH-tunnel to my office across town, effectively putting that machine 
outside the internal LAN (its IP address was now that of an office machine).

In this configuration I was able to connect from that tunneling machine to 
my VNC-listening machine using the external DDNS name.

The only reason I was going through all this is because I am setting up a 
computer for my in-laws and testing it before taking it over to their house.

I wanted to make sure that they could connect back to my machine so that I 
could help them with any problems.  After my tunneling experiment, I now 
know that it will work correctly when I take the computer to their house, 
once it is off my internal LAN.

Again, I appreciate your help.  It's still an interesting problem as to why 
this doesn't work when both machines are on the internal LAN and an external

address is used, but since it's only a temporary situation, I'm willing to 
give up trying to figure it out.  :-)

Regards, Kevan 




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC in listening mode, connection fails with read: Connection reset by peer (10054)

[Philip Herlihy]

That all sounds ok to me, except that I've never had occasion to test the
connection via a dynamic DNS name from/to a client within the same subnet -
obviously you'd never need to do this apart from testing.  Two possibilities
suggest themselves (but don't assume I haven't missed anything!):  firstly
that the Belkin simply can't handle the incongruity of the combination of
NAT (where the router has to keep track of which LAN client issued, say, a
particular web request so that it can route the pages accordingly) and
port-forwarding, which caters for an externally originated connection.  The
other possibility is that the dynamic DNS isn't working, and you're pinging
some innocent bystander, which is dutifully responding (been there, t-shirt,
etc).  DynDNS have a (short) list of certified hardware and say that many
devices don't work acceptably well.  They have a software client which is
free to download and easy to configure.  However, you can ensure that the
DNS setting is correct by logging on to DynDNS from any machine on your LAN
and updating the address (ideally after disabling the router facility just
in case).  Presumably you want to make this connection from a server outside
your own LAN.  Can you (after lowering the security settings) access the
router's configuration pages from outside?  Have you tried getting an
external server to connect?

Incidentally, in the scenario you describe you need forward only port 5500
to the host of the listening client; you would only need to port-forward
5800 or 5900 if you are trying to reach a server (rather than client) from
outside the LAN.

Philip Herlihy   


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Kevan Rehm
Sent: 13 October 2009 03:59
To: vnc-list@realvnc.com
Subject: VNC in listening mode, connection fails with read: Connection
reset by peer (10054)

Greetings,

I have my home PC configured to Run Listening VNC Viewer, and the PC has a

static IP address of 192.168.2.10 behind a wireless Belkin router.  I have 
port-forwarded TCP ports 5500, 5800, and 5900 in my Belkin router to the 
same port addresses in 192.168.2.10, and I have configured my PC's McAfee 
firewall to open TCP ports 5500, 5800, and 5900.   I downloaded the 
PFPortChecker program from portforward.com, and it confirms that all three 
ports are indeed open.

I have also created a DDNS hostname at dyndns.org so that I have a hostname 
whose DNS resolution will work even as Comcast periodically changes the IP 
address they give me.  I configured the Belkin router to update the 
dyndns.org site whenever the Comcast address changes.  I am able to ping my 
machine successfully using the DDNS hostname.  So far, so good.

On another PC in my Belkin's internal network, I can start up the VNC 
Server, select Add Client, and connect to the listening viewer 
successfully by using 192.168.2.10, and can see the server machine's 
desktop.  Works perfectly.  If on that same machine I instead select Add 
Client but use the dyndns.org hostname, a pop-up immediately appears on the

listening machine saying read: Connection reset by peer (10054).  If I 
click OK in the pop-up, the same message appears two more times, at which 
point the VNC server machine reports Connection failed.  Any idea why this

is failing?  It doesn't seem to be a port-forward problem.

Any help would be greatly appreciated.

Regards, Kevan 


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: No-IP and Real VNC on multiple PC's‏

[Philip Herlihy]

No experience of this, sorry.

Philip Herlihy   


-Original Message-
From: Christopher Woods [mailto:christop...@custommade.org.uk] 
Sent: 28 September 2009 11:30
To: 'Roberto Meza'; phi...@herlihy.eu.com
Cc: vnc-list@realvnc.com
Subject: RE: No-IP and Real VNC on multiple PC's‏

 I must say I’ve also had problems with 2Wire modems not apparently
detecting machines which are connected through it, so the hard-reset might
be a good idea.

Is it just DHCP clients 2Wire units have problems with? Does it detect uPnP
devices ok?




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: No-IP and Real VNC on multip le PC's‏

[Philip Herlihy]

My understanding of NAT is that a router must be able to associate multiple 
connections (possibly connectionless UDP conversations) between its LAN clients 
and external stations which can see only the router as a single entity.  So, if 
a UDP datagram arrives from a station on the WAN the router must be able to 
“remember” which of its clients it should be sent to.

 

Port forwarding is a fixed configuration, where a connection on a particular 
port (e.g. 5900 or 5500) is always routed to a particular client.  The most 
helpful routers allow the port to be translated, so you can connect to the 
router on port 8903 or port 8904 and the router will send the connection to 
10.0.0.3 or 10.0.0.4 respectively, while translating the port on the LAN side 
to 5900.

 

Caveat: I’m no networking guru!

 


Philip Herlihy






 

From: Dale Eshelman [mailto:eshelm...@gmail.com] 
Sent: 27 September 2009 00:44
To: Philip Herlihy
Cc: vnc-list@realvnc.com
Subject: Re: No-IP and Real VNC on multiple PC's‏

 

I am familiar with the link. I just thought there was something special you 
were addressing I did not know. I do not know a router that does not have port 
forwarding.

I just thought the term NAT referenced something special regarding routers. 
So I guess Net Address Translation is the same as port forwarding.

 

On Sep 26, 2009, at 05:09 AM, Philip Herlihy wrote:





You may find this helpful:

http://portforward.com/

Philip Herlihy  


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Dale Eshelman
Sent: 26 September 2009 02:55
To: Christopher Woods
Cc: 'Bob Grabbe'; vnc-list@realvnc.com
Subject: Re: No-IP and Real VNC on multiple PC's‏

Can you provide an example of of the setting and location of setting  
on the router that need to take place for NAT? What must a router have  
in the settings to be a NAT router?
Thanks

On Sep 25, 2009, at 12:28 PM, Christopher Woods wrote:




 

I've done this before, although only with two pc's behind the

same router.

For example, the router is set up to forward port 5900 to

pc1, with the ip of 192.168.1.50 and port 5901 to pc 2 with

the ip of 192.168.1.51.

PC1 is set in vnc to listen on port 5900 and pc2 is set to

listen on port 5901. You set this on the connections tab of

the options for the vnc server on each pc.

If I want to connect to pc1, I run the vnc client ( from work

) to the No-ip address:5900, if I want to connect to pc2,

it's the No-ip address:5901.

 

With a good NATting router, having to change the listen ports on  

each PC

*shouldn't* be necessary, but it can make things simpler. (however  

if you're

connecting from those machines via a LAN it adds the requirement to  

specify

the port as well, which I dislike...)

 

If the 2Wire can only directly map incoming traffic to the  

equivalent port

on the internal machine, then Roberto will have to do that. As long  

as his

router supports restricted or full cone NAT and allows for differing  

local

and remote port assignments, he should only have to make his changes  

on the

router (all the LAN PCs will quite happily work with the default  

settings).

 

 

___

VNC-List mailing list

VNC-List@realvnc.com

To remove yourself from the list visit:

http://www.realvnc.com/mailman/listinfo/vnc-list



Dale Eshelman
eshelm...@gmail.com

ShopToEarn (Dist ID 105985)
 http://www.ShopToEarn.net/DaleEshelman

MonaVie (Distr ID 1316953)
http://www.monavie.com/Web/US/en/product_overview.dhtml

The closer I get to the pain of glass in Windoz, the farther I can see  
and I see a Mac on the horizon.

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

 


Dale Eshelman

eshelm...@gmail.com

 

ShopToEarn (Dist ID 105985)

 http://www.ShopToEarn.net/DaleEshelman http://www.ShopToEarn.net/Eshelman 

MonaVie (Distr ID 1316953)
http://www.monavie.com/Web/US/en/product_overview.dhtml

 

The closer I get to the pain of glass in Windoz, the farther I can see and I 
see a Mac on the horizon.

 

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: No-IP and Real VNC on multiple PC's‏

[Philip Herlihy]

The nice thing about NAT is that the router does it automatically.
Port-forwarding has to be set up manually, unless you can fathom the
mysteries of uPnP (which I'm not sure I can).  In the situation you
describe, the router to which the listening client is attached would need
port-forwarding to be configured.  At the other end NAT would take care of
things without intervention.  Which is why listening clients are so useful,
and in some situations a huge advantage over Remote Desktop, which can't do
this.

Philip Herlihy   


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Christopher Woods
Sent: 27 September 2009 14:17
To: 'Philip Herlihy'; 'Dale Eshelman'
Cc: vnc-list@realvnc.com
Subject: RE: No-IP and Real VNC on multiple PC's‏

 My understanding of NAT is that a router must be able to 
 associate multiple connections (possibly connectionless UDP 
 conversations) between its LAN clients and external stations 
 which can see only the router as a single entity.  So, if a 
 UDP datagram arrives from a station on the WAN the router 
 must be able to “remember” which of its clients it should be sent to.
 
  
 
 Port forwarding is a fixed configuration, where a connection 
 on a particular port (e.g. 5900 or 5500) is always routed to 
 a particular client.  The most helpful routers allow the port 
 to be translated, so you can connect to the router on port 
 8903 or port 8904 and the router will send the connection to 
 10.0.0.3 or 10.0.0.4 respectively, while translating the port 
 on the LAN side to 5900.


Entirely accurate; apologies for any confusion from my earlier response. I
was not attempting to conflate static port forwarding with NAT (I was just
indicating that if his router can happily handle NAT, it should be able to
support multiple port forwards ;)

The NAT capabilities might come in to play if the server is set to connect
to an external listening client...


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: No-IP and Real VNC on multiple PC's‏

[Philip Herlihy]

I assume you’ve configured VNC server on PC5 to use port 5905 (and so on).
You’ve also added a firewall exception for port 5905 on that machine (you
could have just trusted the application and the firewall will figure out
which port is involved).  If I understand you correctly, then what’s missing
is a port-forwarding rule in the router which will direct incoming
connections using port 5905 to the IP address of PC5.  And so on, for the
other machines.

 

Can’t remember what the 2Wire interface looks like, but many routers call
these rules “Virtual Servers”.

 

Be aware that VNC requires TWO colons if you are using anything other than
the default port, so your address should be:  papeleria.no-ip.org::5901

 

 


Philip Herlihy






 

From: Roberto Meza [mailto:roberto_mez...@hotmail.com] 
Sent: 27 September 2009 15:15
To: christop...@custommade.org.uk; phi...@herlihy.eu.com;
eshelm...@gmail.com
Cc: vnc-list@realvnc.com
Subject: RE: No-IP and Real VNC on multiple PC's‏

 

Hello:
 
I think I'm missing something on my 2Wire 2701HG-T router configuration or
somewhere else.
 
I can only connect to the PC (the main one) that has the No-IP client
installed.
 
I added an exception on Windows XP firewall on each of the 7 PC's
 
So for the main PC I added the exception port TCP 5900
So for PC1 I added the exception port TCP 5901
So for PC2 I added the exception port TCP 5902
So for PC3 I added the exception port TCP 5903
So for PC4 I added the exception port TCP 5904
So for PC5 I added the exception port TCP 5905
So for PC6 I added the exception port TCP 5906
 
I'm entering on the VNC Viewer papeleria.no-ip.org:5901 to try to connect to
PC1 but I can't.
 
How am I supposed to configure the router?
 
What I did was to forward ports 5900 through 5901 to the IP address if the
main PC (192.168.1.71) where the No-IP client is installed.
 
Am I missing something?
 
Thanks
 
 From: christop...@custommade.org.uk
 To: phi...@herlihy.eu.com; eshelm...@gmail.com
 Subject: RE: No-IP and Real VNC on multiple PC's‏
 Date: Sun, 27 Sep 2009 14:16:34 +0100
 CC: vnc-list@realvnc.com
 
  My understanding of NAT is that a router must be able to 
  associate multiple connections (possibly connectionless UDP 
  conversations) between its LAN clients and external stations 
  which can see only the router as a single entity. So, if a 
  UDP datagram arrives from a station on the WAN the router 
  must be able to “remember” which of its clients it should be sent to.
  
  
  
  Port forwarding is a fixed configuration, where a connection 
  on a particular port (e.g. 5900 or 5500) is always routed to 
  a particular client. The most helpful routers allow the port 
  to be translated, so you can connect to the router on port 
  8903 or port 8904 and the router will send the connection to 
  10.0.0.3 or 10.0.0.4 respectively, while translating the port 
  on the LAN side to 5900.
 
 
 Entirely accurate; apologies for any confusion from my earlier response. I
 was not attempting to conflate static port forwarding with NAT (I was just
 indicating that if his router can happily handle NAT, it should be able to
 support multiple port forwards ;)
 
 The NAT capabilities might come in to play if the server is set to connect
 to an external listening client...
 
 
 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: No-IP and Real VNC on multiple PC's‏

[Philip Herlihy]

I’ve used one of these routers to configure Remote Desktop through the one
router to multiple PCs.  I connect to (say) xxx.xxx.xxx.xxx:8049 and the
2Wire routes it to the designated machine (typically local IP 10.0.0.49),
translating the port to 3389 on the fly (“map to host port”).  Works a
treat.

 

On this router you edit (create) an “Application” for each type of
connection: I call mine something like (eg) RDC-8049, and have it “map to
host port” 3398.Exactly the same for VNC: I’d have an Application called
VNC-8049 and map that to host port 5900.  Then I select the desired computer
from the “Select a computer” drop-down (numbered “1” in the screenshot on
the site below) and add it to the “Hosted Applications” list for that
machine.

 

If your router isn’t correctly detecting the connected PCs then I’d guess a
power-cycle might help, but I can’t help further with that.

 


Philip Herlihy






 

From: Roberto Meza [mailto:roberto_mez...@hotmail.com] 
Sent: 27 September 2009 16:57
To: phi...@herlihy.eu.com
Cc: vnc-list@realvnc.com
Subject: RE: No-IP and Real VNC on multiple PC's‏

 

This tutorial is good to connect to only one PC detected by the router.
 
I will write 2Wire's support to know what do I need to do for the router to
detect all the machines, not just a few.
 
Thanks
 

  _  

From: phi...@herlihy.eu.com
To: roberto_mez...@hotmail.com
Subject: RE: No-IP and Real VNC on multiple PC's‏
Date: Sun, 27 Sep 2009 16:37:24 +0100

Check this:

 

http://portforward.com/english/routers/port_forwarding/2wire/2701HG-T/VNC.ht
m

 

I must say I’ve also had problems with 2Wire modems not apparently detecting
machines which are connected through it, so the hard-reset might be a good
idea.

 

Regarding Christopher’s comment about the double-colon, for all I know they
have removed the requirement for the second colon – I’ll have to try it some
time!

 

 


Philip Herlihy






 

From: Roberto Meza [mailto:roberto_mez...@hotmail.com] 
Sent: 27 September 2009 15:55
To: phi...@herlihy.eu.com
Cc: vnc-list@realvnc.com
Subject: RE: No-IP and Real VNC on multiple PC's‏

 

The problem is that things don't work that way for this particular router.
 
First, you are forced to select a set of computers detected by the router
from a drop down menu list and then configure which ports are associated
with that particular PC's.
 
Problem is not all the 8 PC's appear on that list I don't know why so
there's no way to select all the IP addresses from all the PC's.
 
Unfortunately you cannot manually type the IP addresses for all PC's. Some
of them are there and some aren't.
 
Maybe I need to do a hard reset to the router so it detects all the machines
connected to it.
 
Thanks
 

  _  

From: phi...@herlihy.eu.com
To: roberto_mez...@hotmail.com
CC: vnc-list@realvnc.com
Subject: RE: No-IP and Real VNC on multiple PC's‏
Date: Sun, 27 Sep 2009 15:41:22 +0100

I assume you’ve configured VNC server on PC5 to use port 5905 (and so on).
You’ve also added a firewall exception for port 5905 on that machine (you
could have just trusted the application and the firewall will figure out
which port is involved).  If I understand you correctly, then what’s missing
is a port-forwarding rule in the router which will direct incoming
connections using port 5905 to the IP address of PC5.  And so on, for the
other machines.

 

Can’t remember what the 2Wire interface looks like, but many routers call
these rules “Virtual Servers”.

 

Be aware that VNC requires TWO colons if you are using anything other than
the default port, so your address should be:  papeleria.no-ip.org::5901

 

 


Philip Herlihy






 

From: Roberto Meza [mailto:roberto_mez...@hotmail.com] 
Sent: 27 September 2009 15:15
To: christop...@custommade.org.uk; phi...@herlihy.eu.com;
eshelm...@gmail.com
Cc: vnc-list@realvnc.com
Subject: RE: No-IP and Real VNC on multiple PC's‏

 

Hello:
 
I think I'm missing something on my 2Wire 2701HG-T router configuration or
somewhere else.
 
I can only connect to the PC (the main one) that has the No-IP client
installed.
 
I added an exception on Windows XP firewall on each of the 7 PC's
 
So for the main PC I added the exception port TCP 5900
So for PC1 I added the exception port TCP 5901
So for PC2 I added the exception port TCP 5902
So for PC3 I added the exception port TCP 5903
So for PC4 I added the exception port TCP 5904
So for PC5 I added the exception port TCP 5905
So for PC6 I added the exception port TCP 5906
 
I'm entering on the VNC Viewer papeleria.no-ip.org:5901 to try to connect to
PC1 but I can't.
 
How am I supposed to configure the router?
 
What I did was to forward ports 5900 through 5901 to the IP address if the
main PC (192.168.1.71) where the No-IP client is installed.
 
Am I missing something?
 
Thanks

RE: Keep-alive script available

[Philip Herlihy]

That might have been a wasted few hours, writing that script, then!  I'd
looked for a suitable configuration but hadn't found one.

Do you mean to say that the connection will survive periods of network
glitch/error/whatever if this setting is used?  Or is there still a role for
my script?  Grateful for any further clarification you can offer on this -
as the perceived unreliability of VNC connections in some situations has
led me to use RDC whenever that's an option.

Philip Herlihy   
Email:   phi...@herlihy.eu.com   
Tel: 020 8521 9157  
Mobile:  07931 546660
Fax: 0870 0511055


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Alex Pelts
Sent: 27 September 2009 17:12
To: Philip Herlihy
Cc: vnc-list@realvnc.com
Subject: Re: Keep-alive script available

Or you can set timeout to 0 and server will not drop connection.

Regards,
Alex


Philip Herlihy wrote:
 One of the most useful features of VNC is the facility to set up a reverse
 connection, initiated from the server to a listening client.  Providing
the
 router at the client end can be configured to pass through port 5500,
there
 is no need to mess with firewalls and routers at the server end.  As the
 expertise is usually at the client end - that's a good deal!

  

 However, that leaves the job of maintaining the connection, re-connecting
as
 necessary, at the server end.  Many times I've had someone set up a
 connection only for it to drop a few minutes after they have left.

  

 I've finally (!) got a script working which provides one solution to this.
 The script, which uses only built-in NT commands (tested under XP), sets
up
 a connection and then periodically monitors that it is still live,
 automatically re-establishing the connection if it has dropped.  This
 version is for a client at a location with a known IP address, but it
could
 be adapted to use a domain address (including one obtained via dynamic
DNS).

  

 If you'd like a copy, drop me a note.  Beyond keeping the attribution in
the
 comments, there are no strings attached.

  

 Phil Herlihy

 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list

   



___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: No-IP and Real VNC on multiple PC's‏

[Philip Herlihy]

You may find this helpful:

http://portforward.com/

Philip Herlihy   


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Dale Eshelman
Sent: 26 September 2009 02:55
To: Christopher Woods
Cc: 'Bob Grabbe'; vnc-list@realvnc.com
Subject: Re: No-IP and Real VNC on multiple PC's‏

Can you provide an example of of the setting and location of setting  
on the router that need to take place for NAT? What must a router have  
in the settings to be a NAT router?
Thanks

On Sep 25, 2009, at 12:28 PM, Christopher Woods wrote:


 I've done this before, although only with two pc's behind the
 same router.
 For example, the router is set up to forward port 5900 to
 pc1, with the ip of 192.168.1.50 and port 5901 to pc 2 with
 the ip of 192.168.1.51.
 PC1 is set in vnc to listen on port 5900 and pc2 is set to
 listen on port 5901. You set this on the connections tab of
 the options for the vnc server on each pc.
 If I want to connect to pc1, I run the vnc client ( from work
 ) to the No-ip address:5900, if I want to connect to pc2,
 it's the No-ip address:5901.

 With a good NATting router, having to change the listen ports on  
 each PC
 *shouldn't* be necessary, but it can make things simpler. (however  
 if you're
 connecting from those machines via a LAN it adds the requirement to  
 specify
 the port as well, which I dislike...)

 If the 2Wire can only directly map incoming traffic to the  
 equivalent port
 on the internal machine, then Roberto will have to do that. As long  
 as his
 router supports restricted or full cone NAT and allows for differing  
 local
 and remote port assignments, he should only have to make his changes  
 on the
 router (all the LAN PCs will quite happily work with the default  
 settings).


 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list


Dale Eshelman
eshelm...@gmail.com

ShopToEarn (Dist ID 105985)
  http://www.ShopToEarn.net/DaleEshelman

MonaVie (Distr ID 1316953)
http://www.monavie.com/Web/US/en/product_overview.dhtml

The closer I get to the pain of glass in Windoz, the farther I can see  
and I see a Mac on the horizon.

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Keep-alive script available

[Philip Herlihy]

One of the most useful features of VNC is the facility to set up a reverse
connection, initiated from the server to a listening client.  Providing the
router at the client end can be configured to pass through port 5500, there
is no need to mess with firewalls and routers at the server end.  As the
expertise is usually at the client end - that's a good deal!

 

However, that leaves the job of maintaining the connection, re-connecting as
necessary, at the server end.  Many times I've had someone set up a
connection only for it to drop a few minutes after they have left.

 

I've finally (!) got a script working which provides one solution to this.
The script, which uses only built-in NT commands (tested under XP), sets up
a connection and then periodically monitors that it is still live,
automatically re-establishing the connection if it has dropped.  This
version is for a client at a location with a known IP address, but it could
be adapted to use a domain address (including one obtained via dynamic DNS).

 

If you'd like a copy, drop me a note.  Beyond keeping the attribution in the
comments, there are no strings attached.

 

Phil Herlihy

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Personal VNC question

[Philip Herlihy]

I use a mix of personal and free licenses.  The Personal edition viewer is
freely downloadable and can access both types of server.  You'd need a
license for each machine on which you'll be running the Personal Edition
server.

Bear in mind that you'll need to negotiate a port-forwarding arrangement
with network admin at your work if you're going to be able to initiate a
connection to a machine within the network from outside, or the firewall
will block it.  At home you can set this up yourself.

It's more common to want to print something locally from the server to which
you're connected.  You'd probably want to transfer the printable file (or
maybe a printable version) and kick off the print job on the remote machine.

Philip Herlihy   


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Patrick Immel
Sent: 06 September 2009 15:37
To: vnc-list@realvnc.com
Subject: Personal VNC question

Hello All,

First time poster here.  I am considering making the move to VNC
personal.  I am mainly needing to access my work printer(s) from my
laptop when I am at home or on the road. I would also like access to
my home computer from my laptop as well.  How would I purchase
licenses for this?  Would I buy a personal license for each machine or
could I mix personal and free licenses?

Thanks a bunch,


Patrick Immel
Lighting and Scenic Designer
Northwest Missouri State University
patrickimmel.com

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list




___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Command-line connection to listening client from Vista machine? [now SCRIPTS]

[Philip Herlihy]

EDIT is pretty old stuff.  I just use notepad, or maybe an advanced
programmer's editor like ConText or Crimson Editor (which can highlight
keywords, both free).  Sometimes I use Vi on Windows for the Regular
Expression support!  Just create the text anyhow and save with either .cmd
(preferred) or .bat extension (see here
http://en.wikipedia.org/wiki/Batch_file  for differences) - then run it.
 
The VB family (VB, VBA, VBS) are different.  They need a runtime to
provide library functions.  In Excel VBA, the runtime is built into Excel
(VBA scripts don't run in isolation).  In full-blown VB, you have to provide
a runtime as part of the installation package.  With VBS, you can use
Cscript.exe or Wscript.exe to provide the necessary environment within the
NT command-line environment.  See http://support.microsoft.com/kb/232211 for
more, or see http://technet.microsoft.com/en-gb/scriptcenter/default.aspx
for tons of stuff.  Do understand that vanilla NT scripting is considered
really old hat these days.
 
After my signature I'll paste in a recent (crude) example NT script.  Copy
into Notepad and save as PingMonitor.cmd and run it.  All it does is loop,
pinging an IP address (set in a variable), in this case the BBC.  When it
responds, it plays a sound (your path may vary, as may your file association
for *.wav files), changes the colour of the text in the window and sets the
window's title to ### UP ###.  You can leave it running in the background,
minimised, and if you glance at the taskbar icon it tells you the connection
status of the remote machine - that's if you don't notice Windows Media
Player popping up to play the TADA sound!  If you need to stop it, use
Control-C in the command window.
 
If you have VNC running on remote machines which get their addresses from
DHCP, then you have two options.  Run a listening client at your end, and
manage your own incoming port forwarding for port 5500.  Then the client
simply has to right-click their VNC server icon and enter your IP or domain
address, and it'll connect.  To speed this up, you can leave a command
script on their desktop (etc) which runs:
WinVNC4.exe -connect   YOURADDRESS
I've wrapped mine up in all sorts of VBS which pops up an information panel
and checks for a running server - this now needs work to cope with Vista.
If you're trying to initiate a connection from a Vista box running VNC as a
service you need to add -service in the line above.  Here the user is
connecting to you, of course.
 
The other option is to use Dynamic DNS.  I use DynDNS.com.  You register for
an account, and add a (free) Dynamic DNS hostname.  It picks up your current
IP address, and links that with a third-level domain name you invent,
choosing from a range of second-level domains available.  To maintain the
connection when the IP address changes, you should download, configure and
run the updating client available on the DynDNS site (under support).  Works
a treat - usually propagates within 5 to 10 minutes after the new address is
detected by the update client.  Then, if port forwarding is configured (or
unnecessary) at the remote end, and firewalls are appropriately set, you can
simply give the DynDNS domain name as the remote (server) address in the VNC
client.  DynDNS have paid-for services which you might need, depending on
your requirements.
 
If you're reaching a number of machines through one (reasonably
sophisticated) router, you can set up rules to accept VNC connections on
other ports (add a double-colon and the port number after the address in the
client's address box) and have the router configured to route it to the
preferred machine, translating the port to 5900, the standard one for VNC.
If your router can't do that, then you can configure VNC to respond on a
different port, and route that port to the particular machine.
 
Hope that helps.
 
Philip Herlihy  
:   
:   
:   
:   
 
Here's that example NT script:
=
 
set addr=212.58.254.252 
echo off
title down
color 0C
:loop
ping -n 1 -w 1 %addr% | grep -i TTL
if errorlevel 1 GOTO :loop
color 0A
title ### UP ###
C:\WINDOWS\Media\tada.wav
pause


  _  

From: Dale Eshelman [mailto:eshelm...@gmail.com] 
Sent: 05 July 2009 17:12
To: Philip Herlihy
Subject: Re: Command-line connection to listening client from Vista machine?
[now SCRIPTS]


Thanks  
I have wondered how to do this in Windows. I have written DOS batch files,
UNIX scripts, written COBAL programs, written al lot of Excel macros in
Visual Basic for Applications (VBA). Have heard IT people talk about writing
SCRPTS but did not know what that meant.
I have gone to start-run and typed EDIT. Entered DOS commands and saved the
file with and extension BAT. Did not know there is a command line in Windows
and I guess that is cscript.exe. But not sure how to open a blank window to
enter script. Or do you just open a text editor and start typing, save with
an extension

RE: Command-line connection to listening client from Vista machine? [now SCRIPTS]

[Philip Herlihy]

Sorry it's taken so long to respond - inundated with email lately!

From the way you frame your question it sounds as if scripting would be a
new avenue for you.  I'll give a brief summary here (for fear of
exasperating experienced scripters).  If you want more information, contact
me direct.

Scripting simply means storing a series of commands in a file and then
running the file in one go.  It's a close cousin to programming - loosely,
programs are normally converted into a binary program by a compiler, while
scripts are usually interpreted line by line by some other running
program.

There are several interpreters available for Windows NT and its
descendents.  If you click Start, Run, then type CMD and click OK you'll get
the familiar DOS-like command interpreter.  With a few adjustments, anything
you type in there can be stored in a script and run.  If you put the
following lines in a text file:

DIR
PAUSE

.. and save that as mytest.cmd (not mytest.txt) you can double-click it and
you'll see the black window appear with the output of the DIR command (which
lists files) and a line inviting you to press any key to continue (at which
point the screen disappears, which is why many of my scripts end with
PAUSE!).  If you Google for NT Command Line or NT Command Scripting
you'll find loads of resources, and I rather like the book on NT Shell
Scripting by Tim Hill (Macmillan 1998).  I tend to use plain NT scripting
for simple scripts.

Other interpreters include Windows Scripting Host (usually already
installed as part of Windows) which can interpret Visual Basic Script (VBS)
commands, which are much more powerful than the rather creaky NT
command-line interface.  I tend to use VBS for more complex scripts, as the
error-handling in NT scripting is rudimentary.  VBS can also interact with
Excel and other Office programs in a sophisticated way.

More recently another interpreter has become available, and this promises
something like the (awesome and underused) power of Unix scripting:
PowerShell.  Non-trivial, but immensely powerful.  Some of Microsoft's
flagship server products are expected to be administered mainly by
Powershell scripting in their most recent versions.  I got through two
chapters of the book (still next to my workstation) before other work blew
that away...

How does this affect RealVNC users?  Well, I provide the people I support
with a simple script which they click to connect to my listening client.
I've set up port-forwarding at my end to allow port 5500 through to my
preferred machine, and all Uncle Joe has to do to get my help is
double-click the script's icon on their desktop.  The advantage of this
arrangement is that I can deal with firewall problems at my end without
having to get them to fiddle with such mysteries at their end - it just
works.  I think it would also be possible to create a script which would
check regularly for a working connection and reconnect if none existed, but
that's for another day/month/year.

In the past (XP and earlier) I've used a script which pops up an explanatory
message box first (giving the option to cancel in case of a finger-fumble),
then checks for a running server and then connects to my hard-coded address.
I'll be happy to send you (or anyone else interested) a copy of this on
request.  The essential line is:

WinVNC4.exe -connect phils-domain-address

.. where phils-domain-address is a domain name provided by my ISP, although
an IP address will do.  If you have a dynamic IP address, you can use
DynDNS.com (free) to set up a domain name which will track your changing IP
address (assuming you run the update client on at least one running
machine).

My original question was about Vista.  I've found that including the term
-service in the line above allows the connection to work (in the
configurations I've set up), but I need to modify my script to check whether
a server is running as a service or in user-mode, or not at all.
Nevertheless, if you get the person needing support to check manually if the
server is running (task manager or spot the icon) then that one line may be
all you need in a simple script.  Lord knows when I'll get round to doing
the modification to my script, but I doubt it'll turn out to be any more
difficult than what worked well for XP.

I must say that the documentation for Command Line use of RealVNC is rather
inadequate (or is it just hard-to-find?).

Hope that's useful.


Philip Herlihy, London



-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Dale Eshelman
Sent: 21 June 2009 06:11
To: Philip Herlihy
Cc: vnc-list@realvnc.com
Subject: Re: Command-line connection to listening client from Vista machine?

I would be interested to know how to create a script in WXP Pro as I  
have never done it.
Can you provide more information on how to create a script to use and  
how then to use the script?

On Jun 20, 2009, at 8:10 AM, Philip Herlihy wrote:

 On XP

Command-line connection to listening client from Vista machine?

[Philip Herlihy]

On XP machines I've set up a script which invokes a connection to a
listening client:
 
vinvnc4.ext - connect  MyClientHost.MyDomain.com
 
- very useful.  This doesn't work on Vista.  Can anyone advise on how I'd do
the equivalent from a command-line or command-file?  The Vista box has VNC
running as a service.
 
Phil, London
 
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC on MAC viewing a windows based device

[Philip Herlihy]

Not an expert in this forum, but I thought I'd venture an opinion:

Almost certainly not.  To use VNC you have to have a server process
running on the machine you want to control.  Servers are available for
Windows (the Personal Edition covers Vista) and the Mac (Enterprise version)
etc, but for a DVR?  Well, I guess it's possible that it's running some
Linux variant, but you're unlikely to find it easy to install anything else
on it (hats off if you manage it).  I guess this is one of those situations
where the Mac's ability to conceal complexity is balanced by a lack of
support by developers of niche software products.

I did follow up the thought that you can indeed get Internet Explorer for
the Mac, but although that (apparently) has the capability of running
ActiveX controls, those controls themselves (which are produced by
third-party software developers) almost certainly won't run on the Mac
platform - if they do, they'll surely advertise the fact.

You could, I guess, run a VNC connection from your Mac onto a Windows
machine running RealVNC and so run IE at one remove.  Video performance is
poor over such a connection, though.  Best I can suggest, apart from
contacting the DVR manufacturers (who will probably just shrug).

Phil, London





-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Howard Schroeder
Sent: 07 June 2009 19:13
To: vnc-list@realvnc.com
Subject: VNC on MAC viewing a windows based device

I have a situation where I need to be able to operate a windows based DVR
but I use a MAC laptop.  I understand that MAC do not support the Activex
control capability needed so I was hoping to be able to use VNC to remotely
operate the DVR and view the cameras via a remote session. Is this possible?

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Cursor weirdness - problem vanished

[Philip Herlihy]

Overnight, the problem simply went away.

How weird is that?  (Rebooting hadn't fixed it).  I was all set to reinstall
the graphics drivers.

Phil

-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Philip Herlihy
Sent: 04 June 2009 00:10
To: vnc-list@realvnc.com
Subject: RE: Cursor weirdness

Update:  I'd been playing around with screen resolution on the target
machine, increasing it beyond what the attached physical monitor can handle
as I'd been using this machine to run daisy-chained VNC sessions to other
machines on the subnet - machines with higher screen resolution.  I did
manage to set it back, but the problem persists.  I'd also been playing with
scaling for the first time.

I find I can connect without problems to other machines on the same subnet
(I set up a further port-forwarding on the router) without problems.  I can
daisy-chain a further session to access machine C from machine B without
any problems, but machine A is still weird.  If I connect to machine B and
run a further VNC session to machine A the problem is evident on A but not
B, just as if I'd connected directly.  If I connect as I've always done to
machine A, and then daisy-chain another session onto machine C, the
weirdness affects both sessions.  It does seem to be a problem with machine
A.  I've rebooted machine A, and the router, and my machine, and my router -
problem persists.  Advice greatly appreciated.

My machine is XP; machine A runs Win2K, B runs Win2K and C runs XP.  

Phil


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Philip Herlihy
Sent: 03 June 2009 23:44
To: vnc-list@realvnc.com
Subject: Cursor weirdness

I'm trying to connect tonight to a machine I've accessed many hundreds of
times.  Nothing has changed that I'm aware of, except that the pointer
doesn't seem to be in the right place.  I can't click on things, and I've
just noticed that when I move the mouse I get the familiar dot and also a
flickering pointer some distance away on the screen.  There is an offset of
(say) 300 pixels.  What could be doing this, and how can I fix it?
 
Phil, London
 

 
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Cursor weirdness

[Philip Herlihy]

I'm trying to connect tonight to a machine I've accessed many hundreds of
times.  Nothing has changed that I'm aware of, except that the pointer
doesn't seem to be in the right place.  I can't click on things, and I've
just noticed that when I move the mouse I get the familiar dot and also a
flickering pointer some distance away on the screen.  There is an offset of
(say) 300 pixels.  What could be doing this, and how can I fix it?
 
Phil, London
 

 
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Cursor weirdness

[Philip Herlihy]

Update:  I'd been playing around with screen resolution on the target
machine, increasing it beyond what the attached physical monitor can handle
as I'd been using this machine to run daisy-chained VNC sessions to other
machines on the subnet - machines with higher screen resolution.  I did
manage to set it back, but the problem persists.  I'd also been playing with
scaling for the first time.

I find I can connect without problems to other machines on the same subnet
(I set up a further port-forwarding on the router) without problems.  I can
daisy-chain a further session to access machine C from machine B without
any problems, but machine A is still weird.  If I connect to machine B and
run a further VNC session to machine A the problem is evident on A but not
B, just as if I'd connected directly.  If I connect as I've always done to
machine A, and then daisy-chain another session onto machine C, the
weirdness affects both sessions.  It does seem to be a problem with machine
A.  I've rebooted machine A, and the router, and my machine, and my router -
problem persists.  Advice greatly appreciated.

My machine is XP; machine A runs Win2K, B runs Win2K and C runs XP.  

Phil


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Philip Herlihy
Sent: 03 June 2009 23:44
To: vnc-list@realvnc.com
Subject: Cursor weirdness

I'm trying to connect tonight to a machine I've accessed many hundreds of
times.  Nothing has changed that I'm aware of, except that the pointer
doesn't seem to be in the right place.  I can't click on things, and I've
just noticed that when I move the mouse I get the familiar dot and also a
flickering pointer some distance away on the screen.  There is an offset of
(say) 300 pixels.  What could be doing this, and how can I fix it?
 
Phil, London
 

 
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Indirect connection works better

[Philip Herlihy]

Correction (sorry):

Netsh firewall set  icmpsetting, REM doesn't change anything, just shows
options

... Should be:

Netsh firewall set  icmpsetting  REM doesn't change anything, just shows
options

(ampersand, not comma)


Philip Herlihy   



-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Philip Herlihy
Sent: 18 May 2009 20:24
To: vnc-list@realvnc.com
Subject: RE: Indirect connection works better

Something else I found:  Try this in a command prompt (XP SP1+):

Netsh firewall show icmpsetting
Netsh firewall set  icmpsetting, REM doesn't change anything, just shows
options.

See:  http://support.microsoft.com/kb/875357


Philip Herlihy   


-Original Message-
From: Philip Herlihy [mailto:phi...@herlihy.eu.com] 
Sent: 18 May 2009 20:11
To: 'vnc-list@realvnc.com'
Subject: RE: Indirect connection works better

Thanks to John, and James, for very interesting pointers.

I'll experiment on the affected systems and see what I can demonstrate, but
I'd like some feedback on these ideas first, if anyone has any!

As I understand it, MTU (Maximum Transmission Unit) describes the size of
the largest packet to (be expected to) get through the network without being
fragmented.  Different types of network (e.g. dial-up) work best with
different sizes of MTU.  The default (if there is one) is 1500, with other
sizes down to 1400 being suggested for different situations.  Netgear
suggest trying 1400 to solve most problems:
http://kb.netgear.com/app/answers/detail/a_id/1153

This article describes an empirical way of checking what MTU works best in a
given situation:
http://www.dslreports.com/faq/5793

Now, in the situation I'm most concerned about, I have my machine, my router
(on which I can change the MTU at will), the office router (ditto), two
wireless access points (neither have an MTU setting) and the destination
machine(s).  Changing the MTU on the end machines will involve a registry
hack after identifying the interface:
http://help.expedient.com/broadband/mtu.shtml
Am I right in thinking that if I lower the MTU on any one of them, it'll be
effective across the entire connection?  Which one should I change first?

I've also remembered a situation I encountered some years ago when a
firewall was found to be blocking ICMP packets.  For anyone following this,
ICMP is a collection (as I understand it) of control protocols which can
be necessary for a TCP connection to tune itself.  See:
http://technet.microsoft.com/en-us/library/cc758065(WS.10).aspx 
I found (can't remember the details) that allowing ICMP unblocked this
particular jam.  See: http://www.dslreports.com/faq/2520

Is this likely to be relevant here?  I could do with someone who actually
knows more than I can find on Google to share some experience!


Philip Herlihy   



-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of John Serink
Sent: 15 May 2009 01:37
To: vnc-list@realvnc.com
Subject: Re: Indirect connection works better

You have an MTU issue.
If you have access to the router/gateway you need to put a tcp mssadjust
 command in the outgoing interface, usually eth0 or something like that
where  is the max mtu of you internet connection.

A more painful alternative is to change the mtu on the individual machine
giving you problems.

Cheers,
John

- Original Message -
From: vnc-list-boun...@realvnc.com vnc-list-boun...@realvnc.com
To: vnc-list@realvnc.com vnc-list@realvnc.com
Sent: Fri May 15 02:34:03 2009
Subject: Indirect connection works better

Recent came across a situation again which has puzzled me in the past.  I'm
trying to connect to a machine running VNC Free edition in an office.  I can
make the connection (having set up port forwarding on the router) but it
hangs, with only the top third of the screen visible after several minutes.
Further attempts produced the same result.
 
That office has a workstation used as a simple workstation.  Unlike the
target machine, which is wirelessly connected, this one is connected to
the router by cable.  I can connect reliably to the fileserver PC.  I found
that within my remote session I could start a new session from the
fileserver PC to the target PC, and this worked well.
 
Now that's using the same links, but in two jumps instead of one.  What's
going on?
 
Phil, London
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Indirect connection works better

[Philip Herlihy]

Thanks to John, and James, for very interesting pointers.

I'll experiment on the affected systems and see what I can demonstrate, but
I'd like some feedback on these ideas first, if anyone has any!

As I understand it, MTU (Maximum Transmission Unit) describes the size of
the largest packet to (be expected to) get through the network without being
fragmented.  Different types of network (e.g. dial-up) work best with
different sizes of MTU.  The default (if there is one) is 1500, with other
sizes down to 1400 being suggested for different situations.  Netgear
suggest trying 1400 to solve most problems:
http://kb.netgear.com/app/answers/detail/a_id/1153

This article describes an empirical way of checking what MTU works best in a
given situation:
http://www.dslreports.com/faq/5793

Now, in the situation I'm most concerned about, I have my machine, my router
(on which I can change the MTU at will), the office router (ditto), two
wireless access points (neither have an MTU setting) and the destination
machine(s).  Changing the MTU on the end machines will involve a registry
hack after identifying the interface:
http://help.expedient.com/broadband/mtu.shtml
Am I right in thinking that if I lower the MTU on any one of them, it'll be
effective across the entire connection?  Which one should I change first?

I've also remembered a situation I encountered some years ago when a
firewall was found to be blocking ICMP packets.  For anyone following this,
ICMP is a collection (as I understand it) of control protocols which can
be necessary for a TCP connection to tune itself.  See:
http://technet.microsoft.com/en-us/library/cc758065(WS.10).aspx 
I found (can't remember the details) that allowing ICMP unblocked this
particular jam.  See: http://www.dslreports.com/faq/2520

Is this likely to be relevant here?  I could do with someone who actually
knows more than I can find on Google to share some experience!


Philip Herlihy   



-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of John Serink
Sent: 15 May 2009 01:37
To: vnc-list@realvnc.com
Subject: Re: Indirect connection works better

You have an MTU issue.
If you have access to the router/gateway you need to put a tcp mssadjust
 command in the outgoing interface, usually eth0 or something like that
where  is the max mtu of you internet connection.

A more painful alternative is to change the mtu on the individual machine
giving you problems.

Cheers,
John

- Original Message -
From: vnc-list-boun...@realvnc.com vnc-list-boun...@realvnc.com
To: vnc-list@realvnc.com vnc-list@realvnc.com
Sent: Fri May 15 02:34:03 2009
Subject: Indirect connection works better

Recent came across a situation again which has puzzled me in the past.  I'm
trying to connect to a machine running VNC Free edition in an office.  I can
make the connection (having set up port forwarding on the router) but it
hangs, with only the top third of the screen visible after several minutes.
Further attempts produced the same result.
 
That office has a workstation used as a simple workstation.  Unlike the
target machine, which is wirelessly connected, this one is connected to
the router by cable.  I can connect reliably to the fileserver PC.  I found
that within my remote session I could start a new session from the
fileserver PC to the target PC, and this worked well.
 
Now that's using the same links, but in two jumps instead of one.  What's
going on?
 
Phil, London
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Indirect connection works better

[Philip Herlihy]

Something else I found:  Try this in a command prompt (XP SP1+):

Netsh firewall show icmpsetting
Netsh firewall set  icmpsetting, REM doesn't change anything, just shows
options.

See:  http://support.microsoft.com/kb/875357


Philip Herlihy   


-Original Message-
From: Philip Herlihy [mailto:phi...@herlihy.eu.com] 
Sent: 18 May 2009 20:11
To: 'vnc-list@realvnc.com'
Subject: RE: Indirect connection works better

Thanks to John, and James, for very interesting pointers.

I'll experiment on the affected systems and see what I can demonstrate, but
I'd like some feedback on these ideas first, if anyone has any!

As I understand it, MTU (Maximum Transmission Unit) describes the size of
the largest packet to (be expected to) get through the network without being
fragmented.  Different types of network (e.g. dial-up) work best with
different sizes of MTU.  The default (if there is one) is 1500, with other
sizes down to 1400 being suggested for different situations.  Netgear
suggest trying 1400 to solve most problems:
http://kb.netgear.com/app/answers/detail/a_id/1153

This article describes an empirical way of checking what MTU works best in a
given situation:
http://www.dslreports.com/faq/5793

Now, in the situation I'm most concerned about, I have my machine, my router
(on which I can change the MTU at will), the office router (ditto), two
wireless access points (neither have an MTU setting) and the destination
machine(s).  Changing the MTU on the end machines will involve a registry
hack after identifying the interface:
http://help.expedient.com/broadband/mtu.shtml
Am I right in thinking that if I lower the MTU on any one of them, it'll be
effective across the entire connection?  Which one should I change first?

I've also remembered a situation I encountered some years ago when a
firewall was found to be blocking ICMP packets.  For anyone following this,
ICMP is a collection (as I understand it) of control protocols which can
be necessary for a TCP connection to tune itself.  See:
http://technet.microsoft.com/en-us/library/cc758065(WS.10).aspx 
I found (can't remember the details) that allowing ICMP unblocked this
particular jam.  See: http://www.dslreports.com/faq/2520

Is this likely to be relevant here?  I could do with someone who actually
knows more than I can find on Google to share some experience!


Philip Herlihy   



-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of John Serink
Sent: 15 May 2009 01:37
To: vnc-list@realvnc.com
Subject: Re: Indirect connection works better

You have an MTU issue.
If you have access to the router/gateway you need to put a tcp mssadjust
 command in the outgoing interface, usually eth0 or something like that
where  is the max mtu of you internet connection.

A more painful alternative is to change the mtu on the individual machine
giving you problems.

Cheers,
John

- Original Message -
From: vnc-list-boun...@realvnc.com vnc-list-boun...@realvnc.com
To: vnc-list@realvnc.com vnc-list@realvnc.com
Sent: Fri May 15 02:34:03 2009
Subject: Indirect connection works better

Recent came across a situation again which has puzzled me in the past.  I'm
trying to connect to a machine running VNC Free edition in an office.  I can
make the connection (having set up port forwarding on the router) but it
hangs, with only the top third of the screen visible after several minutes.
Further attempts produced the same result.
 
That office has a workstation used as a simple workstation.  Unlike the
target machine, which is wirelessly connected, this one is connected to
the router by cable.  I can connect reliably to the fileserver PC.  I found
that within my remote session I could start a new session from the
fileserver PC to the target PC, and this worked well.
 
Now that's using the same links, but in two jumps instead of one.  What's
going on?
 
Phil, London
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Indirect connection works better

[Philip Herlihy]

Recent came across a situation again which has puzzled me in the past.  I'm
trying to connect to a machine running VNC Free edition in an office.  I can
make the connection (having set up port forwarding on the router) but it
hangs, with only the top third of the screen visible after several minutes.
Further attempts produced the same result.
 
That office has a workstation used as a simple workstation.  Unlike the
target machine, which is wirelessly connected, this one is connected to
the router by cable.  I can connect reliably to the fileserver PC.  I found
that within my remote session I could start a new session from the
fileserver PC to the target PC, and this worked well.
 
Now that's using the same links, but in two jumps instead of one.  What's
going on?
 
Phil, London
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Indirect connection works better

[Philip Herlihy]

Thanks, Wez - however, in response to guidance you gave me once before I
already have that setting enabled.

What puzzles me is that either route is using the same links, so it's hard
to understand what the difference might be.


Philip Herlihy   



-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of James Weatherall
Sent: 14 May 2009 16:21
To: 'Philip Herlihy'; vnc-list@realvnc.com
Subject: RE: Indirect connection works better

Hi Philip,

Some Wi-Fi routers have trouble handling large numbers of small network
packets, such as are produced when moving the mouse around in the VNC
session, and that in turn can upset the Windows TCP stack and lead to the
sort of behaviour you're seeing.

You can enable the Pointer event rate-limiting feature in the VNC Viewer
to work around this problem.

Cheers,

--
Wez @ RealVNC Ltd


 -Original Message-
 From: vnc-list-boun...@realvnc.com [mailto:vnc-list-
 boun...@realvnc.com] On Behalf Of Philip Herlihy
 Sent: 14 May 2009 15:34
 To: vnc-list@realvnc.com
 Subject: Indirect connection works better
 
 Recent came across a situation again which has puzzled me in the past.
 I'm
 trying to connect to a machine running VNC Free edition in an office.
 I can
 make the connection (having set up port forwarding on the router) but
 it
 hangs, with only the top third of the screen visible after several
 minutes.
 Further attempts produced the same result.
 
 That office has a workstation used as a simple workstation.  Unlike the
 target machine, which is wirelessly connected, this one is connected
 to
 the router by cable.  I can connect reliably to the fileserver PC.  I
 found
 that within my remote session I could start a new session from the
 fileserver PC to the target PC, and this worked well.
 
 Now that's using the same links, but in two jumps instead of one.
 What's
 going on?
 
 Phil, London
 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Indirect connection works better

[Philip Herlihy]

Thanks, Wez,

In fact both routes use WiFi for the last leg, but your point about MTU is
an interesting one.  How do I assess the real and imaginary MTUs?

(Offline for 24 hours from now, but still interested!) 


Philip Herlihy   


-Original Message-
From: James Weatherall [mailto:j...@realvnc.com] 
Sent: 14 May 2009 17:24
To: 'Philip Herlihy'; vnc-list@realvnc.com
Subject: RE: Indirect connection works better

Hi Philip,

Sorry to hear that.  The difference you've highlighted is that the target
machine is on Wi-Fi, not cable, which can cause issues.  You might also
check, for instance, what the target computer thinks the MTU of the Wi-Fi
network is, and compare that to what it really is - if it's smaller than the
server thinks it is then the connection is likely to stall as soon as a
significant amount of data gets transferred.

Regards,

--
Wez @ RealVNC Ltd


 -Original Message-
 From: vnc-list-boun...@realvnc.com [mailto:vnc-list-
 boun...@realvnc.com] On Behalf Of Philip Herlihy
 Sent: 14 May 2009 17:09
 To: vnc-list@realvnc.com
 Subject: RE: Indirect connection works better
 
 Thanks, Wez - however, in response to guidance you gave me once before
 I
 already have that setting enabled.
 
 What puzzles me is that either route is using the same links, so it's
 hard
 to understand what the difference might be.
 
 
 Philip Herlihy
 
 
 
 -Original Message-
 From: vnc-list-boun...@realvnc.com [mailto:vnc-list-
 boun...@realvnc.com] On
 Behalf Of James Weatherall
 Sent: 14 May 2009 16:21
 To: 'Philip Herlihy'; vnc-list@realvnc.com
 Subject: RE: Indirect connection works better
 
 Hi Philip,
 
 Some Wi-Fi routers have trouble handling large numbers of small network
 packets, such as are produced when moving the mouse around in the VNC
 session, and that in turn can upset the Windows TCP stack and lead to
 the
 sort of behaviour you're seeing.
 
 You can enable the Pointer event rate-limiting feature in the VNC
 Viewer
 to work around this problem.
 
 Cheers,
 
 --
 Wez @ RealVNC Ltd
 
 
  -Original Message-
  From: vnc-list-boun...@realvnc.com [mailto:vnc-list-
  boun...@realvnc.com] On Behalf Of Philip Herlihy
  Sent: 14 May 2009 15:34
  To: vnc-list@realvnc.com
  Subject: Indirect connection works better
 
  Recent came across a situation again which has puzzled me in the
 past.
  I'm
  trying to connect to a machine running VNC Free edition in an office.
  I can
  make the connection (having set up port forwarding on the router) but
  it
  hangs, with only the top third of the screen visible after several
  minutes.
  Further attempts produced the same result.
 
  That office has a workstation used as a simple workstation.  Unlike
 the
  target machine, which is wirelessly connected, this one is
 connected
  to
  the router by cable.  I can connect reliably to the fileserver PC.  I
  found
  that within my remote session I could start a new session from the
  fileserver PC to the target PC, and this worked well.
 
  Now that's using the same links, but in two jumps instead of one.
  What's
  going on?
 
  Phil, London
  ___
  VNC-List mailing list
  VNC-List@realvnc.com
  To remove yourself from the list visit:
  http://www.realvnc.com/mailman/listinfo/vnc-list
 
 
 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list
 
 
 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Indirect connection works better

[Philip Herlihy]

Have tried lowering resolution, but to no avail.


Philip Herlihy   


-Original Message-
From: vnc-list-boun...@realvnc.com [mailto:vnc-list-boun...@realvnc.com] On
Behalf Of Dale Eshelman
Sent: 14 May 2009 17:25
To: 'Philip Herlihy'; vnc-list@realvnc.com; james.weather...@realvnc.com
Cc: dean.eshel...@gmail.com
Subject: RE: Indirect connection works better


I find this interesting. I have seen this issue and did not know how to fix
it. I do now.

The other issue I have seen is the screen saver stays on and the page does
not refresh after connect. I have found adjusting to a lower resolution
manually rather than the let the server decide option fixes this as well.

Dale

--- On Thu, 5/14/09, James Weatherall j...@realvnc.com wrote:

 From: James Weatherall j...@realvnc.com
 Subject: RE: Indirect connection works better
 To: 'Philip Herlihy' phi...@herlihy.eu.com, vnc-list@realvnc.com
 Date: Thursday, May 14, 2009, 10:20 AM
 Hi Philip,
 
 Some Wi-Fi routers have trouble handling large numbers of
 small network packets, such as are produced when moving the
 mouse around in the VNC session, and that in turn can upset
 the Windows TCP stack and lead to the sort of behaviour
 you're seeing.
 
 You can enable the Pointer event rate-limiting feature in
 the VNC Viewer to work around this problem.
 
 Cheers,
 
 --
 Wez @ RealVNC Ltd
 
 
  -Original Message-
  From: vnc-list-boun...@realvnc.com
 [mailto:vnc-list-
  boun...@realvnc.com]
 On Behalf Of Philip Herlihy
  Sent: 14 May 2009 15:34
  To: vnc-list@realvnc.com
  Subject: Indirect connection works better
  
  Recent came across a situation again which has puzzled
 me in the past.
  I'm
  trying to connect to a machine running VNC Free
 edition in an office.
  I can
  make the connection (having set up port forwarding on
 the router) but
  it
  hangs, with only the top third of the screen visible
 after several
  minutes.
  Further attempts produced the same result.
  
  That office has a workstation used as a simple
 workstation.  Unlike the
  target machine, which is wirelessly connected, this
 one is connected
  to
  the router by cable.  I can connect reliably to
 the fileserver PC.  I
  found
  that within my remote session I could start a new
 session from the
  fileserver PC to the target PC, and this worked well.
  
  Now that's using the same links, but in two jumps
 instead of one.
  What's
  going on?
  
  Phil, London
  ___
  VNC-List mailing list
  VNC-List@realvnc.com
  To remove yourself from the list visit:
  http://www.realvnc.com/mailman/listinfo/vnc-list
 
 
 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list
 


  

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list


___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC-List digest, Vol 1 #2596 - 4 msgs

[Philip Herlihy]

Clarification:

I provide a shortcut on their desktop which connects their VNC server to my
listening client.

(That could have been very misleading!)

Phil

-Original Message-
Message: 4
From: Philip Herlihy phi...@herlihy.eu.com
To: 'Roger Withnell' ro...@upperbridge.co.uk, vnc-list@realvnc.com
Subject: RE: Connecting to a server behind a router
Date: Sun, 25 Jan 2009 21:22:16 -

For the second scenario, you have to have a server on your customer's
machine.  Oddly enough I've just described this scenario on this mailing
list.

I'm not aware of a way of getting the VNC server onto the client's machine
without getting them to install it, although if you Google for PCHelpware or
UltraVNC SC you'll see there are solutions available where the server is a
single downloadable which runs without installation.  I'd certainly be
interested myself in a way of getting RealVNC on a customer's machine
without them having to install it.  Some customers have managed to install
the server themselves following instructions I've put on the web, but most
assume (wrongly) that it's beyond them, and I end up visiting first.  I'm
not short of work, so I don't miss the ones I can't get to.

I've wondered if it's possible to script an installation, or provide a msi
file, but I've not had time to look into this.

Once you have the server on the customer's machine, you can use the
listening client method to set up the first connection, and use that to
configure their router to allow incoming connections.  I provide a shortcut
on their desktop which runs the listening client.

HTH

Phil
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Connecting to a server behind a router

[Philip Herlihy]

Two alternatives:

1)  Configure your router to forward any incoming connection using the
relevant port (5800 for the web browser connection) to the computer hosting
VNC.  See www.portforward.com for help with this (and your router's
manual!).  Most routers provide this facility, although terminology varies:
look for virtual servers or port forwarding.

If you have multiple machines running VNC, some routers allow you to
translate the port number, so you can configure port 8000 (say) to route
to one VNC server operating on 5800, and 8001 (say) to a different machine,
also on 5800, which makes it easy to access several machines on one network
via a single router.  Alternatively you can set your VNC servers to use
different ports (5800, 5801) and route those ports to the various machines.
You'd connect using the IP address (e.g.) http://aaa.bbb.ccc.ddd::5801 (not
double colon). You may not need this, but it's worth mentioning for
completeness.

2)  You're using the web browser interface, but if you use the standard
server connection (defaults to port 5900) you can achieve a connection if
you initiate it in the reverse direction - from the server, instead of to
the server.  You have to run a listening client on the machine at the
other end, then use the right-click menu on the VNC tray icon to add a new
client, supplying the IP address.  If the client PC is directly connected
to the Internet (e.g. by dial-up), or if the listening port 5500 is being
correctly forwarded by any router at that end, then the connection will be
made.  This is a useful way of operating for anyone supporting a number of
friends or clients who may not have the knowledge or patience to configure
routers at their end.

HTH

Phil, London

-Original Message-
...

Message: 1
From: Roger Withnell ro...@upperbridge.co.uk
To: vnc-list@realvnc.com
Subject: Connecting to a server behind a router
Date: Sat, 24 Jan 2009 19:23:26 -

My Server is 192.168.2.2 on my private network.
I can connect from the Viewer with http://192.168.2.2:5800 .

My static IP address is a.b.c.d

What is the address syntax to connect from a Viewer's browser over the
Internet to my Server.
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Connecting to a server behind a router

[Philip Herlihy]

For the second scenario, you have to have a server on your customer's
machine.  Oddly enough I've just described this scenario on this mailing
list.

I'm not aware of a way of getting the VNC server onto the client's machine
without getting them to install it, although if you Google for PCHelpware or
UltraVNC SC you'll see there are solutions available where the server is a
single downloadable which runs without installation.  I'd certainly be
interested myself in a way of getting RealVNC on a customer's machine
without them having to install it.  Some customers have managed to install
the server themselves following instructions I've put on the web, but most
assume (wrongly) that it's beyond them, and I end up visiting first.  I'm
not short of work, so I don't miss the ones I can't get to.

I've wondered if it's possible to script an installation, or provide a msi
file, but I've not had time to look into this.

Once you have the server on the customer's machine, you can use the
listening client method to set up the first connection, and use that to
configure their router to allow incoming connections.  I provide a shortcut
on their desktop which runs the listening client.

HTH

Phil

-Original Message-
From: Roger Withnell [mailto:ro...@upperbridge.co.uk] 
Sent: 25 January 2009 16:40
To: 'Philip Herlihy'; vnc-list@realvnc.com
Subject: RE: Connecting to a server behind a router

Thanks Philip.

I have two applications:  selling our websites to prospects; and helping
customers when they have problems.

Selling our websites to prospects:
I think I am set up for this correctly now.  I am the server and the
prospect uses a browser to view my desktop.  I can then demonstrate the
website on my server desktop to the prospect on the viewer desktop.

Helping customers when they have problems:
Now I want to see, and operate, my customers desktop to help with their
problems without the customer having to set up anything on their computer.

I think your last paragraph refers to this but I'm not sure.  Can you give
me a step by step procedure as to how I set this up.

Thanking you in anticipation.

Yours
 
Roger

-Original Message-
From: vnc-list-ad...@realvnc.com [mailto:vnc-list-ad...@realvnc.com] On
Behalf Of Philip Herlihy
Sent: 25 January 2009 12:32
To: vnc-list@realvnc.com; ro...@upperbridge.co.uk
Subject: RE: Connecting to a server behind a router

Two alternatives:

1)  Configure your router to forward any incoming connection using the
relevant port (5800 for the web browser connection) to the computer hosting
VNC.  See www.portforward.com for help with this (and your router's
manual!).  Most routers provide this facility, although terminology varies:
look for virtual servers or port forwarding.

If you have multiple machines running VNC, some routers allow you to
translate the port number, so you can configure port 8000 (say) to route
to one VNC server operating on 5800, and 8001 (say) to a different machine,
also on 5800, which makes it easy to access several machines on one network
via a single router.  Alternatively you can set your VNC servers to use
different ports (5800, 5801) and route those ports to the various machines.
You'd connect using the IP address (e.g.) http://aaa.bbb.ccc.ddd::5801 (not
double colon). You may not need this, but it's worth mentioning for
completeness.

2)  You're using the web browser interface, but if you use the standard
server connection (defaults to port 5900) you can achieve a connection if
you initiate it in the reverse direction - from the server, instead of to
the server.  You have to run a listening client on the machine at the
other end, then use the right-click menu on the VNC tray icon to add a new
client, supplying the IP address.  If the client PC is directly connected
to the Internet (e.g. by dial-up), or if the listening port 5500 is being
correctly forwarded by any router at that end, then the connection will be
made.  This is a useful way of operating for anyone supporting a number of
friends or clients who may not have the knowledge or patience to configure
routers at their end.

HTH

Phil, London

-Original Message-
...

Message: 1
From: Roger Withnell ro...@upperbridge.co.uk
To: vnc-list@realvnc.com
Subject: Connecting to a server behind a router
Date: Sat, 24 Jan 2009 19:23:26 -

My Server is 192.168.2.2 on my private network.
I can connect from the Viewer with http://192.168.2.2:5800 .

My static IP address is a.b.c.d

What is the address syntax to connect from a Viewer's browser over the
Internet to my Server.
___
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC-List digest, Vol 1 #2593 - 2 msgs

[Philip Herlihy]

Sounds like you're a bit confused about how this works (we've all been
there!).

If you want to connect to a remote machine so you can view and operate it
from a local machine, then you have to install and configure the VNC
_server_ on the remote machine.  I always configure the server to remove the
desktop background, and to accept connections only from my own (static) IP
address.  You also have to set a password.

Then you run the VNC _client_ on the local machine, and enter the IP address
of the remote machine.  Sure, most machines are behind a router these days;
you have to configure the router to forward the default port (5900) to the
machine you want to connect to.  This site might help:
http://portforward.com/

Alternatively, you can run a listening client on your local machine.  Just
start the client using the -listen argument - create a shortcut with this
command string:  C:\Program
Files\RealVNC\VNC4\vnc-P4_3_2-x86_win32_viewer.exe -listen

Then, with the VNC server running on the remote machine, ask someone there
to right-click the server icon in the system tray, and pick add new
client.  Tell them to enter your IP address, and the connection will be
initiated from their end.  You'll have to configure any router to forward
port 5500 to your local machine.

Hope that helps,

Phil, London

-Original Message-
...
Message: 1
From: PRIMETYME char...@primetymepro.com
To: vnc-list@realvnc.com
Subject: How To Initiate A Call =?UTF-8?Q?Request=3F?=
Date: Thu, 22 Jan 2009 07:46:49 -0700


   How does one initiate a connection request when there are many that still
   does not know the purpose let alone the what an IP address is. Secondly,
   most now have a Modem and a Router would the router need to be configure
to
   use a designated port?

   Charles

...
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: VNC-List digest, Vol 1 #2593 - 2 msgs

[Philip Herlihy]

Hi Charles,
 
I hope you don't mind copying in the mailing list - there may be others
interested and very likely more knowledgeable.
 
I'm sure this is a common wish.  I haven't found a way of installing the
server remotely, although I do have a website which details the installation
process.  I also provide a downloadable script which invokes a connection to
a listening client at my location when double-clicked.  That doesn't get you
round the problem of installing the server on a machine where the operator
isn't at all technical.
 
I've experimented with something called PC Helpware which allows the remote
user to download a server program which runs without installation, and is
used to access a listening client at your location.  I got it to work, but
performance didn't seem as good as RealVNC, and I haven't ever used it
live - just as a demo with a technical friend.  It would be great if the
good folk at RealVNC could come up with something like this!
 
It may, however, be possible to use scripting to set up an unattended
installation.  I've never found time to look into this - but I bet there are
folk reading this who have!
 
Best wishes,
 
Phil

  _  

From: PRIMETYME [mailto:char...@primetymepro.com] 
Sent: 23 January 2009 16:12
To: Philip Herlihy
Subject: RE: VNC-List digest, Vol 1 #2593 - 2 msgs


Phil thank you for replying to my question. However, it's not crystal clear
yet so I would like to borrow a little more of your time with direct
dialouge if you don't mind. If you're in London I know our time zones are
not the same so I will post and you can reply when you get free time. (FYI:
I spent 4 years in England back in the early 80's, I miss those days of
fun).
 
I have successfully connected with the current configuration, I actually
have the VNC Server and VNC Viewer installed among 2 of my systems
currently. Sort of an intranet setup if you will as both are behind my
firewall. 
 
What I am essentially tryiing to accomplish is a way that if a friend and/or
client request for assistance that I could either email them an installable
file or they they could maybe go to my website to download and install the
application on their system then click onto an icon that would initiate a
request that I would somehow receive on my local machine that I would then
connect to and administer the remote assistance. I was hoping that an
installation could be completed without me first having to go to the site.
Much like how the LogMeIn software installs.
 
So I am after a workflow that will get the software installed and configured
without me first going to the location. Is this at all possible? I would
like it to be some sort of a wizard installtion for the prospective friend
and/or client who requests my help... 
 
Kind regards,
 
Charles, Las Vegas
 
 
 

 Original Message 
Subject: RE: VNC-List digest, Vol 1 #2593 - 2 msgs
From: Philip Herlihy phi...@herlihy.eu.com
Date: Fri, January 23, 2009 4:29 am
To: vnc-list@realvnc.com, char...@primetymepro.com

Sounds like you're a bit confused about how this works (we've all been
there!).

If you want to connect to a remote machine so you can view and operate it
from a local machine, then you have to install and configure the VNC
_server_ on the remote machine. I always configure the server to remove the
desktop background, and to accept connections only from my own (static) IP
address. You also have to set a password.

Then you run the VNC _client_ on the local machine, and enter the IP address
of the remote machine. Sure, most machines are behind a router these days;
you have to configure the router to forward the default port (5900) to the
machine you want to connect to. This site might help:
http://portforward.com/

Alternatively, you can run a listening client on your local machine. Just
start the client using the -listen argument - create a shortcut with this
command string: C:\Program
Files\RealVNC\VNC4\vnc-P4_3_2-x86_win32_viewer.exe -listen

Then, with the VNC server running on the remote machine, ask someone there
to right-click the server icon in the system tray, and pick add new
client. Tell them to enter your IP address, and the connection will be
initiated from their end. You'll have to configure any router to forward
port 5500 to your local machine.

Hope that helps,

Phil, London

-Original Message-
...
Message: 1
From: PRIMETYME char...@primetymepro.com
To: vnc-list@realvnc.com
Subject: How To Initiate A Call =?UTF-8?Q?Request=3F?=
Date: Thu, 22 Jan 2009 07:46:49 -0700


How does one initiate a connection request when there are many that still
does not know the purpose let alone the what an IP address is. Secondly,
most now have a Modem and a Router would the router need to be configure
to
use a designated port?

Charles

...
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Installing server remotely

[Philip Herlihy]

Oops!  One thing we are supposed to do is change the subject to something
more useful!
 
No more to add otherwise - will be interesting to see if others have
anything to add.
 
Phil

  _  

From: PRIMETYME [mailto:char...@primetymepro.com] 
Sent: 23 January 2009 17:07
To: Philip Herlihy
Cc: vnc-list@realvnc.com
Subject: RE: VNC-List digest, Vol 1 #2593 - 2 msgs


I absolutley do not have any objections copying in the vnc mail list. I'm
new to this type of forum and don't intend to break any formailties. So just
let me know the do's and don't's and I will comply.
 
At one time I worked for a computer service company and when I visited many
clients I had noticed on some, that there was an icon on the clients
computer that they would click to initiate a help request. Of coure I'm not
sure how the icon/application got there in the first place (meaning locally
or remotly?). And secondly, I forget which company it was, it may have been
Compaq/HP/AOL when I had problems I initiated a chat and from the chat
session they were able envoke a remote session, not sure how they did that
either. But I know by now you get my point as to what I wish to do. I
actuall use the LogMeIn application but will soon be broke if I ever have to
pay for it for some of the more needed features...
 
 
Charles
 
 

 Original Message 
Subject: RE: VNC-List digest, Vol 1 #2593 - 2 msgs
From: Philip Herlihy phi...@herlihy.eu.com
Date: Fri, January 23, 2009 8:30 am
To: 'PRIMETYME' char...@primetymepro.com
Cc: vnc-list@realvnc.com


Hi Charles,
 
I hope you don't mind copying in the mailing list - there may be others
interested and very likely more knowledgeable.
 
I'm sure this is a common wish.  I haven't found a way of installing the
server remotely, although I do have a website which details the installation
process.  I also provide a downloadable script which invokes a connection to
a listening client at my location when double-clicked.  That doesn't get you
round the problem of installing the server on a machine where the operator
isn't at all technical.
 
I've experimented with something called PC Helpware which allows the remote
user to download a server program which runs without installation, and is
used to access a listening client at your location.  I got it to work, but
performance didn't seem as good as RealVNC, and I haven't ever used it
live - just as a demo with a technical friend.  It would be great if the
good folk at RealVNC could come up with something like this!
 
It may, however, be possible to use scripting to set up an unattended
installation.  I've never found time to look into this - but I bet there are
folk reading this who have!
 
Best wishes,
 
Phil

  _  

From: PRIMETYME [mailto:char...@primetymepro.com] 
Sent: 23 January 2009 16:12
To: Philip Herlihy
Subject: RE: VNC-List digest, Vol 1 #2593 - 2 msgs



Phil thank you for replying to my question. However, it's not crystal clear
yet so I would like to borrow a little more of your time with direct
dialouge if you don't mind. If you're in London I know our time zones are
not the same so I will post and you can reply when you get free time. (FYI:
I spent 4 years in England back in the early 80's, I miss those days of
fun).
 
I have successfully connected with the current configuration, I actually
have the VNC Server and VNC Viewer installed among 2 of my systems
currently. Sort of an intranet setup if you will as both are behind my
firewall. 
 
What I am essentially tryiing to accomplish is a way that if a friend and/or
client request for assistance that I could either email them an installable
file or they they could maybe go to my website to download and install the
application on their system then click onto an icon that would initiate a
request that I would somehow receive on my local machine that I would then
connect to and administer the remote assistance. I was hoping that an
installation could be completed without me first having to go to the site.
Much like how the LogMeIn software installs.
 
So I am after a workflow that will get the software installed and configured
without me first going to the location. Is this at all possible? I would
like it to be some sort of a wizard installtion for the prospective friend
and/or client who requests my help... 
 
Kind regards,
 
Charles, Las Vegas
 
 
 

 Original Message 
Subject: RE: VNC-List digest, Vol 1 #2593 - 2 msgs
From: Philip Herlihy phi...@herlihy.eu.com
Date: Fri, January 23, 2009 4:29 am
To: vnc-list@realvnc.com, char...@primetymepro.com

Sounds like you're a bit confused about how this works (we've all been
there!).

If you want to connect to a remote machine so you can view and operate it
from a local machine, then you have to install and configure the VNC
_server_ on the remote machine. I always configure the server to remove the
desktop background, and to accept connections only from my own (static) IP
address. You also have to set a password.

Then you run

RE: Network delays, hanging

[Philip Herlihy]

Thanks, Wez:  I can't be sure, but I think I'm seeing a more reliable
connection since making this change.  I find I could set this option in my
listening client, which makes life easier.

Best wishes,

Phil

-Original Message-
From: James Weatherall [mailto:j...@realvnc.com] 
Sent: 13 January 2009 10:26
To: 'Philip Herlihy'; vnc-list@realvnc.com
Subject: RE: Network delays, hanging

Hi Philip,

In that case I'd recommend setting the Rate limit pointer-events option in
the VNC Viewer's Inputs tab - this causes significantly fewer pointer events
to be sent to the server, resulting in fewer small network packets through
the Wi-Fi router, which is what tends to lead to problems.

Regards,

--
Wez @ RealVNC Ltd


 -Original Message-
 From: vnc-list-ad...@realvnc.com [mailto:vnc-list-ad...@realvnc.com] On
 Behalf Of Philip Herlihy
 Sent: 12 January 2009 21:19
 To: vnc-list@realvnc.com
 Subject: RE: Network delays, hanging
 
 Thanks, Ryo and James,
 
 Hadn't realised the operation of the two systems was so different.  Yes
 (in
 answer to James), the server is connected via wireless, but I also
 connect
 to another wireless system which works perfectly.
 
 Phil
 
 -Original Message-
 From: Ryo Koyama [mailto:rkoy...@gmail.com]
 Sent: 12 January 2009 13:44
 To: Philip Herlihy
 Cc: vnc-list@realvnc.com
 Subject: Re: Network delays, hanging
 
 sounds like a simple matter of bandwidth.  RDP takes much less
 bandwidth than VNC (since it's just sending command strings versus
 repainting the screen) so is more efficient. try limiting the color
 resolution and all other things to lesson bandwidth requirements and
 if yes, then that's likely the issue.
 
 On Mon, Jan 12, 2009 at 5:32 AM, Philip Herlihy phi...@herlihy.eu.com
 wrote:
  Thanks for so quick a response.
 
  I don't use RDP and VNC together.  In general I prefer VNC as I can
 set it
  so that we can both see what's going on.  However, with this friend
 (and
  I've known another situation like it) VNC seems unreliable rather
 than
 just
  slow: it connects, but it stalls for minutes at a time with the
 desktop
  half-drawn, and can frequently drop the connection.  Meanwhile, if I
 try
 RDP
  instead, I get a steady and useable connection.  If I persist with
 VNC, I
  can eventually get the job done, via many disconnections, and it's
 often
  easier late at night when the network is quieter. If I try using VNC
 to
  another destination I get a steady and reliable connection, so it
 doesn't
  seem to be a problem at my end.  I could put this down to a busy
 broadband
  connection at the far end, or a modem producing a lot of errors
 perhaps
  (getting out of my depth here) but what is puzzling is that Remote
 Desktop
  does work, albeit fairly slowly.
 
  Phil
  (away from my desk now for several hours)
 
  -Original Message-
  From: Ryo Koyama [mailto:rkoy...@gmail.com]
  Sent: 12 January 2009 13:16
  To: Philip Herlihy
  Cc: vnc-list@realvnc.com
  Subject: Re: Network delays, hanging
 
  are you saying that your RDP drops when you try to connect via VNC,
 or
  that VNC in general does not connect?
 
  - if the former, could be a simple matter of users  where VNC was
  installed.  it will default to the admin account, regardless of what
  user your logged in as.
  - if the latter, many possible scenarios.
- machine in question is running vista (freeVNC doesn't work)
- VNC is set to only accept local connections
 
  Ryo
 
 
 
  On Mon, Jan 12, 2009 at 4:28 AM, Philip Herlihy
 phi...@herlihy.eu.com
  wrote:
  I support several friends using RealVNC (free edition).  In one
 situation,
  I
  can connect successfully using Remote Desktop, but if I try to use
 RealVNC
  the connections stalls, and often drops.  Any thoughts?
 
  (Second post - no replies to the first one!)
 
  PH
  ___
  VNC-List mailing list
  VNC-List@realvnc.com
  To remove yourself from the list visit:
  http://www.realvnc.com/mailman/listinfo/vnc-list
 
 
 
 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Network delays, hanging

[Philip Herlihy]

I support several friends using RealVNC (free edition).  In one situation, I
can connect successfully using Remote Desktop, but if I try to use RealVNC
the connections stalls, and often drops.  Any thoughts?
 
(Second post - no replies to the first one!)
 
PH
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Network delays, hanging

[Philip Herlihy]

Thanks for so quick a response.

I don't use RDP and VNC together.  In general I prefer VNC as I can set it
so that we can both see what's going on.  However, with this friend (and
I've known another situation like it) VNC seems unreliable rather than just
slow: it connects, but it stalls for minutes at a time with the desktop
half-drawn, and can frequently drop the connection.  Meanwhile, if I try RDP
instead, I get a steady and useable connection.  If I persist with VNC, I
can eventually get the job done, via many disconnections, and it's often
easier late at night when the network is quieter. If I try using VNC to
another destination I get a steady and reliable connection, so it doesn't
seem to be a problem at my end.  I could put this down to a busy broadband
connection at the far end, or a modem producing a lot of errors perhaps
(getting out of my depth here) but what is puzzling is that Remote Desktop
does work, albeit fairly slowly.

Phil
(away from my desk now for several hours)

-Original Message-
From: Ryo Koyama [mailto:rkoy...@gmail.com] 
Sent: 12 January 2009 13:16
To: Philip Herlihy
Cc: vnc-list@realvnc.com
Subject: Re: Network delays, hanging

are you saying that your RDP drops when you try to connect via VNC, or
that VNC in general does not connect?

- if the former, could be a simple matter of users  where VNC was
installed.  it will default to the admin account, regardless of what
user your logged in as.
- if the latter, many possible scenarios.
   - machine in question is running vista (freeVNC doesn't work)
   - VNC is set to only accept local connections

Ryo



On Mon, Jan 12, 2009 at 4:28 AM, Philip Herlihy phi...@herlihy.eu.com
wrote:
 I support several friends using RealVNC (free edition).  In one situation,
I
 can connect successfully using Remote Desktop, but if I try to use RealVNC
 the connections stalls, and often drops.  Any thoughts?

 (Second post - no replies to the first one!)

 PH
 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list

___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

RE: Network delays, hanging

[Philip Herlihy]

Thanks, Ryo and James,

Hadn't realised the operation of the two systems was so different.  Yes (in
answer to James), the server is connected via wireless, but I also connect
to another wireless system which works perfectly.

Phil

-Original Message-
From: Ryo Koyama [mailto:rkoy...@gmail.com] 
Sent: 12 January 2009 13:44
To: Philip Herlihy
Cc: vnc-list@realvnc.com
Subject: Re: Network delays, hanging

sounds like a simple matter of bandwidth.  RDP takes much less
bandwidth than VNC (since it's just sending command strings versus
repainting the screen) so is more efficient. try limiting the color
resolution and all other things to lesson bandwidth requirements and
if yes, then that's likely the issue.

On Mon, Jan 12, 2009 at 5:32 AM, Philip Herlihy phi...@herlihy.eu.com
wrote:
 Thanks for so quick a response.

 I don't use RDP and VNC together.  In general I prefer VNC as I can set it
 so that we can both see what's going on.  However, with this friend (and
 I've known another situation like it) VNC seems unreliable rather than
just
 slow: it connects, but it stalls for minutes at a time with the desktop
 half-drawn, and can frequently drop the connection.  Meanwhile, if I try
RDP
 instead, I get a steady and useable connection.  If I persist with VNC, I
 can eventually get the job done, via many disconnections, and it's often
 easier late at night when the network is quieter. If I try using VNC to
 another destination I get a steady and reliable connection, so it doesn't
 seem to be a problem at my end.  I could put this down to a busy broadband
 connection at the far end, or a modem producing a lot of errors perhaps
 (getting out of my depth here) but what is puzzling is that Remote Desktop
 does work, albeit fairly slowly.

 Phil
 (away from my desk now for several hours)

 -Original Message-
 From: Ryo Koyama [mailto:rkoy...@gmail.com]
 Sent: 12 January 2009 13:16
 To: Philip Herlihy
 Cc: vnc-list@realvnc.com
 Subject: Re: Network delays, hanging

 are you saying that your RDP drops when you try to connect via VNC, or
 that VNC in general does not connect?

 - if the former, could be a simple matter of users  where VNC was
 installed.  it will default to the admin account, regardless of what
 user your logged in as.
 - if the latter, many possible scenarios.
   - machine in question is running vista (freeVNC doesn't work)
   - VNC is set to only accept local connections

 Ryo



 On Mon, Jan 12, 2009 at 4:28 AM, Philip Herlihy phi...@herlihy.eu.com
 wrote:
 I support several friends using RealVNC (free edition).  In one
situation,
 I
 can connect successfully using Remote Desktop, but if I try to use
RealVNC
 the connections stalls, and often drops.  Any thoughts?

 (Second post - no replies to the first one!)

 PH
 ___
 VNC-List mailing list
 VNC-List@realvnc.com
 To remove yourself from the list visit:
 http://www.realvnc.com/mailman/listinfo/vnc-list



___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Network problems when using RealVNC but not when using Remote Desktop

[Philip Herlihy]

I've been using RealVNC successfully for some time.  I now want to help a
friend and find I can get a reliable connection using Remote Desktop but not
using RealVNC.  The connection starts up ok, but is either very slow, or
hangs, eventually disconnecting.  Any thoughts?
 
Phil, London
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list