ISSTP - a SSTP Client for Mac OSX. This is a sstp GUI client for Mac, use a modified sstp-client as backend which support server-name TLS extension. Some servers(ex: *.vpnazure.net) require server-name, otherwise the sstp connection will be rejected. I've asked a question that links to here: Connect to SSTP VPN using MAC OS X. – RobG Jul 24 '17 at 6:51 Looks like it's only one working way to connect last version mac os to SSTP VPN.
Hello,
I'm using mac os x 10.6.8 snow leopard and trying to run sstpclient.I have installed macports and dmg image of sstp client.Unfortunately I'm getting LCP: timeout sending Config-Requests error message.SSTP server works successfully for windows 7 client.Command line and log below.
Can you please advise, thanks.
MacBook-Air:sbin $ sudo ./sstpc -log-level 5 -log-stderr -cert-warn -user **** -pass **** sstp-tr-ca***** debug
Nov 25 20:28:27 sstpc: Resolved sstp-tr-ca.**** to 184.75.*.*
Nov 25 20:28:27 sstpc: Connected to sstp-tr-ca.****
Nov 25 20:28:28 sstpc: The certificate did not match the host: sstp-tr-ca.****
Nov 25 20:28:28 sstpc: Server certificated failed verification, ignoring
Nov 25 20:28:28 sstpc: Sending Connect-Request Message
Nov 25 20:28:28 sstpc: SSTP CRTL PKT(14)
Nov 25 20:28:28 sstpc: TYPE(1): CONNECT REQUEST, ATTR(1):
Nov 25 20:28:28 sstpc: ENCAP PROTO(1): 6
Nov 25 20:28:28 sstpc: 0x10 0x01 0x00 0x0e 0x00 0x01 0x00 0x01 0x00 0x01 0x00 0x06 0x00 0x01
Nov 25 20:28:28 sstpc: SSTP CRTL PKT(48)
Nov 25 20:28:28 sstpc: TYPE(2): CONNECT ACK, ATTR(1):
Nov 25 20:28:28 sstpc: CRYPTO BIND REQ(4): 40
Nov 25 20:28:28 sstpc: 0x10 0x01 0x00 0x30 0x00 0x02 0x00 0x01 0x00 0x04 0x00 0x28 0x00 0x00 0x00 0x03
Nov 25 20:28:28 sstpc: 0x0a 0xa9 0x1a 0xca 0xb2 0xd7 0x57 0xa2 0xdf 0xa3 0x2d 0xa7 0xa6 0xd1 0x52 0x19
Nov 25 20:28:28 sstpc: 0x61 0x6c 0x86 0xc3 0x6c 0xdd 0x80 0x25 0xbe 0xd8 0x53 0xe7 0x25 0x10 0x75 0xd5
Nov 25 20:28:28 sstpc: Started PPP Link Negotiation
Nov 25 20:29:28 sstpc: Sending Echo-Request Message
Nov 25 20:29:28 sstpc: SSTP CRTL PKT(8)
Nov 25 20:29:28 sstpc: TYPE(8): ECHO REQUEST, ATTR(0):
Nov 25 20:29:28 sstpc: 0x10 0x01 0x00 0x08 0x00 0x08 0x00 0x00
Nov 25 20:29:28 sstpc: SSTP CRTL PKT(20)
Nov 25 20:29:28 sstpc: TYPE(5): ABORT, ATTR(1):
Nov 25 20:29:28 sstpc: STATUS INFO(2): 12
Nov 25 20:29:28 sstpc: 0x10 0x01 0x00 0x14 0x00 0x05 0x00 0x01 0x00 0x02 0x00 0x0c 0x00 0x00 0x00 0x02
Nov 25 20:29:28 sstpc: 0x00 0x00 0x00 0x08
Nov 25 20:29:28 sstpc: Connection was aborted, Reason was not known
**Error: Connection was aborted, Reason was not known, (-1)
/var/log/system
Nov 25 20:28:28 MacBook-Air pppd: pppd 2.4.2 (Apple version 412.5) started by root, uid 0
Nov 25 20:28:28 MacBook-Air pppd: Connect: ppp0 <-> /dev/ttys002
Nov 25 20:28:58 MacBook-Air pppd: LCP: timeout sending Config-Requests
Nov 25 20:28:58 MacBook-Air pppd: Connection terminated.
We've been using Azure's built-in VNet/VPN solution, with a combination of both point-to-site and site-to-site connections, and so far it's worked reasonably well. But our company is very - very - distributed, and we need to grant some remote OS X clients access to resources inside our Azure VNet. And of course, despite it being one of the top requests on UserVoice, MS doesn't support any non-Windows client in their Point-to-Site VPN configuration.
Download Cisco Vpn Client For Mac Os X
So I'm left looking for other options. One possibility, of course, would be to configure each of the remote home offices with, say, a Dell Sonicwall, and configure that Sonicwall with a Site-to-Site VPN connection. But that gets expensive and complicated, and still doesn't allow them to, say, connect to the VPN if they're on the road or at a coffee shop.
So I've been looking into some of the VPN solutions that show up on the Azure marketplace - for instance, VNS3 from Cohesive, or SohaCloud, or pfSense, or whatever. The problem is that these all seem to be focused on the (much more complex) Site-to-Site configuration style - at least, that's what all their documentation seems to be pointing to (for instance, https://cohesive.net/dnld/Cohesive-Networks_VNS3-3.5-Azure.pdf). And all I want is a really simple Point-to-Site configuration.
What's my best (meaning simplest) option here? I'm no network guy, and I start feeling out of my depth (and like I'm headed down a rathole) whenever I start trying to translate the documentation into my particular scenario.
I certainly can't be the only person who's had to figure out how to let OS X clients into an Azure VNet - what's the recommended approach here?
2 Answers
Vmware View Client For Mac Os X
They now support the mac natively using IKEv2: https://docs.microsoft.com/en-us/azure/vpn-gateway/point-to-site-vpn-client-configuration-azure-cert#installmac
You have two workarounds:
- Install a Windows Server on the Azure and connect it to the VNET. You may use it as a jumpbox to access the resource on the VNET.
Vpn Client For Mac
Note: Windows Server only allow 2 users login at same time. If you need to let more than 2 users to connect to the jumpbox, you need to install the RDS services and purchase the CAL.
- Install a VPN server on Azure and let your clients connect to the VPN server.
Note: You need to enable the NAT on the VPN server, because the IP addresses of the VPN clients are not registered in Azure and are un-routable. Every VPN client should use the VPN server's internal IP address as the source address when it tries to access the resource in VNET.