Correction - you don't *need* static IP on both ends to establish a VPN tunnel.
A site-to-site VPN can be done using dynamic DNS. If it's client-to-site, that's not even necessary - only the site side should be static IP. Even with Novell BorderManager VPN, the client side of client-to-site VPN doesn't need static IP.
For example, we use a Cisco VPN concentrator, and we can connect from any client, as long as it's got an internet connection, using either the IPSEC TCP/IP or UDP connection type or the browser-initiated SSL client (which traverses NAT.)
There are other VPN appliances out there that can do much the same.
This probably holds true for open-source software VPN implementations as well.
Main Topics
Browse All Topics





by: DSPoolePosted on 2008-03-07 at 18:16:05ID: 21075545
You will need to create a VPN between your client side and your server side. There is no other way around this. NAT'ing public IP's to a private IP address of your eDirectory tree will be insufficient as SLP won't cross NAT boundries.
Once you have a VPN set up so your client can PING the IP address of the server you wish to reach, then you can install the Novell Client for Windows (currently 4.91 SP4 with 4 or 5 post SP4 patches) and access your resources.
Good thing you have static IP's - you will need static public IP addresses on both sides (client and server) of the network in order to establish a VPN.