connection issue - tightvnc works on same router, but not from remote routers

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

connection issue - tightvnc works on same router, but not from remote routers

BRENT RASMUSSEN
Can anyone help me with this.  I am a new user and have just set up my desktop and laptop,  Tightvnc works when both are in my home using same wireless router, but when I am on road, the laptop will not connect with my desktop
 
Brent
[hidden email]
801-390-0222

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

Re: connection issue - tightvnc works on same router, but not from remote routers

Michael Grant-3
Is your home computer behind a NAT router and/or firewall?  If so, consider using a VPN.  You could create a port forward for port 5800 to your home desktop.

Michael Grant

On Fri, May 27, 2011 at 12:46, BRENT RASMUSSEN <[hidden email]> wrote:
Can anyone help me with this.  I am a new user and have just set up my desktop and laptop,  Tightvnc works when both are in my home using same wireless router, but when I am on road, the laptop will not connect with my desktop
 
Brent
[hidden email]
<a href="tel:801-390-0222" value="+18013900222" target="_blank">801-390-0222

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list



------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

Re: connection issue - tightvnc works on same router, but not from remote routers

Arfin Greebly
In reply to this post by BRENT RASMUSSEN

Brent,

Need more information.

1) Presumably your router uses NAT between the internal and external IP
addresses, and

2) presumably you know your external IP address when you're trying to
access from outside.  Is this correct?

3) Presumably you have done a standard install, and not changed the VNC
ports, so the default ports 5900 and 5800 are being used.

4) Do you have a application rule set up in your router such that inbound
requests on port 5900 and 5800 are directed to your desktop's internal IP
address?


~~ Garry


----- On Fri, 27 May 2011, BRENT RASMUSSEN wrote: -----

>
>
> Can anyone help me with this.
>
> I am a new user and have just set up my desktop and laptop,  Tightvnc
> works when both are in my home using same wireless router, but when I am
> on road, the laptop will not connect with my desktop
>
> Brent
> [hidden email]
> 801-390-0222
>

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

Re: connection issue - tightvnc works on same router, but not from remote routers

Mel Burslan
In reply to this post by Michael Grant-3
>From what the original message said, I don't believe the original poster has any idea about port forwarding regarding his router.

Unfortunately for Brent, unless he is on his home network, he will not have access to his router's management interface, while he is on the road, most probably for the long weekend.

Brent, if you can share the make and model of your wireless router, someone here with the same router, can walk you through the steps of how to change the configuration to accommodate what you are trying to do.

Good luck

Mel

On Fri, May 27, 2011 at 10:34 AM, Michael Grant <[hidden email]> wrote:
Is your home computer behind a NAT router and/or firewall?  If so, consider using a VPN.  You could create a port forward for port 5800 to your home desktop.

Michael Grant

On Fri, May 27, 2011 at 12:46, BRENT RASMUSSEN <[hidden email]> wrote:
Can anyone help me with this.  I am a new user and have just set up my desktop and laptop,  Tightvnc works when both are in my home using same wireless router, but when I am on road, the laptop will not connect with my desktop
 
Brent
[hidden email]
<a href="tel:801-390-0222" value="+18013900222" target="_blank">801-390-0222

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list



------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list




--
I am no longer on facebook, but you still can follow my posts @ http://thenomad.posterous.com
Success is a lousy teacher. It seduces smart people into thinking they can't lose...


------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

RE: connection issue - tightvnc works on same router, but not fromremote routers

Bob McConnell
In reply to this post by Arfin Greebly
From: Arfin Greebly

> Need more information.
>
> 1) Presumably your router uses NAT between the internal
> and external IP addresses, and
>
> 2) presumably you know your external IP address when
> you're trying to access from outside.  Is this correct?
>
> 3) Presumably you have done a standard install, and not
> changed the VNC ports, so the default ports 5900 and
> 5800 are being used.
>
> 4) Do you have a application rule set up in your router
> such that inbound requests on port 5900 and 5800 are
> directed to your desktop's internal IP address?

Setting it up this way creates two new problems.

1. Everyone that probes your internet address will be able to see you
have those ports open, and will know what application they lead to. They
can then bombard them with connection attempts until they find the
correct password. BINGO, they have full access to your home computer.

2. Everything between the two computers is passed in plain text,
including the password. Anyone that can sniff that traffic will be able
to grab the password and get access to your home computer. This is an
even bigger problem if you use wireless connections for your laptop,
whether they are in an office or the local cafe.

You are far better off setting up a VPN, which would encrypt all traffic
between the machines, including the passwords. If your current
router/firewall can not handle that, take a look at m0n0wall or
shorewall.

Bob McConnell

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

Re: connection issue - tightvnc works on same router, but not fromremote routers

Michael Grant-3

You are far better off setting up a VPN, which would encrypt all traffic
between the machines, including the passwords. If your current
router/firewall can not handle that, take a look at m0n0wall or
shorewall.


For many people, this is just too difficult.  

Is there some way to start tls/ssl inside a vnc connection?

With respect to the nat/firewall issue, I have brought this up before.  It'd be really great if there was server end one could install on a server that would sit there and listen for incoming connections from vnc desktops and from vnc clients and put them together.  With this, you could have what teamviewer or logmein does for you, but running on your own equipment.  People could, I suppose, put up a public server to help people like Brent who just want to plug and play.

Michael Grant


------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

RE: connection issue - tightvnc works on same router, but not fromremote routers

BRENT RASMUSSEN
In reply to this post by Bob McConnell
Bob,
Do these same problems exist with Teamviewer or Logmein?
Brent
 
> Subject: RE: connection issue - tightvnc works on same router, but not fromremote routers

> Date: Fri, 27 May 2011 14:16:24 -0400
> From: [hidden email]
> To: [hidden email]; [hidden email]
>
> From: Arfin Greebly
>
> > Need more information.
> >
> > 1) Presumably your router uses NAT between the internal
> > and external IP addresses, and
> >
> > 2) presumably you know your external IP address when
> > you're trying to access from outside. Is this correct?
> >
> > 3) Presumably you have done a standard install, and not
> > changed the VNC ports, so the default ports 5900 and
> > 5800 are being used.
> >
> > 4) Do you have a application rule set up in your router
> > such that inbound requests on port 5900 and 5800 are
> > directed to your desktop's internal IP address?
>
> Setting it up this way creates two new problems.
>
> 1. Everyone that probes your internet address will be able to see you
> have those ports open, and will know what application they lead to. They
> can then bombard them with connection attempts until they find the
> correct password. BINGO, they have full access to your home computer.
>
> 2. Everything between the two computers is passed in plain text,
> including the password. Anyone that can sniff that traffic will be able
> to grab the password and get access to your home computer. This is an
> even bigger problem if you use wireless connections for your laptop,
> whether they are in an office or the local cafe.
>
> You are far better off setting up a VPN, which would encrypt all traffic
> between the machines, including the passwords. If your current
> router/firewall can not handle that, take a look at m0n0wall or
> shorewall.
>
> Bob McConnell
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> ___________________________________________________________
> TightVNC mailing list, [hidden email]
> To change your subscription or to UNSUBSCRIBE, please visit
> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

RE: connection issue - tightvnc works on same router, but notfromremote routers

Bob McConnell
In reply to this post by Michael Grant-3
From: Michael Grant

>> You are far better off setting up a VPN, which would encrypt all
traffic
>> between the machines, including the passwords. If your current
>> router/firewall can not handle that, take a look at m0n0wall or
>> shorewall.
>
> For many people, this is just too difficult.  
>
> Is there some way to start tls/ssl inside a vnc connection?

None of the VNC packages I have looked at support encryption at all. You
need to set up the secure pipe (VPN) first, then make the VNC connection
through it. That is the more natural setup anyway. There may be other
connections where you need the protection of the pipe.

Bob McConnell

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

RE: connection issue - tightvnc works on same router, but not fromremote routers

Bob McConnell
In reply to this post by BRENT RASMUSSEN
I don't know, I've not heard of either of those. However, I would
suspect it does. The normal setup is to use a single, secure pipe that
will then accept multiple connections and protocols. It's a lot easier
than setting up separate locks and keys for each one. Either a VPN or
SSH can be used for the pipe.

Bob McConnell

From: BRENT RASMUSSEN

Bob,
Do these same problems exist with Teamviewer or Logmein?
Brent
 
> Subject: RE: connection issue - tightvnc works on same router, but not
fromremote routers

> Date: Fri, 27 May 2011 14:16:24 -0400
> From: [hidden email]
> To: [hidden email]; [hidden email]
>
> From: Arfin Greebly
>
> > Need more information.
> >
> > 1) Presumably your router uses NAT between the internal
> > and external IP addresses, and
> >
> > 2) presumably you know your external IP address when
> > you're trying to access from outside. Is this correct?
> >
> > 3) Presumably you have done a standard install, and not
> > changed the VNC ports, so the default ports 5900 and
> > 5800 are being used.
> >
> > 4) Do you have a application rule set up in your router
> > such that inbound requests on port 5900 and 5800 are
> > directed to your desktop's internal IP address?
>
> Setting it up this way creates two new problems.
>
> 1. Everyone that probes your internet address will be able to see you
> have those ports open, and will know what application they lead to.
They
> can then bombard them with connection attempts until they find the
> correct password. BINGO, they have full access to your home computer.
>
> 2. Everything between the two computers is passed in plain text,
> including the password. Anyone that can sniff that traffic will be
able
> to grab the password and get access to your home computer. This is an
> even bigger problem if you use wireless connections for your laptop,
> whether they are in an office or the local cafe.
>
> You are far better off setting up a VPN, which would encrypt all
traffic
> between the machines, including the passwords. If your current
> router/firewall can not handle that, take a look at m0n0wall or
> shorewall.
>
> Bob McConnell

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

Re: connection issue - tightvnc works on same router, but not fromremote routers

Arfin Greebly

Brent,

Products like LogMeIn, GoToMyPC, and LapLink Everywhere use a central "arbitration" server to work their magic.  No experience with TeamViewer.

  • The host side contacts the master server (outbound on port 80) and lets the server know that it's awake and waiting.  This allows the host/server to operate in any kind of networking environment, requiring no special router settings or configuration.  It just works.
  • The client (remote) side uses a browser to log into the master server, and the master server facilitates the connection.  For best performance use Firefox or IE for the browser environment.  Opera works well, but doesn't support the client-specific plug-ins that improve performance.  I can't speak for Chrome, as I haven't tried it.  If you are connecting from a Linux-based browser for LogMeIn, expect some initial confusion, as the control application may be the Flash version, and you lose the right mouse button (Flash grabs it), but your middle button will provide that function.
  • Once the connection is established, the central server steps out of the way, but keeps track of the session status.

Having said all of that, please note that LogMeIn will generally not perform as well as TightVNC.  Your interface with VNC is crisper, cleaner, you could say "tighter" than the LogMeIn client.  GoToMyPC provides a client that performs very well, and provides features like sound and printer pass-through, as well as file copying.  And, naturally, there is no free version of GoToMyPC or LapLink.  Finally, both of these "port 80" clients have heavier system-side hooks than VNC, and you can (as I do) find yourself having to phone someone to reset the host computer when things mysteriously just "hang" or the client screen goes black and won't acquire a valid screen image.

If you can get the arrangements in place for VNC to work, I believe you will be happier with that.

Myself?  I use all three.  If my router suddenly decides not to forward my VNC port, I can log in using one of the others and fix the problem.  If one of my six boxes suddenly quits listening on port 5900/5800 (or 5700/5600, or whatever for that box), I can get in and restart things using one of the others.

But frankly, I'm always happiest if I can get a VNC connection.

~~ Garry


----- On 05/27/2011 12:07 PM, Bob McConnell wrote: -----
I don't know, I've not heard of either of those. However, I would
suspect it does. The normal setup is to use a single, secure pipe that
will then accept multiple connections and protocols. It's a lot easier
than setting up separate locks and keys for each one. Either a VPN or
SSH can be used for the pipe.

Bob McConnell

From: BRENT RASMUSSEN

Bob,
Do these same problems exist with Teamviewer or Logmein?
Brent
 
  
Subject: RE: connection issue - tightvnc works on same router, but not
    
fromremote routers
  
Date: Fri, 27 May 2011 14:16:24 -0400
From: [hidden email]
To: [hidden email]; [hidden email]

From: Arfin Greebly

    
Need more information.

1) Presumably your router uses NAT between the internal
and external IP addresses, and

2) presumably you know your external IP address when
you're trying to access from outside. Is this correct?

3) Presumably you have done a standard install, and not
changed the VNC ports, so the default ports 5900 and
5800 are being used.

4) Do you have a application rule set up in your router
such that inbound requests on port 5900 and 5800 are
directed to your desktop's internal IP address?
      
Setting it up this way creates two new problems.

1. Everyone that probes your internet address will be able to see you
have those ports open, and will know what application they lead to.
    
They
  
can then bombard them with connection attempts until they find the
correct password. BINGO, they have full access to your home computer.

2. Everything between the two computers is passed in plain text,
including the password. Anyone that can sniff that traffic will be
    
able
  
to grab the password and get access to your home computer. This is an
even bigger problem if you use wireless connections for your laptop,
whether they are in an office or the local cafe.

You are far better off setting up a VPN, which would encrypt all
    
traffic
  
between the machines, including the passwords. If your current
router/firewall can not handle that, take a look at m0n0wall or
shorewall.

Bob McConnell
    

------------------------------------------------------------------------------

  

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

Re: connection issue - tightvnc works on same router, but not fromremote routers

Michael Grant-3
In reply to this post by BRENT RASMUSSEN
No they don't have these problems, TeamViewer, LogMeIn, GotoMyPC and other such services are run as services on external sites.  You set up their software on your machine which keeps a connection open to their server, then when you want to get into your PC, you use their software (their sort of vnc client) to connect, and their server relays to your waiting machine.  It avoids all the firewall and nat problems.  But you are dependent on their good will to let you use their service for free which may not be free forever.  You are also trusting they don't snoop what you are doing.

With VNC, it's all in your hands.  Currently the design of any of the VNC softwares, (there's a bunch like UltraVNC, Tight, XVNC..etc), none of them that I know of have any sort of server component that you could install on a central server somewhere like TeamViewer, LogMeIn, or GotoMyPC (or a bunch of other similar services out there).

Where VNC excels is that it's light weight, it's totally personal as in you set it up for yourself, you don't have any dependency on any external company, it's always free, and the quality is excellent.  The image TeamViewer presents I think is also excellent and fast having used both LogMeIn and GoToMyPC.  I don't think there's that much difference in image quality and speed these days between VNC and these other product/services.

So if you want to go to the trouble of learning the technical ins and outs of how to get VNC working in your environment, it may be just what you need.  If you're less technical, perhaps looking at one of these off the shelf services would be more accessible for you.

Michael Grant

On Fri, May 27, 2011 at 14:55, BRENT RASMUSSEN <[hidden email]> wrote:
Bob,
Do these same problems exist with Teamviewer or Logmein?
Brent
 
> Subject: RE: connection issue - tightvnc works on same router, but not fromremote routers

> Date: Fri, 27 May 2011 14:16:24 -0400
> From: [hidden email]
> To: [hidden email]; [hidden email]

>
> From: Arfin Greebly
>
> > Need more information.
> >
> > 1) Presumably your router uses NAT between the internal
> > and external IP addresses, and
> >
> > 2) presumably you know your external IP address when
> > you're trying to access from outside. Is this correct?
> >
> > 3) Presumably you have done a standard install, and not
> > changed the VNC ports, so the default ports 5900 and
> > 5800 are being used.
> >
> > 4) Do you have a application rule set up in your router
> > such that inbound requests on port 5900 and 5800 are
> > directed to your desktop's internal IP address?
>
> Setting it up this way creates two new problems.
>
> 1. Everyone that probes your internet address will be able to see you
> have those ports open, and will know what application they lead to. They
> can then bombard them with connection attempts until they find the
> correct password. BINGO, they have full access to your home computer.
>
> 2. Everything between the two computers is passed in plain text,
> including the password. Anyone that can sniff that traffic will be able
> to grab the password and get access to your home computer. This is an
> even bigger problem if you use wireless connections for your laptop,
> whether they are in an office or the local cafe.
>
> You are far better off setting up a VPN, which would encrypt all traffic
> between the machines, including the passwords. If your current
> router/firewall can not handle that, take a look at m0n0wall or
> shorewall.
>
> Bob McConnell
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> ___________________________________________________________
> TightVNC mailing list, [hidden email]
> To change your subscription or to UNSUBSCRIBE, please visit
> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list



------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

RE: connection issue - tightvnc works on same router, but not fromremote routers

BRENT RASMUSSEN
In reply to this post by Arfin Greebly
THank you all for so much help today.. I am not technical enough to do all the VNC stuff and the Logmein and teamviewer are working well.
 

Date: Fri, 27 May 2011 13:47:13 -0700
From: [hidden email]
To: [hidden email]
Subject: Re: connection issue - tightvnc works on same router, but not fromremote routers


Brent,

Products like LogMeIn, GoToMyPC, and LapLink Everywhere use a central "arbitration" server to work their magic.  No experience with TeamViewer.

  • The host side contacts the master server (outbound on port 80) and lets the server know that it's awake and waiting.  This allows the host/server to operate in any kind of networking environment, requiring no special router settings or configuration.  It just works.
  • The client (remote) side uses a browser to log into the master server, and the master server facilitates the connection.  For best performance use Firefox or IE for the browser environment.  Opera works well, but doesn't support the client-specific plug-ins that improve performance.  I can't speak for Chrome, as I haven't tried it.  If you are connecting from a Linux-based browser for LogMeIn, expect some initial confusion, as the control application may be the Flash version, and you lose the right mouse button (Flash grabs it), but your middle button will provide that function.
  • Once the connection is established, the central server steps out of the way, but keeps track of the session status.

Having said all of that, please note that LogMeIn will generally not perform as well as TightVNC.  Your interface with VNC is crisper, cleaner, you could say "tighter" than the LogMeIn client.  GoToMyPC provides a client that performs very well, and provides features like sound and printer pass-through, as well as file copying.  And, naturally, there is no free version of GoToMyPC or LapLink.  Finally, both of these "port 80" clients have heavier system-side hooks than VNC, and you can (as I do) find yourself having to phone someone to reset the host computer when things mysteriously just "hang" or the client screen goes black and won't acquire a valid screen image.

If you can get the arrangements in place for VNC to work, I believe you will be happier with that.

Myself?  I use all three.  If my router suddenly decides not to forward my VNC port, I can log in using one of the others and fix the problem.  If one of my six boxes suddenly quits listening on port 5900/5800 (or 5700/5600, or whatever for that box), I can get in and restart things using one of the others.

But frankly, I'm always happiest if I can get a VNC connection.

~~ Garry


----- On 05/27/2011 12:07 PM, Bob McConnell wrote: -----
I don't know, I've not heard of either of those. However, I would
suspect it does. The normal setup is to use a single, secure pipe that
will then accept multiple connections and protocols. It's a lot easier
than setting up separate locks and keys for each one. Either a VPN or
SSH can be used for the pipe.

Bob McConnell

From: BRENT RASMUSSEN

Bob,
Do these same problems exist with Teamviewer or Logmein?
Brent
 
  
Subject: RE: connection issue - tightvnc works on same router, but not
    
fromremote routers
  
Date: Fri, 27 May 2011 14:16:24 -0400
From: [hidden email]
To: [hidden email]; [hidden email]

From: Arfin Greebly

    
Need more information.

1) Presumably your router uses NAT between the internal
and external IP addresses, and

2) presumably you know your external IP address when
you're trying to access from outside. Is this correct?

3) Presumably you have done a standard install, and not
changed the VNC ports, so the default ports 5900 and
5800 are being used.

4) Do you have a application rule set up in your router
such that inbound requests on port 5900 and 5800 are
directed to your desktop's internal IP address?
      
Setting it up this way creates two new problems.

1. Everyone that probes your internet address will be able to see you
have those ports open, and will know what application they lead to.
    
They
  
can then bombard them with connection attempts until they find the
correct password. BINGO, they have full access to your home computer.

2. Everything between the two computers is passed in plain text,
including the password. Anyone that can sniff that traffic will be
    
able
  
to grab the password and get access to your home computer. This is an
even bigger problem if you use wireless connections for your laptop,
whether they are in an office or the local cafe.

You are far better off setting up a VPN, which would encrypt all
    
traffic
  
between the machines, including the passwords. If your current
router/firewall can not handle that, take a look at m0n0wall or
shorewall.

Bob McConnell
    
------------------------------------------------------------------------------

  

------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________ TightVNC mailing list, [hidden email] To change your subscription or to UNSUBSCRIBE, please visit https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

RE: connection issue - tightvnc works on same router, but not fromremote routers

BRENT RASMUSSEN
In reply to this post by Michael Grant-3
THank you all for so much help today.. I am not technical enough to do all the VNC stuff and the Logmein and teamviewer are working well.

 

Date: Fri, 27 May 2011 17:18:14 -0400
Subject: Re: connection issue - tightvnc works on same router, but not fromremote routers
From: [hidden email]
To: [hidden email]
CC: [hidden email]; [hidden email]; [hidden email]

No they don't have these problems, TeamViewer, LogMeIn, GotoMyPC and other such services are run as services on external sites.  You set up their software on your machine which keeps a connection open to their server, then when you want to get into your PC, you use their software (their sort of vnc client) to connect, and their server relays to your waiting machine.  It avoids all the firewall and nat problems.  But you are dependent on their good will to let you use their service for free which may not be free forever.  You are also trusting they don't snoop what you are doing.

With VNC, it's all in your hands.  Currently the design of any of the VNC softwares, (there's a bunch like UltraVNC, Tight, XVNC..etc), none of them that I know of have any sort of server component that you could install on a central server somewhere like TeamViewer, LogMeIn, or GotoMyPC (or a bunch of other similar services out there).

Where VNC excels is that it's light weight, it's totally personal as in you set it up for yourself, you don't have any dependency on any external company, it's always free, and the quality is excellent.  The image TeamViewer presents I think is also excellent and fast having used both LogMeIn and GoToMyPC.  I don't think there's that much difference in image quality and speed these days between VNC and these other product/services.

So if you want to go to the trouble of learning the technical ins and outs of how to get VNC working in your environment, it may be just what you need.  If you're less technical, perhaps looking at one of these off the shelf services would be more accessible for you.

Michael Grant

On Fri, May 27, 2011 at 14:55, BRENT RASMUSSEN <[hidden email]> wrote:
Bob,
Do these same problems exist with Teamviewer or Logmein?
Brent
 

> Subject: RE: connection issue - tightvnc works on same router, but not fromremote routers
> Date: Fri, 27 May 2011 14:16:24 -0400
> From: [hidden email]
> To: [hidden email]; [hidden email]

>
> From: Arfin Greebly
>
> > Need more information.
> >
> > 1) Presumably your router uses NAT between the internal
> > and external IP addresses, and
> >
> > 2) presumably you know your external IP address when
> > you're trying to access from outside. Is this correct?
> >
> > 3) Presumably you have done a standard install, and not
> > changed the VNC ports, so the default ports 5900 and
> > 5800 are being used.
> >
> > 4) Do you have a application rule set up in your router
> > such that inbound requests on port 5900 and 5800 are
> > directed to your desktop's internal IP address?
>
> Setting it up this way creates two new problems.
>
> 1. Everyone that probes your internet address will be able to see you
> have those ports open, and will know what application they lead to. They
> can then bombard them with connection attempts until they find the
> correct password. BINGO, they have full access to your home computer.
>
> 2. Everything between the two computers is passed in plain text,
> including the password. Anyone that can sniff that traffic will be able
> to grab the password and get access to your home computer. This is an
> even bigger problem if you use wireless connections for your laptop,
> whether they are in an office or the local cafe.
>
> You are far better off setting up a VPN, which would encrypt all traffic
> between the machines, including the passwords. If your current
> router/firewall can not handle that, take a look at m0n0wall or
> shorewall.
>
> Bob McConnell
>
> ------------------------------------------------------------------------------
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery,
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now.
> http://p.sf.net/sfu/quest-d2dcopy1
> ___________________________________________________________
> TightVNC mailing list, [hidden email]
> To change your subscription or to UNSUBSCRIBE, please visit
> https://lists.sourceforge.net/lists/listinfo/vnc-tight-list

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list



------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

RE: connection issue - tightvnc works on same router, but not fromremote routers

BRENT RASMUSSEN
In reply to this post by Bob McConnell
THank you all for so much help today.. I am not technical enough to do all the VNC stuff and the Logmein and teamviewer are working well.

 
> Subject: RE: connection issue - tightvnc works on same router, but not fromremote routers

> Date: Fri, 27 May 2011 15:07:40 -0400
> From: [hidden email]
> To: [hidden email]; [hidden email]
>
> I don't know, I've not heard of either of those. However, I would
> suspect it does. The normal setup is to use a single, secure pipe that
> will then accept multiple connections and protocols. It's a lot easier
> than setting up separate locks and keys for each one. Either a VPN or
> SSH can be used for the pipe.
>
> Bob McConnell
>
> From: BRENT RASMUSSEN
>
> Bob,
> Do these same problems exist with Teamviewer or Logmein?
> Brent
>
> > Subject: RE: connection issue - tightvnc works on same router, but not
> fromremote routers
> > Date: Fri, 27 May 2011 14:16:24 -0400
> > From: [hidden email]
> > To: [hidden email]; [hidden email]
> >
> > From: Arfin Greebly
> >
> > > Need more information.
> > >
> > > 1) Presumably your router uses NAT between the internal
> > > and external IP addresses, and
> > >
> > > 2) presumably you know your external IP address when
> > > you're trying to access from outside. Is this correct?
> > >
> > > 3) Presumably you have done a standard install, and not
> > > changed the VNC ports, so the default ports 5900 and
> > > 5800 are being used.
> > >
> > > 4) Do you have a application rule set up in your router
> > > such that inbound requests on port 5900 and 5800 are
> > > directed to your desktop's internal IP address?
> >
> > Setting it up this way creates two new problems.
> >
> > 1. Everyone that probes your internet address will be able to see you
> > have those ports open, and will know what application they lead to.
> They
> > can then bombard them with connection attempts until they find the
> > correct password. BINGO, they have full access to your home computer.
> >
> > 2. Everything between the two computers is passed in plain text,
> > including the password. Anyone that can sniff that traffic will be
> able
> > to grab the password and get access to your home computer. This is an
> > even bigger problem if you use wireless connections for your laptop,
> > whether they are in an office or the local cafe.
> >
> > You are far better off setting up a VPN, which would encrypt all
> traffic
> > between the machines, including the passwords. If your current
> > router/firewall can not handle that, take a look at m0n0wall or
> > shorewall.
> >
> > Bob McConnell

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list
Reply | Threaded
Open this post in threaded view
|

RE: connection issue - tightvnc works on same router, but not from remote routers

BRENT RASMUSSEN
In reply to this post by Mel Burslan
Mel,
THank you all for so much help today.. I am not technical enough to do all the VNC stuff and the Logmein and teamviewer are working well.

 

Date: Fri, 27 May 2011 11:01:46 -0700
Subject: Re: connection issue - tightvnc works on same router, but not from remote routers
From: [hidden email]
To: [hidden email]
CC: [hidden email]

From what the original message said, I don't believe the original poster has any idea about port forwarding regarding his router.

Unfortunately for Brent, unless he is on his home network, he will not have access to his router's management interface, while he is on the road, most probably for the long weekend.

Brent, if you can share the make and model of your wireless router, someone here with the same router, can walk you through the steps of how to change the configuration to accommodate what you are trying to do.

Good luck

Mel

On Fri, May 27, 2011 at 10:34 AM, Michael Grant <[hidden email]> wrote:
Is your home computer behind a NAT router and/or firewall?  If so, consider using a VPN.  You could create a port forward for port 5800 to your home desktop.

Michael Grant

On Fri, May 27, 2011 at 12:46, BRENT RASMUSSEN <[hidden email]> wrote:
Can anyone help me with this.  I am a new user and have just set up my desktop and laptop,  Tightvnc works when both are in my home using same wireless router, but when I am on road, the laptop will not connect with my desktop
 
Brent
[hidden email]
801-390-0222

------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list



------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list




--
I am no longer on facebook, but you still can follow my posts @ http://thenomad.posterous.com
Success is a lousy teacher. It seduces smart people into thinking they can't lose...


------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___________________________________________________________
TightVNC mailing list, [hidden email]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list