Remote connect to windows server 2012 with launchpad
I have a customer running a Windows Server 2012 Essentials R2 domain and trying to connect with his new MacBook Pro running OS X El Capitan remotely using Windows Launchpad however, Launchpad will not connect outside the office. I was under the impression that this was the part of the functionally of this app. Any suggestions on how to connect in to server to access the shared folders while off property? In office, he connects without any issues. I'm trying to make this solution as simple as possible for the customer.
I've setup a VPN connection on hi s macbook, which appears to connect to the network. But still unable to access any of the server shares, or get Launchpad to connect.
I've setup a VPN connection on hi s macbook, which appears to connect to the network. But still unable to access any of the server shares, or get Launchpad to connect.
Hi Houston,
If the VPN connects perfectly, then all your user has to do is:
1) Hold down the "command" button and tap "K". You'll see this appear
2) Type in the path using SMB to start. Like this: 
Lastly, if this is a server that he accesses routinely, you may want to have his Mac mount the server every time he logs on. Please watch the .gif
I hope this helps.
If the VPN connects perfectly, then all your user has to do is:
1) Hold down the "command" button and tap "K". You'll see this appear
2) Type in the path using SMB to start. Like this: Lastly, if this is a server that he accesses routinely, you may want to have his Mac mount the server every time he logs on. Please watch the .gif
I hope this helps.
If you have a working VPN and only need file access then don't worry about the additional app. You can add the shared manually as is shown by Justin above. Do make sure the VPN is connecting to the same subnet as the server on the lan. Are you using your firewall for the VPN?
For those not thoroughly familiar with SBS or Essentials, the #1 rule is "use the wizards".
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Yes, the subnets at either end of a tunnel need to be different. This is why best practice is to use a less common subnet at the main office. I use the last 2 digits of their street address. eg, 12 Maple St = 192.168.23.x
ASKER
Several good answers and thank you! Discovered cause and effect by myself troubleshooting. Changing clients IP scheme on server corrected error.
From the Dashboard, on the home page, use the "set up anywhere access" wizard to configure DNS, VPN, NPS, and certificate. Then under properties of the user, select the Anywhere Access tab and make sure the user is allowed VPN access and access to the shared folders. There should also be an box you can check in the launch pad to always stay connected.
The better option is to use remote web access to access the folders rather than the VPN. This is set up as part of the wizard. VPN's have one major flaw, a tunnel allowing any and all traffic between your corporate network and a remote device. Viruses and hackers can make use of this.
If you need further details please advise.