remote-access

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
remote-access [2021/02/13 21:09]
rafi 		remote-access [2021/07/24 22:33] (current)
rafi
Line 1: Line 1:
 ==== Using Privatise for Remote Access ==== ==== Using Privatise for Remote Access ====
  
-Remote access using Privatise is easy to deploy, and can replace clunky hardware. It can be used for encrypted RDP, file sharing, and integration with a Windows server DC for connecting remotely to an Active Directory domain.+Secure Remote access using Privatise is easy to deploy, and can replace clunky hardware. It can be used for encrypted RDP, file sharing, and integration with a Windows server DC for connecting remotely to an Active Directory domain. 
 + 
 +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.
Line 12: Line 14:
  
 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 ===
- 
-{{:add-dc-server.png?400|}} 
  
 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 or Active Directory DC Agent.+1. Click on Add Server/DC Agents under "Get Started" on the left menu.
  
-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 29: Line 37:
 4. Choose General File Sharing Server 4. Choose General File Sharing Server
  
-When you return to Dashboard, you will see the new file sharing server agent with type "Server" with it's IP. You will install this agent on the file sharing server. If you want to connect to this server with a fully qualified domain and not IP, please:+5. Select the group you want to associate the server with. 
 + 
 +You will now be able to see the new server agent under "Manage Server Agents" under "Manage" in the left sidebar. 
 + 
 +To connect to the file sharing server agent using a FQDN or Fully Qualified Domain Name. Go to your [[ROC-DNS|ROC-DNS Control Dashboard]].
  
 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, you can add an IP address of a general local domain, for example of an office router that is port forwarded to a server. 
  
 {{:custom-hostnames.png?400|}} {{:custom-hostnames.png?400|}}
  
-=== Adding a Domain Controller Agent === +----
- +
-To connect to a Windows Server 2012 and above, you will have to fill the following steps. +
- +
-1. Click on Add Server or Active Directory DC Agent.+
  
-2. You will be brought to a page to add either an Active Directory DC Agent or Server. 
  
-{{::updated-ad.png?400|}} +=== Installation ===
-3. Add a name for the Domain Controller agent. This is for your own records and keeping things organised.+
  
-4. Choose Active Directory Domain Controller.+To install the Server Agent, you should login to the server you want to install it on:
  
-5. Add the Local Domain of your DC. For example: Ford.local+1. Then login to your managed company portal from the server itself.
  
-6. The Domain Controller DNS & LAN will now be accessible by Privatise agents in the same group. No configurations or specific local LAN DNS records required!+2. Go to "Manage Server Agents" and Install Privatise with the corresponding agent directly onto the server as seen in the image below.
  
-=== Configuring the Domain Controller ===+{{::manage-server-agents.png?400|}}
  
-Please make sure to have the following settings configured after installing Privatise on your Domain Controller:+----
  
-1. Go to network adapters -> TAP Adapter V9 -> Right Click Properties -> IPV4 -> Right Click Properties -> Advanced -> Unclick "Register This Connection for DNS".+3. Install the downloaded Privatise Installer executable on the server.
  
-2. Go to DNS Manager -> Domain Controller -> Server -> Right Click Properties -> Interfaces -> Click on "Listen on All Addresses".+----
  
 === Troubleshooting === === Troubleshooting ===
  • remote-access.1613250547.txt.gz
  • Last modified: 2021/02/13 21:09
  • by rafi