I appreciate the information, but, I am attempting to connect VNC with the local LAN IP 198.162.2.abc. This is after I connected the VPN on the external IP address 70.abc.ad.ds
dean __________________________________________________ Dean Richardson SCOPE Management Solutions, LTD. PO Box 5554 Alvin,TX 77512 P: 281.387.6659 F: 281.331.7794 [EMAIL PROTECTED] -----Original Message----- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 25, 2005 1:26 PM To: [email protected] Cc: [EMAIL PROTECTED] Subject: Re: Linksys WRV54G Dean: Sounds like you've found your problem. Since you make the VPN connection to your customer's server *first*, then the IP address you need to use for the target VNC Server should be your customer's *internal* IP address -- something like 192.168.2.abc -- *not* their external IP address (ie, the one you use to establish a original VPN connection). Put another way, once you've "VPN'd" with your customer, you're "virtually" on their LAN already (so you don't, as you ask, need to worry about port forwarding). cheers, Scott > If I am understanding your question correctly, I am connecting to the > route (customer's server) from outside the LAN (customer's). I am in > my office with the Linksys router. First connection made to the > customer's server is with the Sonic Wall Global VPN Client, which > works fine. Second connection attempt is with either VNC or Dameware, which times out. > > > Customer's network is setup on 192.168.2... LAN and my network is set > up with 192.168.0..... Network. > > > If I am connecting via VPN connection, do I even need to set up port > forwarding? And if so, do I need it set up on the Linksys Router in my > office which is sending the request to the other network? I have tried > this. > > dean _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
