Yes, if we can get one computer set up, we can probably do the others relatively easily.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Richard Clegg Sent: Tuesday, March 19, 2002 3:06 AM To: '[EMAIL PROTECTED]' Subject: RE: VNC and NAT There's always SSL if you really want to be secure, but I think we should probably get him connecting first, before we start anything else. ;) -----Original Message----- From: Tony Wright [mailto:[EMAIL PROTECTED]] Sent: 19 March 2002 08:56 To: '[EMAIL PROTECTED]' Subject: RE: VNC and NAT I have a netgear router and in there you can route ports to different internal ip's. I have set mine so one computer is on 5800/5900 (the pc is on screen 0) and another is on 5801/5901 (the pc is on screen 1) This way depending on which address I use 5800 or 5801 I connect to different PC's on my net work. Do you really need dhcp on your internal network? could you not just allocate fixed IP's? Regarding the external IP address I am using DNS2GO. So in my web browser I just type www.xxx.com:5800 or 5801 Mind you I suggest setting IP authorisation on your clients to restrict who can connect as the 8 char password doesn't appear very strong to me. (Has anyone done anything about this? even adding a username would make it a lot more secure) Tony Wright -----Original Message----- From: Richard Clegg [mailto:[EMAIL PROTECTED]] Sent: 19 March 2002 08:22 To: '[EMAIL PROTECTED]' Subject: RE: VNC and NAT Alternatively, if you're running in a Windows environment, you could use some software like DNS2Go (http://dns2go.deerfield.com) which runs on the PC you want to connect to, i.e. your home machine, and you set it up to send out a 'heartbeat' which keeps a domain set to point at that address. Because the 'heartbeat' originated from your PC, connecting to that domain connects you directly back to that PC. That's the way I got round NAT and DHCP, but there are probably others. Doesn't solve the port problem, though. Rich -----Original Message----- From: Scott "The Axe" O'Bryan [mailto:[EMAIL PROTECTED]] Sent: 19 March 2002 05:53 To: [EMAIL PROTECTED] Subject: RE: VNC and NAT That is correct, but as we know, the DHCP MAY change at the most inconvienient times. You can set up your DHCP server to assign addresses only within a certain range and then fix the IP of the VNC server outside of that range. For instance, my network topology looks like this: Other network systems: Router: 192.168.1.1 DHCP: 192.168.1.100 - 192.168.1.254 VNC Server: IP Address: 192.168.1.10 Gateway: 192.168.1.1 DNS: The DNS for your ISP. This always works if you have access to your DHCP configuration. If not, well then there is nothing you can do. Also, if your DHCP is due to your ISP on some sort of Broadband connection, then I suggest TZO (www.tzo.com), they will fix an IP Address to an ISP's DHCP. But make sure that you have some sort of firewall in place. Hope that helps. Scott -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of H. Phil Duby Sent: Monday, March 18, 2002 9:33 PM To: [EMAIL PROTECTED] Subject: Re: VNC and NAT ----- Original Message ----- From: "Jason Crooks" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 18, 2002 9:36 AM Subject: VNC and NAT > Hello, > > Is there anywhere I can get some answers on connecting to a VNC server that > is behind a router doing DHCP and NAT? I am doing that with a 3COM router with DHCP and NAT. All I needed to do was go to the 'virtual server' configuration page (configuration is through web browser), set ports 5800 and 5900 to forward to the machine with VNC server running, and enable them. Even with DHCP, the IP does not change often enough to be a problem. I think I've seen it change once in the past year plus. YMMV > Thanks > > ----------------------------------------- > Jason Crooks > [EMAIL PROTECTED] -- Phil --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
