for a Linux (remote, behind the firewall) to Windows
(server). Also, can the tunnel on the server end be set to passively listen
for incoming connections?
Paul
On Friday 14 December 2007 4:57:07 pm Scott C. Best wrote:
Thomas:
Hello! You're unable to connect from work to home because
(most
Thomas:
Hello! Sorry for the confusion: demo2007 is just the
password to use to authenticate the EchoVNC connection to the
demo echoServer. It's *not* the password you set in your VNC
Server, to authenticate VNC Viewer connections. Two different
passwords. :)
cheers,
Scott
Hi steve,
Thomas:
Hello! You're unable to connect from work to home because
(most likely) your workplace firewall is blocking outgoing connections
to the TCP port that your VNC Server at home is listening to. That is,
by default, a VNC Server listens to TCP 5900. If you changed that to
TCP 443,
John:
Heya. Please try this:
1. Download EchoVNC 2.31 and install it on the PC you want to
take remote control of (eg, your work PC). The startup Wizard
will automatically detect your RealVNC server and configure
itself to work with it correctly.
2. During the Startup Wizard
the lot.
Thanks again
John
On Dec 11, 2007 6:17 PM, Scott C. Best [EMAIL PROTECTED] wrote:
John:
Heya. Please try this:
1. Download EchoVNC 2.31 and install it on the PC you want to
take remote control of (eg, your work PC). The startup Wizard
will automatically detect your RealVNC
Hello! Apologies as necessary for the cross-posting.
The EchoVNC team is pleased to announce a major release of our
software: version 2.30 is now available!
GPL'd source and a binary installer are available here:
http://downloads.sourceforge.net/echovnc/EchoVNC-2.30-Setup.exe
Brian:
Heya. As far as I know, the commercial verions of RealVNC
allow you to specify the *same* TCP port for both VNC data and
HTTP data connections. And I think ... it was done to address
exactly your situation. :)
cheers,
Scott
Greetings,
This is probably a noob question, but I
Brendan:
Heya. Getting VNC to work across a proxy is a bit tricky:
usually, it is required that you first establish a proxy-aware tunnel
of some sort. That is, you would first run some software on the VNC
Viewer PC that established a connection with a server on the other
side of your
Brendan:
Heya. Regarding SSH and proxytunnel, do you have access to
a Linux/*nix server anywhere? Makes life easier for this part.
Regarding EchoVNC, two things to note: first, most web proxy's
will not allow connections to non-standard ports, like what VNC
and echoServer use by
Brendan:
I think I understand your setup to be:
Windows-PC -proxy- Internet - Ubuntu-PC
When I said Viewer, I presumed you wanted to start a
VNC Viewer on the Windows-PC, and connect to a VNC Server that
could connect directly with the Ubuntu-PC (either via the
Internet, or via
Skip:
Yikes, 20 hours. :) Have a look here:
http://faq.gotomyvnc.com/fom-serve/cache/64.html
The important thing to keep in mind is that after you've
setup your routers port-forwarding, you will not be able to connect
to them -- using the external IP address -- from the inside.
Eric:
Heya. It sounds like everything is working fine. You just
won't be able to connect to your WAN address while you're *inside*
the LAN. Most routers don't support such a hairpin turn. An
analogy would be trying to dial your home phone number from one
of your home phones, and having
Giacomo:
Hello! Yes, EchoVNC does it that way: http://www.echovnc.com
The clients use something called echoWare; it's available for Windows,
OSX, and Linux. The relay server is available for Windows and Linux.
cheers,
Scott
Hello everyone,
when connecting to an host behind NATs
Abi:
Heya. Similar to the Yoics solution is EchoVNC:
http://www.echovnc.com
The idea is that both sides of the VNC connection (server
and viewer) make an independant login connection to publically
available server. This new server then acts as a relay point
between the two
Abi:
Heya. Good page here about VNC and Firewalls:
http://faq.gotomyvnc.com/fom-serve/cache/63.html
-Scott
Dear colleagues,
I just use the RealVNC to control the network on my branches. Lets say branch
A, B and C. Each computers already installed with the RealVNC servers. I'm in
Bruce:
Heya. Here's a possible solution:
1. Behind your firewall/router, setup an echoServer. It acts as
the relay between the VNC Viewer and Servers, similar to
how GoToMyPC's servers act as relays.
2. Customize a copy of InstantVNC so that when run, it logs into
your
Lee:
Heya. While not a RealVNC solution, the EchoVNC approach makes
this a bit easier. With EchoVNC, each of your support clients logs into
an echoServer, which acts as a relay when you fire up a Viewer to connect
to them. In the Viewer, you can get a simple list of who's available
to
JS:
Hello! Third-party solution:
1. Run an echoServer on your LAN, port-forward to it from your one
exposed port.
2. For every PC on your internal network, create one connection group
on the echoServer. Each connection group has its own group password.
3. Setup either InstantVNC
Wladyslaw:
Hello! I hope these pages help answer your questions:
http://faq.gotomyvnc.com/fom-serve/cache/63.html
cheers,
Scott
Would someone help me with this problem by providing an idea of how to
address my desktop PC from The Internet.
I can always connect and remotely control
Johan:
Hello! Just checking: if you open a command-line on your
Windows PC (Start - Run - cmd), and then netstat -an, can you
verify that something is listening to 27036? I'm not sure how
you told the VNC Server to listen to this port, but the netstat
command will tell you if it did.
PROTECTED]
[mailto:[EMAIL PROTECTED] Scott C. Best
Verzonden: maandag 9 juli 2007 20:39
Aan: vnc-list@realvnc.com
CC: [EMAIL PROTECTED]
Onderwerp: Re: VNC and NAT - using random ports?
Johan:
Hello! Just checking: if you open a command-line on your
Windows PC (Start - Run - cmd
Johan:
Yes, I'm sure updating to the latest version of the Personal
Edition will help. I do not know the low-level cause of the 10054 error
in the earlier Personal Edition versions, but apparently it's been
fixed in the 4.2.1 release. I also don't know if it exists in the
4.1.2 Free
Hello! The official release of EchoVNC 2.10 is now available:
http://www.echogent.com/download_echovnc.htm
This version includes all of the Viewer repairs of 2.02, and
includes new server repairs and enhancements:
* Modified EchoVNC so that it will run alongside other VNC
John:
Heya. The easiest way to connect with your parent's computer
across an unconfigured firewall/router is with EchoVNC. Our latest
release is *nearly* ready, but everything you'll require is here:
ftp://ftp.echogent.com/EchoVNC/bin
This latest version runs alongside other
Gerardo:
Hello! Personally, I've always thought VNC logging was awful,
so I tried to do something about it:
ftp://ftp.echogent.com/EchoVNC/bin
In this version, the server uses the vnc2swf toolkit to log
VNC sessions to a Shockwave movie file, storing it in the VNC installation
Or EchoVNC. Lots of ways to work with VNC now, without setting
up port-forwarding. Though it's analogous to the difference between
driving a stick-shift or automatic transmission -- some people want the
convenience, some want the feel of it. :)
cheers,
Scott
Why not use Hamachi?
John:
Heya. Some suggested answers to your questions. First off,
though, my EchoVNC and Echogent's are the same EchoVNC. :)
1. Are there other products in addition to the above products I
need to look at? Any clear leaders? Does the Packet Server really
work? Any serious negatives?
project maintains VNC compatibility too, so perhaps that's what
you're thinking of?
Cheers,
Wez @ RealVNC Ltd.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott C. Best
Sent: 03 January 2007 00:07
To: vnc-list@realvnc.com
Subject: speaking
with it. If you've
based your project on that codebase then, unless you've taken out the
incompatible bits, your project won't be VNC compatible either.
Cheers,
Wez @ RealVNC Ltd.
-Original Message-
From: Scott C. Best [mailto:[EMAIL PROTECTED]
Sent: 03 January 2007 17:23
To: James Weatherall
Cc: vnc
Right up front: thanks to the RealVNC guys for tolerating
this release announcement on their email list.
Just last week, we released version 2.00 of EchoVNC: the
only VNC flavor with integrated echoWare, allowing VNC Viewers to
connect to VNC Servers without either side having to
Heyaz. A good alternative to Hamachi is the echoServer approach.
It works in a similar way, making the VNC connection appear to be
outgoing from the point of view of both firewalls. Unlike Hamachi,
though: (1) you can own and operate your own reflection server (rather
than relying on run
John:
Hello! While Kaboodle was the first echoWare application we
had to tunnel VNC without port-forwarding, the most advanced version
is now embedded within UltraVNC:
http://forum.ultravnc.info/viewtopic.php?t=7162
Hopefully, it's a much more straightforward way of
Kevin:
Heya. I felt compelled to reply, as your VNC password
information is very misleading.
Telnet and FTP actually *do* send passwords in the clear.
That is, if you actually captured packets in transit, you'd see
the password right there. However, VNC absolutely does not do
Adam:
Heya. I administer the Kaboodle program that John mentioned.
It uses something called echoWare to make firewall-friendly VNC
connections, without any port-forwarding setup. The most advanced
combination of echoWare and VNC right now is in UltraVNC -- we
integrated echoWare directly
it on the colleges computer without installing anything. Thank you!!!
Thank you s much!!! :-)
- Original Message - From: Scott C. Best [EMAIL PROTECTED]
To: vnc-list@realvnc.com
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Saturday, August 19, 2006 11:35 AM
Subject: Re: Can't
Ed:
Heya. Yup, it's something of a FAQ, but a good one. :) In
order to make a VNC connection either to or from a web-proxied LAN,
you need to first establish a tunnel of some sort through the
proxy. There are several utilities which allow this: SSH, Zebedee,
ProxyTunnel, EchoVNC.
Stephen:
Heya. One of the original replies to this thread suggested
you try EchoVNC, and maybe that's a better solution for you. Using
EchoVNC, you can establish a persistent TCP connection to an
echoServer of your choice (ideally, one you control). We run one
a demo one at
Daryl:
Heya. First thing to do is to check to see if you can
connect a Viewer PC to your Server PC *on the same LAN*. If you
mouse-over the VNC Server icon in the service tray, it will tell
you the IP address it's listening to. Plug that number into the
Viewer on another LAN PC and see
Ian:
Heya. Are you trying to connect to the PC from behind the
same firewall/router you're trying to configure? If so, that likely
won't work. If you're on the same LAN as that PC, you'll need to
use the LAN IP-address; only if you're off-LAN will the external
side IP address work for
Heya. Wanted to suggest giving EchoVNC a try: it's a utility
that assists making VNC connections regardless of firewalls, routers,
or web-proxies: http://echovnc.gotomyvnc.com
It supports HTTP, SOCKS and NTLM proxies, both on the Server
and Viewer side of the connection, and it
Ms.Su:
Hello! Have you given EchoVNC a try? It's a reflector-like
wrapper for VNC connections that works with all flavors of VNC,
Real, Ultra, etc.
http://echovnc.sourceforge.net/fom-serve/cache/1.html
cheers,
Scott
Is there a plan for the free version of RealVNC to have repeater,
Jiri:
Heya. The problem I think you're having is the use of private
IP address on your wireless network at home. Those addresses are only
valid for LAN's -- they won't work when used across the Internet, even
for ping's.
Have a look here:
Eddie:
Heya. Have a look here for some advice in getting VNC to
run across the Internet:
http://faq.gotomyvnc.com/fom-serve/cache/63.html
The 10061 error I think you're seeing is explained here:
http://faq.gotomyvnc.com/fom-serve/cache/66.html
cheers,
Scott
Hi all,
Please
Frank:
Heya. There's a FAQ here for the question you're asking:
http://faq.gotomyvnc.com/fom-serve/cache/88.html
If the PC you're trying to access runs Windows, the easiest
way to reach it is with EchoVNC. Setup that, use the free demo
echoServer, and connect to it with another
Bill:
Heya. Two quick questions:
snip
The problem is when I try to connect via the VNC Viewer, I get the
infamous Unable to connect to host: connection refused (10061) error.
The address I'm using is the DynDNS domain name, domain.homeip.net:5900
or domain.homeip.net:5901.
snip
Arthur:
Heya. I think Jerry is right. To try his idea out, give
EchoVNC a try. We run a free reflector at demo.echovnc.com that
the statup Wizard will offer to connect you with automatically:
http://www.echovnc.com
It's fully compatible with RealVNC, of course.
cheers,
Scott
Arthur:
Heya. Some answers inline; am CC'ing the EchoVNC email list,
which may be a more appropriate place for this thread long-term.
A couple of questions. I would give the enduser the echoWinVNC.exe after
it's configured. I would run EchoVNC on my computer. When a new user
Vincent:
Heya. Try EchoVNC; it works with any flavor of VNC. You
can get it here: http://www.echovnc.com;.
cheers,
Scott
Is there anything analogous to the repeater program made for UltraVNC
for use with RealVNC? The repeater allows you to have one open port on
a router, but direct
Ben:
Heya. The current generation of VNC Viewers are not, AFAIK,
proxy compatible. I expect that to change with the upcoming releases,
but for now your options are two-fold:
1. The VNC-based CoPilot system (http://www.copilot.com)
2. EchoVNC (http://www.echovnc.com)
The idea of
Hal:
Heya. Have you tried EchoVNC? It has support for HTTP,
SOCKS, and NTLM proxies. For the first two, it relies on the
CONNECT method, which not all web-proxies support. But if your
target connection is listening to TCP 443 (ie, where HTTPS
traffic usually goes), the proxy will
Paul:
Heya. Fortunately, a popular question:
http://faq.gotomyvnc.com/fom-serve/cache/87.html
Hope that helps!
-Scott
Hi
I want to remotely control my pc at home from my office.
At home I am running windows xp professional sp 2 behind a netgeat dg834 router.
At work I am
Michael:
Heya. I think John's suggestion is a good one: some DynDNS
clients monitor for a change in IP address *of the PC they're
running on*, which doesn't help very much if the PC is behind a
router. Activating a DynDNS client that's embedded in the router
itself will be much more
Paul:
Heya. I presume you've got Mailgate setup to act as a web
proxy? If so, you might want to try using EchoVNC to access your
target VNC Server. In general, EchoVNC enables VNC data connections
to VNC servers situated behind unconfigured firewalls and routers,
and it supports HTTP,
Rob:
Heya. There's this other protocol called ftp that (like
some of us) is actually more than 30 years old. :) So don't be too
quick to disparage FAQ's that are just entering kindergarten...
If you get the RFB response, then you're correctly
connecting to the VNC Server's data
Rob:
Heya. Great description of the problem. :) Double NAT'ing,
though, ouch. That's painful. Do you need to run the 5200 in router
mode? Put another way, does anything else to connect to it besides
the LinkSys? If not, it's overkill and bridge mode might work
better.
Rick:
Heya. At the risk of sounding unhelpful...if your client can't
ping from his machine to the other machines he's VPN'd with, then it
sounds like a VPN configuration problem, not a VNC problem. If you know
exactly the VPN client software he's using, I can perhaps point you in
the
Steve:
Heya. You're describing a very common use of VNC, and you
should be able to find a lot of existing documentation about getting
the router's port-forwarding setup, and combining it with a dynamic-DNS
client to achieve what you want to do. For example, one user's experience
is
Stephen:
Heya. When you make a VNC connection, the password you
type is not sent across the wires, not in plaintext, and not
encrypted. Instead, the exchange uses something called challenge
response. Good description here:
http://en.wikipedia.org/wiki/Challenge-response
Works
Stephen:
Encryption will not help prevent session hijacking. It's used
just to insure the privacy of your communication. Anything you do over
an un-encrypted VNC connection can be captured, saved and replayed in
the future. That kinda gives me the creeps. :)
Typical SSL
Jaroslaw:
Heya. Your answer to Kausar is mostly correct. However, with
EchoVNC, you can make a connection to a RealVNC Server without any
firewall or router adjustments on the either the viewer or target LAN.
EchoVNC simply relays connections thru an echoServer, so that
both the Viewer
Tao:
Heya. Sorry, I wanted to be sure: you can or can't ping
the 10.0.0.2 server from your 192.168.50.38 XP client?
-Scott
Hello, everyone
I installed VNC in my xp machine (192.168.50.38) and Windows 2003 Server (
10.0.0.2). I also installed a Fedora linux machine as soft router (
Tom:
Heya. Similar to UltraVNC's single-click...have you tried
echoWinVNC yet? It's part of our remote-support system built around
VNC: http://www.echogent.com/products.htm
The ideas are the same: the end-user starts up a .exe that
requires no installation, and no end-user
Theo:
Heya. So if you run the scan at http://www.GoToMyVNC.com from
the PC you've setup the port-forwarding to...what's the result? If it
doesn't detect your VNC Server, either the port-forwarding rule or the
firewall-exception rule on your VNC Server PC still needs adjusting.
cheers,
Dermie:
Heya. I think this falls under the other suggestions
you asked for. :) Another easy way to support your parent's PC
is thru the use of a single-click VNC solution like echoWinVNC:
http://www.echogent.com/download.htm
The idea is that your parent's fire-up the server
Mike:
Sounds like something's running, but not showing itself.
Try running the free (and really useful) fport utility:
http://www.foundstone.com/resources/proddesc/fport.htm
It will show everything running that's using network
connections.
cheers,
Scott
Hello, I'm new to this
John:
Heya. Just to clarify: you're running the VNC Server on a
WinXP PC, and when you try to connect to it from *another* PC -- not
the same PC -- on the same network...the Viewer screen disappears
after you enter the IP address of the VNC Server -- you never get
as far as a VNC
Sathish:
Heya. As John suggests, I think what you're seeing is the way
it's supposed to work. If PC-A and PC-B are on the same home network,
but PC-A is VPN'd to a remote site, you will very likely *not* be
able to make a VNC connection from PC-B to PC-A.
As the name implies,
Anthony:
Heya. Have a look at EchoVNC:
http://www.echovnc.com
It uses a proxy server called echoServer to relay VNC
connections, regardless of firewall or routers or proxies (even
NTLM proxies), so there's no port-forwarding or firewall adjusts
required at all. Also, the data
this?
Regards,
Wez @ RealVNC Ltd.
Scott C. Best wrote:
Anthony:
Heya. Have a look at EchoVNC:
http://www.echovnc.com
It uses a proxy server called echoServer to relay VNC
connections, regardless of firewall or routers or proxies (even
NTLM proxies), so there's no port-forwarding
, but not the modified versions themselves. The README
doesn't make clear that the modified code is also released under the GPL, nor
does it provide the text of the GPL, nor does it provide an offer of the
source code to the modified version.
Regards,
Wez @ RealVNC Ltd.
Scott C. Best wrote:
Wez
Max:
Heya. The Kaboodle application does this, so you can
find a C++ example of what it's doing here:
http://prdownloads.sf.net/kaboodle/Kaboodle_1.02_src.zip?download
Have a look in LocalInstallWinVNC.cpp in the
RemoteVNC folder.
cheers,
Scott
Hi,
I am installing vnc with
Tomas, Pam:
Hamachi is a good general-purpose UDP tunneling tool, but for
VNC-specific connections, I'd propose that EchoVNC is better:
http://www.echovnc.com
It has a good Startup Wizard that should make it easy for you
to establish your first connection.
cheers,
Scott
Nico:
Heya. The Linux server can be used to port-forward a total
of 5 ports to each of the awaiting VNC Servers. Details here:
http://faq.gotomyvnc.com/fom-serve/cache/64.html
This gets tricker if your client is connected to the
Internet with a dynamic IP-address, or if they
Just to clarify...yes, in EchoVNC all of the packets go
thru the echoServer. We'll be adding a UDP punch-thru to echoWare
so that it attempts direct connections when possible, but it will
always have a highly reliable TCP fallback.
And yes, the rendezvous server (aka, echoServer)
Gary, Biz:
Heya. Yes, setting up an echoServer to act as a relay for
EchoVNC connections will eliminate the need for router configuration
on the VNC Servers. The advantage compared with the also-useful
reverse connection that Gary describes is that you can initiate
the VNC connection
Dan, Franklin:
Heyaz. First off, yes: EchoVNC does this. Similar to GoToMyPC,
you use EchoVNC to login to a echoServer becoming a member of a
connection group on that server. An echoServer can have one or more
connection groups, each one with its own password, but only one is
really
Heyaz. Apologies in advance for the slightly off-topic
post...
I was hoping to hear from some volunteers willing to
test-out accessing VNC servers that are behind either HTTP or
SOCKS proxies. We've recently added that capability to the
open-source EchoVNC project, and while
Dimitry:
Heya. As John said, EchoVNC should work well for you.
The pre-release to version 1.4 has a fix so that it plays
more nicely with RealVNC servers; we've also added HTTP/SOCKS
proxy support:
ftp://ftp.echogent.com/EchoVNC/EchoVNC_1.40PRE02_Setup.exe
With EchoVNC, you
Mike:
Heya; fortunately, your IT guys are wrong about this. VNC
is simply a remote desktop application, not a Virtual Private
Network application. Unlike the latter (in which a remote PC
does traverse your firewall and effectively becomes part of the
LAN), a remote desktop connection
Heya. Another VNC user's experience with getting this
working can be found here:
http://faq.gotomyvnc.com/fom-serve/cache/127.html
In it, it describes the port-forwarding you'll need to
do. If your unfamiliar with how to setup your router to do that,
have a visit here:
Mark:
Heya. So when you open a web browser on your VNC
Server PC, and run the scan at www.GoToMyVNC.com, what
does it say? If it can detect a VNC Server, then you will
be able to connect to your VNC Server from outside of
your LAN using the same IP address the scan is testing.
Heya. Yes, I setup the GoToMyVNC site so that the user
doesn't have control over what port it scans, or what IP address
it scans. I get enough emails from IT staffers as it is. :)
For better or worse, the scan at CanUSeeMe is much less strict:
Ryan:
Heya. Some details on getting a VNC server to auto-start
on Linux are here:
http://faq.gotomyvnc.com/fom-serve/cache/65.html
Hope it helps!
-Scott
good day! h0w can i configure my vnc server to start when our linux server
boots so that i can connect to it and monitor
B-Rock:
Heya. First things first: you should test to see if you got
the port-forwarding on your router correct. On your VNC Server PC,
open a webpage to www.GoToMyVNC.com and run the scan there. If it
can't see your VNC Service, then you've still got some work to do...
One users
Wez:
Just to clarify, EchoVNC isn't its own VNC Server. It's
just a tool to enable VNC connections to standard VNC Servers
without having to make any port-forwarding or firewall-exception
adjustments for the VNC Server PC.
-Scott
Aaron,
Have you tried using the standard VNC release
Boi1der:
Sorry to hear that Comcast has gotten so stringent.
It's about as bad -- and perhaps as necessary -- as WinXP-SP2
changing the default on the builtin Windows firewall from
disabled to enabled.
As John indicated though, as long as Comcast is still
allowing you unfettered
Will:
Heya. Yes, your Linksys router is a NAT'ing router, and
you'll need to setup port-forwarding on it to access a VNC Server
that's behind it. Details of that here:
http://www.portforward.com/english/routers/port_forwarding/Linksys/BEFSR41-v3-v4-v5/VNC.htm
Once you're done
Frederick:
Heya. I'm CC'ing your message to the EchoVNC mailing list,
which is probably a better place for this discussion:
https://lists.sourceforge.net/lists/listinfo/echovnc-users
As to your questions...you make a good point: if a user
is running VNC within a network, they
Christopher:
Heya. Everything you need to know about getting VNC to
work across the Internet can be found here:
http://faq.gotomyvnc.com/fom-serve/cache/63.html
I hope it helps!
-Scott
Hi,
I have installed a tighvnc on my windows xp computer.
I try to connect it at
Frederick:
Heya. First off, doing anything on your school computers
which is contrary to specific IT policy could be grounds for
disciplinary action, or worse. This may be one case in which
asking for permission is easier than asking for forgiveness.
To answer your
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
Bart:
Heya. It's a common question that a lot of new users ask.
Here are the details of another user's experience in getting it
working:
http://faq.gotomyvnc.com/fom-serve/cache/127.html
I hope that helps get you started...
-Scott
Hello, here is the situation. I just
Laurent:
Heya. In just a few words...
http://faq.gotomyvnc.com/fom-serve/cache/64.html
Hope that helps!
cheers,
Scott
Hello Markus,
Thank you for your advices, you have seen right.
Just to be curious, how can we use a server behind NAT in few words ?
Regards,
Laurent.
Mike:
Heya. Getting port-forwarding working with Windows' ICS
is notoriously difficult. The best reference for it I've found
is here:
http://www.homenethelp.com/ics/ics-install-netxp.asp
Instead of ICS, and despite your caps lock key, I would
recommend you consider purchasing a
Munsie:
Heya. Hope this isn't too distracting a suggestion, but
since you've already tried for hours to get it working, and since
your PC's all run Windows on both sides...have you given EchoVNC
a try? Having setup both, I find it a lot easier to setup than a
SSH installation on Windows.
Aldo:
Heya. Yes, to access your .199 PC from the Internet, you
can setup port-forwarding on your router. To test the router setup,
run the scan here:
http://www.gotomyvnc.com
If that scan can see your VNC Server, then your
port-forwarding is setup correctly. It's difficult to
Gary:
Heya. Quick question: when you start the Viewer on the
laptop and specify the desktop server, do you use the server's
PC name or its LAN IP address (10.0.0.xxx I hope)? If using
the IP address doesn't work, what does it say when you run
ping vnc.server.ip.address from the command
Moshe:
Heya. Everything you need to know about making a
VNC connection over the web can be found here:
http://faq.gotomyvnc.com/fom-serve/cache/63.html
Hope that helps!
-Scott
Sorry,but I dont understand how to connect to a remote client over the web.
Can somebody help
Mike:
Heya. If you'll forgive the self-promotion here...the
easiest solution to accessing multiple clients behind different
unconfigured firewall routers is to use EchoVNC. It's not its
own VNC flavor, it just makes existing VNC installations (such as
RealVNC) easier to use. We just
Daniel:
Heya. It's a good question, and fortunately has a
fairly good answer. :) Here's a URL that should help:
http://faq.gotomyvnc.com/fom-serve/cache/64.html
The xxx.xxx.xxx.xx:5930, with one :, tells
the Viewer to connect to Display 5930 which, as above,
would be on TCP
1 - 100 of 331 matches
Mail list logo
