Bill:
Heya; glad it's working. To get EchoVNC working, you should
login to the echoServer using a *different* name on either side of
the connection (the login name is used to define you uniquely...so
try to be unique). And EchoVNC comes with a RealVNC Viewer, so you
need not install anything else on the Viewer side. On the server
side, you'll need to have a VNC Server, of course. :)
cheers,
Scott
On Sat, 16 Jul 2005, Bill @ PondExpo.com wrote:
Hi Scott and Angelo:
You won't believe this....I liked the "Cavalier" solution so I installed
echovnc on both the server and laptop. Named them both the same. Both
showed I was connected, but I didn't see anything further....Only that I was
connected. Then I tried the real vnc viewer and did not connect. Then I
disabled the echovnc on both PC's, tried the realvnc server and viewer, and
got connected.!!!! I don't know why...but realvnc is working fine. Tried
several different wireless connections and it's fine.
So now I am curious about echovnc. Scott, can you give me some more help as
to how to make it work..Should I be connected and then use the realvnc
viewer? Or is it not necessary to use anything from realvnc? How?
Thanks very much Angelo and Scott..... Bill
----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]>
To: <vnc-list@realvnc.com>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, July 15, 2005 11:03 AM
Subject: Re: Can't connect from ouside my network
Bill:
Heya. Been following your discussion with Angelo, and I
think there's two ways of going about fixing your problem. The
first is what you're doing: root-cause the technical connection
problem you're having. The second approach is a bit move cavalier:
just get a connection to work, and to heck with the details. :)
If the second approach sounds at all interesting, please
try this: install EchoVNC ("http://www.echovnc.com";) on your RealVNC
Server PC, and use it to login to the demo-echoserver site (the
startup Wizard will offer to do this automatically). Then do the
same on your new laptop. Now you'll be able to connect to your
VNC Server using just the "login names" you connected to the demo
echoserver with; you won't need to hassle with IP addresses, port
forwards, dynamic DNS, etc, etc. The echoserver acts as a "relay"
between the two endpoints, so as long as you can connect to the
echoserver, you can ultimately make a VNC connection.
As said above, it skips a lot of the details, so it's
not an interesting solution for everyone. But maybe it's what
you're looking for. I hope it helps!
cheers,
Scott
<snip>
_______________________________________________
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
