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.

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.

3. You can create custom Fully Qualified Domain Names and attach them to static internal IPs (NAT'S) of the Privatise agents.

Remote Access is supported by version 2.0.3 on the Windows Agent and above.

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 is easy to do. Simply follow 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.

3. Add a name for the file sharing server agent. This is for your own records and keeping things organized.

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:

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.

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.

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.

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.

5. Add the Local Domain of your DC. For example: Ford.local

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!

Configuring the Domain Controller

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”.

2. Go to DNS Manager → Domain Controller → Server → Right Click Properties → Interfaces → Click on “Listen on All Addresses”.

Troubleshooting

Q. Can't Connect to AD Domain Controller

A. Check IPConfig on the AD DC, and make sure that it has the correct Static IP. Make sure that you only used the agent once, as static IPs do not support multiple installs. On the client machine, make sure that the agent you have installed is in the same group as the AD DC.

If that is correct, make sure you configured routing correctly on the Windows Server. See this video for more information.

Q. I'm not able to add an AD DC or File Sharing Agent

A. Make sure that the group you want to add the agent to has a ROC. Please see Provisioning a ROC for more information.

Q. Installing an agent broke my file sharing server or DC locally & I had to remove it. What happened?

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 Disabling DHCP Autoconfiguration for more information.

  • remote-access.txt
  • Last modified: 2021/02/13 21:09
  • by rafi