Sorry, I thought I did, I must have clicked on reply instead of reply-all
-----Original Message----- From: Jerry Westrick [mailto:[EMAIL PROTECTED] Sent: Friday, June 17, 2005 9:20 AM To: [EMAIL PROTECTED]; vnc-list@realvnc.com Subject: Re: New To VNC-First Post Okay, Mark: A little "Netiquet".... (Network Etiquet) You answered this post directly to me, where it should have been sent to the list. The foremost reason for that is so that someone else can then learn from your expiriences, and maybe not required additional time from all the nice people here helping you for free! Generally, you don't send a message personally to someone in the list unless they request you to, or they send you a personal note... On Friday 17 June 2005 17:11, Mark Sarria wrote: > Sandbox setup. > This is what I have so far. For testing purposes I have installed VNC > server on my desktop computer here in the office, and I installed the > client portion on my laptop. Both systems are running windows XP with SP 2. > > I have successfully connected to the server in my office, on my local LAN. > I assume that you know that windows XP comes with it's own RDP software. And that it's slightly more efficient than VNC, and that you've choosen VNC for some other reason (like you also want to connect to linux/unix/solaris etc, or just hate M$ products 8-). > My Office environment > We have a Cisco router 3660,that acts as our DHCP server, firewall, and > Gateway. There was very little in the documentation on how to get pass the > firewall, because I am new to VNC, it seem rather confusing.. > Okay, Before we go into investigating your firewalls, you should know that people can (possibly) spy on your vnc connections while they are going over the internet. So you most probably need some sort of security. This is usually provided by using one of the following: - VPN connections - encrypting tunnels - Using the pay version of RealVNC 8-) The reason I bring this up now is that the method you use (if you want to avoid being spied on 8-) changes the way that TCP/IP behaves between the Vnc client and the Vnc Server. Most people run into the TCP/IP complexities for the first time, trying to setup remote communications (like you are doing 8-). So here's the beef: Assuming you are only using XP and assuming you only want to use VNC and finally assuming you don't want to invest any money.... I would suggest you install an SSH server in your office and in Nicaragua and use putty on the clients to setup encrypted tunnels.... Then you can use the tunnels to Vnc (or rdp) into Nicaragua and/or your office from anywhere in the internet. Jerry > > My production environment > My production environment will have > - 2 windows XP server > - 1 Windows 2000 server > Nicaragua, is using a Linksys Firewall/router, my home office Linksys > Router. > > This is were I am at. > > Thanks > > --mark > > > -----Original Message----- > From: Jerry Westrick [mailto:[EMAIL PROTECTED] > Sent: Friday, June 17, 2005 1:12 AM > To: [EMAIL PROTECTED] > Subject: Re: New To VNC-First Post > > On Friday 17 June 2005 00:50, Mark Sarria wrote: > > I have a general question, it probably has been answered "many a times", > > but I would like to know if I can connect to a computer in another part > > of the world? Meaning I travel a lot between Nicaragua and California. > > When I am in Nicaragua, I would some times like to connect to my server > > in California, and vice versa (California to Nicaragua) > > > > Is this possible with VNC, and what would I need (network > > setup/configuration)to make this happen? > > > > Thanks > > > > --mark > > Hello Mark... > > 1) Yep this is possible... This is what it is for... > 2) Network setup usually gets messy. This has nothing to do with > VNC (which requires a simple TCP/IP connection), but TCP/IP as > used on the internet today is a complex subject... > > To help us help you I suggest you do the following: > > 1) identify the OS of your clients (machines with vnc on screen) > 2) identify the OS of your servers (machines being handled from afar) > > Then to I suggest that you get VNC installed and running on your server > testing with a local client, as this will eliminate problems with VNC > installation/configuration when we get to the network part. > > and Lastly, before you get started on how to configure your network > you need to figure out if your servers are behind a NAT/Router. > > This will get you started, we all are looking forward to you progress > reports... > > Jerry _______________________________________________ VNC-List mailing list VNC-List@realvnc.com To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
