Another thing to be wary of even if you are behind a router - if you
use the computer running the realvnc server to log onto say a work
VPN, you are no longer behind your own router but that of the work
router and they might not be blocking the realvnc ports. Just
something to keep in mind if using a VPN.
On 9/29/06, Robin Hill <[EMAIL PROTECTED]> wrote:
On Sat Sep 30, 2006 at 06:58:28AM +1000, Paul wrote:
> I want to controll another PC on my *local* network.
>
> Here is what I did...
>
> PC to be controlled 192.168.1.103.
>Installed vnc-4_1_2-x86_win32.exe(free) with defaults.
>Set password, 8 characters.
>Access control-> removed +, added 192.168.1.100, which is the
> controlling PC.
>disabled "Serve Java viewer via HTTP on port:"
>Sharing-> enabled "Never treat new connections as shared"
>On router, port forward port 5900 TCP and UDP.
>XP firewall exceptions, 5900 TCP and UDP
>
> RealVNC viewer connects/works on controlling PC, 192.168.1.100
>
Well, to prevent any internet access, you could also remove the port
forwarding on your router. If both PCs are on the local network then
the router shouldn't be involved at all.
Cheers,
Robin
--
___
( ' } | Robin Hill<[EMAIL PROTECTED]> |
/ / ) | Little Jim says |
// !! | "He fallen in de water !!" |
[demime 1.01d removed an attachment of type application/pgp-signature]
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list