Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
remote-access [2020/11/27 07:57] rafi |
remote-access [2021/07/24 22:33] (current) rafi |
||
---|---|---|---|
Line 1: | Line 1: | ||
==== Using Privatise for Remote Access ==== | ==== Using Privatise for Remote Access ==== | ||
- | One of the most requested features we have seen over the last year has been software based remote access. | + | Secure |
- | We're excited | + | The advantage over using a Privatise Server Agent is that it's easy to setup & allows for secure remote access without having to expose an entire LAN. This makes the connection more secure. |
- | 1. You can use Privatise to connect remotely via the Privatise VLAN while still allowing your internal office machines to connect over the normal LAN! | + | 1. You can use Privatise to connect remotely via the Privatise VLAN while still allowing your internal office machines to connect over the normal LAN. |
2. Privatise supports Windows Server 2012 and above for integration with your Active Directory Domain Controller. | 2. Privatise supports Windows Server 2012 and above for integration with your Active Directory Domain Controller. | ||
- | 3. You can create custom Fully Qualified Domain Names and attach them to static internal IPs (NAT' | + | 3. You can create custom Fully Qualified Domain Names and attach them to static internal IPs (NAT' |
Remote Access is supported by version 2.0.3 on the Windows Agent and above. | Remote Access is supported by version 2.0.3 on the Windows Agent and above. | ||
Line 15: | Line 15: | ||
Important: When joining an AD Domain, make sure that you have admin access to that client PC in case of any issues or if you have to reset the domain! | Important: When joining an AD Domain, make sure that you have admin access to that client PC in case of any issues or if you have to reset the domain! | ||
- | === Setting up a Remote Access agent for file sharing === | + | ---- |
- | {{: | + | === Setting up a Remote Access agent for file sharing === |
Setting up a remote access agent for file sharing is easy to do. Simply follow the following steps: | Setting up a remote access agent for file sharing is easy to do. Simply follow the following steps: | ||
- | 1. Click on Add Server | + | 1. Click on Add Server/DC Agents under "Get Started" |
- | 2. You will be brought to a page to add either an Active Directory DC Agent or Server. | + | {{::add-server-agents-dc.png?400|}} |
- | {{::select-filesharing.png?400|}} | + | ---- |
+ | |||
+ | 2. You will be brought to a page to add either an Active Directory DC Agent or File Sharing Server. | ||
+ | |||
+ | {{:file-sharing-server.png?400|}} | ||
+ | |||
+ | ---- | ||
3. Add a name for the file sharing server agent. This is for your own records and keeping things organized. | 3. Add a name for the file sharing server agent. This is for your own records and keeping things organized. | ||
Line 31: | Line 37: | ||
4. Choose General File Sharing Server | 4. Choose General File Sharing Server | ||
- | When you return | + | 5. Select the group you want to associate the server with. |
+ | |||
+ | You will now be able to see the new server agent under "Manage | ||
+ | |||
+ | To connect to the file sharing server | ||
1. Go to Local DNS Records | 1. Go to Local DNS Records | ||
2. Add a Fully Qualified Domain Name on the left, and static IP of the Privatise agent you want to connect to. | 2. Add a Fully Qualified Domain Name on the left, and static IP of the Privatise agent you want to connect to. | ||
- | |||
- | 3. Alternatively, | ||
{{: | {{: | ||
- | === Connecting to an AC DC Agent === | + | ---- |
- | To connect to a Windows Server 2012 and above, you will have to fill the following steps. | ||
- | 1. Make sure routing & remote access is enabled on your Windows Server 2012 and above. | + | === Installation === |
- | 2. Click on Add Server | + | To install the Server Agent, you should login to the server you want to install it on: |
- | 3. You will be brought | + | 1. Then login to your managed company portal from the server itself. |
- | {{:: | + | 2. Go to " |
- | 4. Add a name for the Domain Controller agent. This is for your own records and keeping things organised. | + | {{:: |
- | 5. Choose Active Directory Domain Controller. | + | ---- |
- | 6. Add the IP of your Domain Controller. | + | 3. Install |
- | 7. Add the local NAT range of your Domain Controller. | + | ---- |
- | + | ||
- | 8. You will now see the static IP added to that agent in the main dashboard. | + | |
- | + | ||
- | {{::dc-ip.png? | + | |
- | + | ||
- | 9. The Domain Controller DNS & LAN will now be accessible by Privatise agents in the same group. No configurations required! | + | |
=== Troubleshooting === | === Troubleshooting === | ||
Line 82: | Line 83: | ||
A. Most likely you did not install the correct agent on the DC or file sharing server. DC & file sharing agents are specifically configured to allow for normal LAN access. | A. Most likely you did not install the correct agent on the DC or file sharing server. DC & file sharing agents are specifically configured to allow for normal LAN access. | ||
+ | |||
+ | Q. **Privatise keeps restarting on the Domain Controller** | ||
+ | |||
+ | A. Disable DHCP autoconfiguration. Please see [[https:// |