Andrew:
The demo server was down this AM. Please try connecting again.
If you can't connect, your workplace firewall is blocking outgoing
connections to "non standard ports" (very common). If so, I'll setup
a second server on port 443, which your firewall will most likely
allow connections to.
cheers,
Scott
On Tue, 11 Oct 2005, Andrew Grimble wrote:
Hello All,
I'm struggling badly with VNC at the moment. I've tried everything I can
think of and have run out of ideas.
What I am trying to do is pretty standard I think. I have a computer at home
which I want to access from Work using VNC. My work has a firewall which I
have no access to and no info about but it seems to block almost everything.
My PC at home just conencts through a modem to broadband and has a tiny
firewall on it.
I have tried a direct connection using realVNC which obviously didn't work. I
tried to set up an SSH tunnel before I realised I needed to be able to port
forward which I can't do because I have no access to the work firewall.
So then I came across echoVNC/echoServer and thought this was the answer to
all my problems:
First I tried setting up echoVNC to connect to a demo echoServer that was
mentioned on the sourceforge website but echoVNC at work wouldn't connect to
it. I then thought i'd try and set up an echoServer at home. The echoserver
is running fine at home on port 1328. The echoVNC at home connects to this ok
and looks like it is runnning fine and I have tightVNC serever running on top
of all that. Once again, the problem is connecting to this from work. When I
try and connect to the echoServer in echoVNC, it doesn't connect. I put in
the same IP address and port as I do from home but it doesn't seem to see it
from work. Any idea why this would be? Anyway, this is a showstopper as far
as echoVNC is.
TightVNC doesn't connect directly from work (port5900 and port 5800http)
using the normal viewer. However, if I try accessing things using a browser,
I get a bit more success.
If I try the ip address along with port 1328, I get "KaboodleProxy_Protocol
Version 1.0_Server Version 1.0" which I assume is the echoServer talking
back.
If I try the ip address along with port 5800, It try's to connect using Java
and offers me the chance to put in my password but then comes back with
"Network Error: could not connect to server: <ip address>:5900"
So I guess my questions are:
Why can't I get echoVNC at work to connect to my echoServer at home...and is
there a way to do this?
Why do I get the network error?
Can anyone suggest a set up that might actually work?
An answer to any or all of the above would be greatly appreciated,
Best Regards,
Andrew
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
