G'day
> You set up a machine to be in VNC listen mode.
I'm very interested to do such a thing. Can you share with us more detail.
1. Have a static IP address.
It would probably would with a dynamically named address, but having a
static ip is simpler.
2. Download and install UltraVNC, Tight VNC, or Chicken of the VNC.
I normally use Ultra VNC on a WinXP machine because
when a client connects from a WinXP machine back to my machine I have
file transfer capabilities.
Tight VNC is faster, but no file transfer.
Chicken of the VNC has a listen mode, and I have not used it. I've
found the PC versions faster, especially when supporting a remote Mac.
3. Make a startup item to have a VNC Client run on your machine in listen mode.
For my machine I use
"C:\Program Files\UltraVNC\vncviewer.exe" -listen
which opens up port 5500 to accept incoming connections.
I could also use
"C:\Program Files\TightVNC\vncviewer.exe" -listen
which opens up port 5400 to accept incoming connections.
4. Configure your router to forward requests to 5500 to your internal
support machine. Your could have multiple machines by opening up
multiple ports on your router.
5. Supply your clients with an easy method to call back into your
site. I have a RB project that I'm happy to share, ie release as open
source, that works well enough with Windows Clients, for Mac clients I
ask them to download the latest version of OSXVNC.
For PC clients I get them to
1. Initially, Turn off their firewall
2. Install UltraVNC
3. Startup VNC server
4. Install the Remote Assistance App
(Which is just a gui to create a batch file which gets launched)
example of the command line
"C:\Program Files\UltraVNC\winvnc.exe" -connect your.support.domain::5500
5. Open up the remote assistance app.
That's generally it, the remote assistance app automatically starts up
the command process.
If it doesn't it means that either the client has not started the VNC
server or still has the firewall running.
6. Initially, set up their firewall to allow VNC connections, then
turn on their firewall again.
For Mac clients I get them to
1. Download and install the latest version of OSXVnc
2. Launch OSXVnc
3. Type in an address to connect back to my machine
4. Press the add button.
No need to shutdown firewalls since Mac firewalls are generally
incoming, not outgoing. ie All the Mac's I've connected to with
firewalls trust outgoing connections.
Obviously this could be automated in the same way I've automated the
windows client, any one that want to add MacOSX support to the open
source remotae assistance app please send me an email offlist to
[EMAIL PROTECTED]
So in summary, after you've set your site up.
1. Get the client to download the VNC version that suits their machine.
2. Get the client to install the app
3. Get the client to connect,
Generally I can start supporting a new remote client in less than 10
minutes for the first instance, and after that it takes less than a
minute.
It even works fast enough over a phone line, ie no broadband. One
client wanted to be able to help their aging parents who have an
ancient Win98 box and connect to the net using a 56K modem. We
configured their laptop and now they just connect to the net, and
launch the remote assistance app whenthey need help.
--
Keith Hutchison
http://balance-infosystems.com http://realopen.org
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
