JavierJ:
Hello! I agree that most networking equipment is not
configurable by the average Internet user (ie, someone who
knows what their email address is but not their IP address).
This makes these rather nifty devices difficult to own and
probably even more difficult to sell. I think
Javier:
Strange that sourceforge didn't work for you. I put
a copy of Kaboodle onto Echogent's FTP server:
ftp://ftp.echogent.com/Kaboodle/Kaboodle_0.80.zip
Slower, but it should work.
cheers,
Scott
Subject: Re: VNC with a router
Date: Mon, 1 Jul 2002 11:09:27 +0200
David:
Hello! Yes, connecting to a VNC server that's behind
a NAT'ing router is very straightforward (well, okay, it's as
straightforward as such things get).
The first thing you need to do is to connect to the
server using the IP address on the *external* side of the
NAT'ing
Bryan:
Heya. Since the VNC server is running on the same machine
as the SSH server, it may be that your VNC server needs to be setup
to Allow Loopback.
Two quick debug steps: after you start VNC on your server,
trying telnet'ing to 127.0.0.1:5903 from the command line of
your
Colin:
Heya. If your win2000 machine is allowing connections to
localhost:5902 then it must be setup to AllowLoopback (one
of the registry options for VNC). If that option is set, it's
possible that LoopbackOnly is also set, which would explain why
your other LAN machines cannot connect.
Dale:
Heya. I've some quick questions and suggestions about
your setup:
I have: A win2000 box, diamond 192.168.0.1, running openssh 3.4p1 under
cygwin, and winVNC 3.3.3 R9, both running as a service.
I can ssh OR VNC from another win200 box, amethyst 192.168.0.14; or a mac
OSX
Ian:
Heya. Two quick suggestions for you:
1. When you're trying to connect to your win98 machine from the
outside world, are you using the 192.168.0.16 address or
the masqueraded address? Of course, you should be using the
latter.
2. If you are using the masqueraded address,
Jaqui:
My guess is that you were being ignored because you didn't
describe what you *had* tried that didn't work. Mailing lists are
typically the first place users go *after* what's described in the
documentation doesn't work. :)
To get Confirm before Connect working in VNC, you
Heyaz. Having answered the same question many times for
many firewalled/gateway'd users of VNC, I got motivated to put
together a little script to answer it for me. :) Have a look here:
http://www.GoToMyVNC.com
Simply, it runs a scan to see if the IP address on your
George:
Heya. I've two suggestions:
1. Go back into your LinkSys setup, and set it up to forward just one
port from the external side to your VNC server: TCP-5900. Choosing
a large range isn't really playing it safe -- WinVNC will listen
on 5900 unless you tell it differently.
Heyaz. This is an announcement that version 0.90 of the
Kaboodle LAN-Management utility for Windows has been released.
Zowee. :)
Kaboodle is similar to other VNC helper applications
like VNC Manager and ZebeDee. It distinguishes itself by being
a collection of many smaller
Bud:
Heya. It definitely sounds as if one of the two sides
of your connection is protected by a firewall, while the other
side isn't. Of course, in the interest of your own sanity,
they both should be protected by a firewall, but that's
another thread completely.
Try this: fire
Heyaz. So I'm using Kaboodle (I know, shocking) on my
Windoze box to get the VNC server listening to port-80 (I'm
adding an Autostart button to it, so users can just dial in
any port they want and click this button to get the service
running without having to fiddle with the registry).
Steve:
Heya. To see if someone's logged onto a particular PC,
you need to turn on VNC logging. There's a registry setting you
need to setup, and the data is written into a WinVNC.log file.
Alternatively, you can try Kaboodle. I tried to reduce the
details to a log VNC usage radio button
Heyaz. This is an announcement that version 0.95 of the
Kaboodle LAN-Management utility for Windows has been released.
This will likely be the last pre-release version before version
1.0 is unleashed on the world.
Kaboodle is similar to other VNC helper applications
like VNC
Whoops...
Heyaz. This is an announcement that version 0.95 of the
Kaboodle LAN-Management utility for Windows has been released.
This will likely be the last pre-release version before version
1.0 is unleashed on the world.
Sorry for the duplicate message! Didn't mean
Dustin:
Heya. You can do some of what you want, but not all of it.
Sorry. :) VNC connections can be view only, so that someone
connecting cannot supply keyboard or mouse inputs -- they can only
watch. But there is no mode of VNC which disables keyboard or mouse
inputs *from the local
Tim:
Heya. Have a suggestion for you:
Here's the deal: I installed VNC on my computer, which runs Windows 98
and has a cable internet connection. I then went to a friend's house,
and we installed it on his computer, which also has Windows 98 and a
cable internet connection. I was
Jonathan:
Heya. Some quick thoughts:
Yes, I can connect to the Vnc host machine through another computer
thats on the router. But when I try to connect to the Vnc host machine
thats on the router through a machine thats outside the router it
doesn't work.
As William
Dustin:
Heya. There's two way to do what you want to do:
1. Use Jim Redman's VNCProxy: www.ergotech.com/misc/VNCProxy.html
You run it on a webserver that's a peer with your VNC server,
then use a special Java viewer to connect with the web-server.
All traffic between the viewer
Mike:
Heya. There's two way to do what you want to do:
1. Use Jim Redman's VNCProxy: www.ergotech.com/misc/VNCProxy.html
You run it on a webserver that's a peer with your VNC server,
then use a special Java viewer to connect with the web-server.
All traffic between the viewer
PT:
Heya. Got two suggestions for you:
1. Try using fport /a. It's like netstat, only it can filter
by application. You can find it at www.foundstone.com.
2. Try turning on VNC logging. The easiest way to do this, is
(imo) to use Kaboodle: open the VNC icon, click on the Server
George:
Heya. I think Matthew's and William's suggestion was spot-on:
you want to setup your firewall/router to forward the ports like this:
ExternalIP:5900 - Internal1:5900
ExternalIP:5901 - Internal2:5900
ExternalIP:5902 - Internal3:5900
Then you only need to change the
Jack:
Heya. Most of my neighbors have DSL with sbcglobal as
well. Here's what you need to do to get VNC working (I presume
you're asking how someone else can connect to you, not how you
can connect somewhere):
1. Connect to the Internet with the EnterNet client, the
one that asks for
Meyer:
Heya. As YDG suggested, you'll need to make 5 port
forwarding entries into the router that's doing the IP address
sharing:
1. External TCP port 5900 to your first PC's port 5900
2. External TCP port 5901 to your second PC's port 5900
3. External TCP port 5902 to your third PC's
Meyer:
Okay, try this: from one of your 5 PC's that's got a VNC
server up and running, open a browser and point it to:
http://www.GoToMyVNC.com
Run the server-detection test that's there. If your
firewall/router is setup correctly, this test should detect all
5 of your
Dave:
Heya. Yes, you're right: I forgot to mention that. If
your PC is on a LAN behind a NAT'ing firewall/router, you will be
unable to use the VNC viewer to connect to your firewall/router's
external, real-world, IP address. Sorry. 'Tis a limitation of
NAT'ing firewall/routers.
Lorenzo:
Heya. Some suggestions for you to try:
Problem 1:
Can't even telnet from the laptops to the server using
telnet 192.168.1.3 5900. Can't use VNC viewers to
connect to it either altough the server registers just
fine.
So on your Win98 server, when you put the mouse
Duncan:
Heya. Some thoughts as to your question:
I have two computers connected via ethernet cards to a hub and then an
Internet server.
I am running both in W98.
I want to connect the two computers over the local connections rather
than across the Internet.
Sounds like
Heyaz. This is an announcement that version 0.99 of the
Kaboodle LAN-Management utility for Windows has been released.
This is the full-featured version; 1.0 will simply include better
integration with the GetEngaged web portal. Once it's built, that
is...
Kaboodle is similar to
Jan:
Heya. Even though you're new to VNC, I think you'll
find it's really easy to use. Some comments inline:
I need to remote-control by internet a PC connected to a LAN (the NT
server but also some W98 clients).
You're using the right software then. :) Just install VNC
on all
running the VNC server.
Point the web-browser to www.GoToMyVNC.com and run the test there.
If it cannot detect that a VNC service is running, then, well, there's
your problem.
Getting closer!
cheers,
Scott
On Sun, 29 Dec 2002, Runco wrote:
Hi,
Scott C. Best wrote:
Again, though
Tim:
Heya. Your setup sounds pretty common, and it sounds like
your DSL router is really doing its job well. :) That is, the
router is preventing someone on the Internet from initiating a
connection to your internal PC's. In the big picture of Internet
security, that's a Good Thing.
Betsy:
Heya. Quick question: is it possible that your cable-modem's
external IP address is changing? I've heard that some cable-companies
give DHCP leases with fairly short short timeouts (~30 minutes). And
when the lease renews, it's intentionally given a different IP
address, so as to
Joseph:
Heya. Since you're running on Windows, might I suggest
that you try Kaboodle? Via its VNC Service icon, you can turn
on logging, get logging reports, and setup VNC to run on whatever
port you want. It handles all the required registry tweaking,
and works with whatever VNC version
Ben:
Heya. If your VNC server is running on Windows, might
I suggest you give Kaboodle a try? Via it's VNC Service icon,
you can activate VNC logging. Beyond that, though, the Show
Log button will parse the file and present the info you really
want to see: who connected from where and
Sylvain:
Heya. What you're asking sounds like what the Listen mode
of VNC viewing is meant to address. Via that mode, you actually
initiate the VNC connection from the *server* side; in the latest
RealVNC version, it's the Add New Client menu item. This will
attempt to initiate a
Jeff:
Heya. There's two ways of doing what you want to do. The
most straightforward is to adjust the port-forwarding rules in
your firewall. Just point external TCP port 5900 to PC#1's port
5900 on your LAN, external 5901 to PC#2's 5900, external 5902
to PC#3's 5900, etc. This way, all of
Jerry:
Heya. The 64.229 address is the real one: if you enter
that IP address into a VNC viewer, it should be able to connect
to your WinXP machine (presuming you've turned off the WinXP
firewall settings...or, better, allowed port 5900 to not be
blocked). To test this...start a browser
Kenny:
Heya. If you're testing using www.GoToMyVNC.com from the
work PC that's running a VNC server, and it's *not* reporting
success...then something is either blocking the packets, or your
VNC server isn't setup right. Please double-check that the LinkSys
router is setup correctly, and
Matthew:
Heya. As is described in the documentation, VNC uses
TCP port 5900+N for the data-channel and TCP port 5800+N
for serving up the Java viewer, where N is the VNC display
number (usually 0).
For your LinkSys box, just setup forwarding from
external TCP 5900 to TCP 5900 on
Matthew:
Heya. Try this:
1. Port-forward external TCP 5900 to internal PC #1's port 5900
2. Port-forward external TCP 5901 to internal PC #2's port 5900
3. Port-forward external TCP 5902 to internal PC #3's port 5900
...
4. Port-forward external TCP 590N to internal PC #N's port 5900
Damian:
Heya. One more suggestion to add to your pile: try
the Mindterm SSH client. I use it at my work, as it allows
me to SSH from my desktop out via the corporate proxy server.
It also has SSH tunnel support, so if you can run an SSH
server anywhere on your home LAN, you can simply
Romain:
Heya. First off, don't worry about ping's not getting
thru: it's not unusual for an ISP to block those. If you can
access your home-PC from work via HTTP or FTP, you're 90 percent
of the way to VNC'ing.
Try this: from your home-PC, open a browser to
www.GoToMyVNC.com and
Pedro:
Heya. I think you may have a simple problem: the IP
address range 169.254.x.x isn't a valid IP address range, so
your PC might be refusing to initiate a connection to it. This
address range is what you'll get when a DHCP lease request fails.
The legit private IP ranges are:
Deven:
Easy. Just adjust the port forwarding setup in the
NAT'ing router that services the LAN with your target VNC server.
Set it up so that TCP-port 5900 on the external side is forwarded
to TCP-port 5900 on your target server (if you can tell us what
brand of router you have, we can be
.
Anyway, how do you configure/set your IP? Is it with winipcfg in
win98? It doesn't seem to let me do it... Maybe Control Panel/Network ?
Pedro Goncalves
On Wed, 19 Feb 2003, Scott C. Best wrote:
Pedro:
Heya. I think you may have a simple problem: the IP
address range
Chris, Mike:
Heyaz. One quick sanity check is to verify that your
router has actually been setup correctly. On the VNC server,
open a browser and point it to www.GoToMyVNC.com and run
the test there. If it doesn't report success, then a real
VNC viewer won't be able to connect either.
Trevor:
Heya. Since you're running a Linux box at home, you
can kill two birds with one stone here by setting up an
SSH tunnel. That is, run a proxy-aware SSH client at work
(eg, PuTTY, Mindterm, etc) and setup a tunnel to your SSH
server on your home network. Then, at work, point your
David:
Heya. Have you given Kaboodle a try? It provides a
functionality similar to SSH tunnels for remotely accessing all
of the VNC servers on a given LAN, but IMO it's better integrated,
having a builtin VNC connection manager and server-detection
system. You can find it here:
Dennis:
Heya. Great post: good to see one with so many details
that usually get left out. :)
Help me understand this, though: are you seeing problems
accessing the problem PC while it's VPN'd with your work LAN?
If so...then it's actually acting correctly. That is, when you
VPN
Peter:
Hello! Thanks for writing. You make some good points I
wanted to comment on:
I'm working now on a version that allows for
a secure tunnel to be setup that doesn't require touching the
firewall settings on either side of the connection.
With all due respect I must admit to
Heyaz. Thanks to Glenn Mabbutt's help, I finally have a
FAQ-o-Matic running for the VNC community. A FOM allows for both
the presentation and categorization of FAQs, as well as end-user
(this mean you!) contributions. You can find it here:
http://FAQ.GoToMyVNC.com
It's a
Jippie:
Heya. Here's what I do with my in-laws (no, really):
have them start a VNC Server and Add Client That connects
their Server to your Viewer, sort of a backwards connection
(better called a server-initiated connection). This way, you
tell your Mum what web address to type in,
Ken:
Heya. It sounds as if your client as a low-end firewall
protecting their network of Win2K PC's. GoToMyPC is clever in
that it can easily circumvent low-end firewall appliances (the
tradeoff to the convenience is that all the data during a remote
control session goes thru GoToMyPC's
JulieAnn:
Heya. There's two ways to do what you're asking. The
first is to simply connect a VNC Viewer to one of the PCs on
the target LAN, and from thereopen a second VNC Viewer
and connect to any other VNC server on the LAN.
The second way would be to use a secure tunneling
DM:
Heya. Loopback is the coolest thing since spam filters,
so it's worthwhile to understand its significance. On your PC,
the Network Interface Card (NIC) or modem create what the PC
thinks of as a data interface. Every interface has an IP address
associated with it, so if you need to
Jorge:
Heya. I've collected a few tips about debugging a VNC
setup that your Dad should be able to follow along with. Have
him start here:
http://faq.gotomyvnc.com/fom-serve/cache/76.html
After that, point him towards the Troubleshooting
section of the site:
Bertrand:
Heya. Try this: when you initiate the SSH tunnel from
the SSH client, specify the VNC Server's IP address as the host
IP address, rather than the lookback IP address (127.0.0.1). So:
use: ssh -l username -L 5900:ip-address:5900 ip-address
instead of: ssh -l username
Linas:
Heya. I recall reading that there may be a bug in the
latest Windows version, where you need to specify the port in
the VNC Server Properties to 0 (or something) and not choose
Auto. Try that and see if it helps.
If not, head here: http://FAQ.GoToMyVNC.com; and look
in the
Steve:
Heya. I got something of a list of VNC flavors here:
http://FAQ.GoToMyVNC.com
In the VNC Flavors and Add-On's section. Nothing there
yet about flavor-specific options/hacks, but it's doable. If I'm
missing anything you know about, or if you want to update the info
Emi:
Heya. Since you're able to get all the way to a password
prompt, you're 90-percent of the way there. Have you tried connecting
to the VNC Server with different encoding modes, and using different
Viewers? What version is the VNC Server running?
Lastly, try dialing down the
Matthew:
Heya. Here's some more info on getting VNC to work behind
a firewall/router appliance like your LinkSys box:
http://faq.gotomyvnc.com/fom-serve/cache/63.html
Hope it helps!
-Scott
Im using a Linksys brand 4-port cable/DSL 10/100 Ethernet router. How do I
Raghusimha:
Heya. Try following this troubleshooting guide, see if
it helps:
http://faq.gotomyvnc.com/fom-serve/cache/4.html
I tried to set it up in order of easiest to check
first, with increasing specificity. Hope it helps!
-Scott
Hi,
I am new to VNC and I have been
Mark:
Heya. Yes, it's a well-beaten question, but you asked
it so nicely I can't help myself. :) Have a look here:
http://faq.gotomyvnc.com/fom-serve/cache/63.html
I collected some info on how to setup VNC and your
LAN's firewall so that they play together nicely. I hope it
Stephanie:
Heya. I'm going to presume that you're running a VNC
Viewer on a Windows PC, trying to connect to another Windows
PC that's running a VNC Server. To get started, it's just:
http://www.realvnc.com/winvncviewer.html
Usually, in the prompt for the VNC Server name, you'll
Rob:
Heya. FWIW, I keep a list of VNC add-on applications which
enhance the functionality of VNC:
http://faq.gotomyvnc.com/fom-serve/cache/3.html
File-transfer is handled by many apps mentioned there: eSVNC
does it as part of the VNC platform itself, Kaboodle does it as part
of
Mr. Wang:
Your target VNC server at work is most likely behind
*some* sort of firewall, either a personal firewall like
ZoneAlarm or WinXP's builtin one, or a NAT'ing router. I'd
be amazed if there really was no firewall at all.
I've collected some suggestions into a
Jeremy:
Yes, the firewall/proxy setuyp you have at work is most
likely blocking your attempts to connect to a non-popular TCP
service (ie, something not associated with web-browsing, ftp'ing,
or telnet'ing).
Your best bet is to setup an SSH or Zebedee tunnel from
your workplace
Mr. Wang:
Since PC2 can ping PC1 via the dial-up network, you should be
very close to having a VNC connection work. Please tell me, though:
what is the exact error message you see when your connection attempt
fails?
-Scott
Hello, Barry Zubel:
Some details show as follows:
My
Heya. Hope the info here helps:
http://faq.gotomyvnc.com/fom-serve/cache/64.html
-Scott
Hi, all! How can I use VNC with a PC connected to Internet via router?
I need to control a MS-based network remotely...anybody can help me?
Thanks
___
Eric:
Heya. Seeing a black-screen after you log into a VNC
Server running on a WinXP machine is symptomatic with the Fast
User Switching incompatibility between VNC and WinXP. From the
RealVNC website:
| VNC will work with XP provided that Fast User Switching and Remote
| Administration
Mark:
Heya...
Something I found out which may be the issue is that the vnc
servers I am trying to connect to behind the firewall are using the
same IP addressing I am using from my home LAN which could be the
issue. Both sites are using 192.168.1. addressing. So when I try to go
on list once...
Lastly, try running a copy of fport on your VNC server,
and verify that the application really is running:
http://www.foundstone.com/resources/proddesc/fport.htm
Good luck!
-Scott
On Fri, 15 Aug 2003, Karl wrote:
On 14/08/2003 at 5:53 p.m. Scott C. Best wrote
Wow, this is almost real-time debugging. :)
Can you VNC into your troublesome machine from a PC on
the same LAN? At least, get to the password prompt?
-Scott
On Fri, 15 Aug 2003, Karl wrote:
On 14/08/2003 at 10:35 p.m. Scott C. Best wrote:
Karl:
Hurm
Karl:
I think I've become convinced that one of your ISPs (either
at home or at work) is blocking ports, perhaps in response to the
very recent press about the MSBlast worm that comes to life this
weekend.
If your mini-LAN test at works shows that the VNC server
is working
Dave:
Heya. That's sort of the point of the scan: a lot of VNC
users have setups similar to yours wherein the IP address that
a VNC Viewer should use to connect to your VNC Server is *not*
the same IP address as the PC on which the server is running.
Something along the way (either, as
Dave:
Heya. So...exactly what is the make and model on your DSL
modem/router? And...can you open a web-browser and connect to it
with http://ip.address.of.router;?
-Scott
Heya. That's sort of the point of the scan: a lot of VNC
users have setups similar to yours wherein the IP
Erica:
Heya. Since you're getting as far as a password prompt, we
can rule-out anything having to do with your DSL or VPN connection.
Which is good...that's usually where 90-percent of the troubles lurk.
As Adam said, this sounds a lot like the very-common problem
that people
Jens:
Heya. Your question is something of a FAQ; I hope it's
answered well-enough here:
http://faq.gotomyvnc.com/fom-serve/cache/87.html
cheers,
Scott
Hello,
I am using this list the first time and hope I do everything all right.
I run vncserver on my PC at home, and at work, I
for us. Hope that helps!
Bob
-Original Message-
From: Scott C. Best [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2003 6:24 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Question: proxy server
Jens:
Heya. Your question is something of a FAQ; I hope
Michael:
Heya. I think I'm willing to split this hair over VNC
security.
First off, I agree with you that VNC users should try to
use a secure-tunnel whenever they VNC across the Internet. That
just a inarguable Good Idea. For those using VNC to remotely
administer their
Possibly the easiest way to test it is to startup a
web-browser on the VNC server and point it to www.GoToMyVNC.com
and run the scan there. If it can connect from the outside,
then your firewall/router is setup correctly.
Hope this helps!
-Scott
From: Michael Herman [EMAIL
Bjorn:
Heya. Some comments to your comments:
If I wanted to sniff other people's VNC traffic i'd first try to find
an existing program to do this. If I couldn't find one I would:
1: use one of the existing programs that can intercept TCP sessions.
Maybe I'd have to teach it how to
Colin:
Heya. I wrote up something of a FAQ to help guide new
users to get VNC working from behind a firewall:
http://faq.gotomyvnc.com/fom-serve/cache/63.html
Hope it helps!
-Scott
Hello,
I need some help. I am trying to connect from behind a firewall using VNC
viewer to a
Ralph:
Hello! Congrats and best-wishes on the upcoming arrival!
I hope everything goes perfectly.
Regarding your remote-access question: you can't do it
(with VNC) without the support of your company's IT staff. Sorry.
You have to admit it'd question the integrity of your
Vince:
What you describe works nicely if someone is sitting
in front of the PC that you to give someone else remote
control over. It doesn't help at all with *taking* control of
a PC that's sitting on a remote network protected by a firewall.
I suppose some sort of script can be
Ravi:
Heya. I've written up a VNC Troubleshooting guide here:
http://faq.gotomyvnc.com/fom-serve/cache/4.html
As that guide will suggest, you should open a web-browser
on your VNC server and point it to http://www.GoToMyVNC.com;.
That will confirm whether a VNC connection from
Jens:
Heya. It sounds like you're well-protected behind a good
proxy at work. Sorry. :)
Proxies can be configured to allow only certain applications
to pass through them, by filtering based on the user-agent string
that an application tells to the proxy. That is, your SSH client
Sean:
Heya. Is it possible that the target VNC Server
is running with an AuthHosts setting? That is, it may be
setup to restrict connections from anything with an IP
address in a limited range; when you dialup you may be
given an address in this range.
You'll need to look in the
Sean:
Hmmm. I am unsure if 'Failed to connect to server' is
an authoritative reply from the VNC server or not. So try this:
startup a web-browser on your VNC Viewer, and point it to
the VNC Server: http://vnc.server.ip.address:5800;. See
if that can connect.
Alternatively, try
Dai:
Heya. Sorry for the late reply. The scan at GoToMYVNC
only checks out port 5900-5909; the browser-based VNC Viewer
needs to use port 5800 as well. So it sounds like you setup
your router to let port 5900 thru...but did you forget to setup
port 5800?
cheers,
Scott
Situation: I want
Frank:
You're right that it's a beginner's question; still not
a stupid one though. :) Fortunately...it's also a Frequently
Asked Question:
http://faq.gotomyvnc.com/fom-serve/cache/63.html
In general..you'll need to setup the port-forwarding on
your LinkSys router, and then open
(GMT)
From: Scott C. Best [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Kaboodle 0.99b released!
Heya Kaboodle users. This email is an announcement of the
version 0.99b release of Kaboodle. You can find it here:
http://www.kaboodle.org
This new version has the following
Peter:
Heya. I help run a Faq'o'Matic server for VNC stuff where
you can contribute q's and a's: FAQ.GoToMyVNC.com
Thanks in advance for any contributions!
-Scott
Hello all,
Where can I send reports of typos outdated links in the FAQ (
http://www.realvnc.com/faq.html) /or
John:
Heya. With many broadband services, the IP address given
by the ISP will change very frequently. The easiest way to work
around this is to install a dynamic DNS client on the target
PC you're trying to connect with. Though I don't use it, this
service seems very popular (and free):
Hari:
Heya. You ask a fairly common question: your PC is on
a LAN that uses the 192.168.*.* address range, but those IP
addresses are for internal, intra-LAN only. Somewhere on
your network, there's a router which automatically translates
your internal 192.168.x.y IP address into a real IP
Lauren:
Heya. It sounds as the other PC's in your library simply
already had VNC installed on them, by an administrator-level user.
So installing VNC again as a non-administrator...it sounds like
you got the right error messages. :)
FWIW, there are many VNC-helper apps out there
David:
Heya. It sounds as if your father-in-law is simply giving
you the wrong IP address. That is, it's possible he's giving you
the IP address that's valid on his network, which isn't the same
thing as the IP address that the rest of the world sees him by.
This process of IP address
Howard:
Heya. Here's a more recent discussion about VNC and
NAT'ing firewall/routers like your DLink:
http://faq.gotomyvnc.com/fom-serve/cache/133.html
snip
I have dug through the archives, but I must confess that I didn't
understand a lot of what I saw there, especially concerning
1 - 100 of 331 matches
Mail list logo
