Morten - this sure sounds like your provider is intending for you to establish a "site-to-site" tunnel between network equipment, as opposed to a "client-to-gateway" connection. If it were the latter, than the provider would be telling you how to make that connection and what client software to use.
Perhaps I'm over-simplifying, but that's just how I read it. -Jim From: [email protected] [mailto:[email protected]] On Behalf Of Morten Brix Pedersen Sent: Monday, September 16, 2013 1:43 PM To: [email protected] Subject: [vpn-help] VPN setup Hi, I'm pretty new to VPN so I am looking for much appreciated help. We need to connect to an external system/API, which requires a VPN-connection. >From the provider we have received information on the ip address on the VPN >peer and a preshared key. Further we had to give them our public ip in order >to restrict connections from just our ip. I setup an AWS EC2 Instance (Windows) and installed Shrew Soft VPN. I am then trying to connect to their ip with the preshared key using IPSec, but the only thing showing up is: bringing up tunnel ... negotiation timout occurred tunnel disabled One thing I notice in the VPN Trace tool is that "Destination" is our servers private ip address and not the public ip address that we gave them. On AWS EC2, it does not seem possible to register the network interface with the public ip. Is there a way to override this destination ip? How can I debug this further? Thanks - Morten.
_______________________________________________ vpn-help mailing list [email protected] https://lists.shrew.net/mailman/listinfo/vpn-help
