| AJS 4.x
Manual | Note! This Manual is for the "Windows authentication" version, which is designed to work with existing Windows server or Active Directory accounts and Windows authentication. If you want to create accounts by yourself and store their credentials in your own HTTP Commander XML database, you need to download the "Forms authentication" version! This Manual is for the Windows authentication version only! | Web file manager Free Installation assistance Manual Home page

Access internal network resources.

It is still possible to configure Http Commander to use your internal resources, if you decided to host Http Commander outside of your internal network: on our ownwebdrive.com, on Amazon, Azure or another third parties hosting.
First of all you will need to configure VPN (Virtual Private Network) connection between Http Commander server and your internal network.
There are a lot of different ways to configure VPN server in your network. It could be managed by router or by dedicated windows/linux server. Please refer to this article to configure VPN (Routing and Remote Access) server on your Windows Server.
We assume that VPN server already configured and can be accessed outside of your network.

## Creating VPN connection

Now you need to configure VPN connection on your web server (where Http Commander is installed on).

#### To create a new VPN connection (on Windows Server 2008 an later)

1. In the task bar, locate and right-click on the Network icon. Click Open Network and Sharing Center . Network and Sharing Center opens.

2. In Network and Sharing Center, in Change your networking settings , click Set up a new connection or network . The Set up a Connection or Network wizard opens.

3. In Choose a connection option, click Connect to a workplace, and then click Next.

4. In How do you want to connect, click Use my Internet connection (VPN) .

5. If the wizard asks whether you want to set up an Internet connection, make your selection to set one up now or postpone until later.

6. In Type the Internet address to connect to , in Internet address, type the IP address of the VPN server to which you want to connect. In Destination name type a friendly name to help you identify the VPN connection later. Also select any check boxes that are appropriate for your situation.

7. Click Create. The VPN connection is created and the Networks side bar opens to show you the network connections that are configured on the computer.

Connecting by using your VPN connection

After you have created a VPN connection, the easiest way to access it from the desktop is to left-click the network icon in the system tray. The left-click opens the Networks side bar and displays your VPN connection. To connect, left click the VPN connection, and then click Connect, In Network Authentication, type your user name in the format DOMAIN\User name, and then type your password.

## Using internal resources

Note: possible performance issues with network folders
If you have performance issues with network folders (slow loading of file list), then you can try disable Http Commander features which uses metadata when file list is loaded. These features are :

- EnableFilesFoldersLabels - File and Folder labels
- ShowFileMarkWhenExistsDetails - mark for files/folders with filled details (metadata)
- ShowFileMarkWhenLockedByWebdavClient- icon for locked files.

If you will disable those features , file list will be loaded much more faster!

If you use Windows auth version of Http Commander, you can join server into your internal AD and use existing AD accounts for authentication. No further configuration will be required for usage of internal network shares since Http Commander will work under authenticated user identities who already have access (we assume) to network shares.

If you use Forms auth version with user accounts managed by Http Commander, then some additional steps required to configure access to your network folders. Http Commander should work under user account who have permissions (both Ntfs and Share) to access network folder. In short you need to create user account with the same username and password on both sides: Http Commander server and your network file server.

Here are steps to do that:

1. Connect to server where Http Commander is installed on, open computer management, navigate to "Local users and groups" section. Create new user with the same credentials as show on previous step. use account name as username and one of access key as password.
   Hide screenshot

2. Once user created, we need to configure Http Commander application pool to work under his identity.
   Open IIS management console, application pools section, select htcomnetpool (pool under which Http Commander is working).
   Click on "Advanced settings..." link.
   Hide screenshot

3. Navigate to "Identity" row and change it to "Custom account", use credentials for newly created user.
   Hide screenshot

4. Create user with the same username and password on your network file server (if you did not used credentials of existing account on previous step)
5. Make sure that user have correct NTFS and SHARE permissions on network folder.
   Hide screenshot

6. Open Http Commander in browser, login as administrator and open Admin panel.
   Add new shared folder and specify path to internal file share in "Physical path" field. Click on "test access button. Test should be passed if configuration is done correctly.