Setting up a VPN Connection

Guide to connecting to Epic's virtual private network (VPN) in order to access the Perforce server and obtain the engine.


This document will guide you through the steps in setting up a secure Virtual Private Network (VPN) Connection to Epic Games so that you will be able to connect to the Perforce depot. Once you have a VPN Connection set up, you can set up Perforce .

Epic has set aside the 2nd and 4th Sunday of the month from 8am-Noon EST for performing scheduled maintenance. Please keep this in mind when planning as it is possible that any or all of the support outlets, especially network/server resources, could be affected during these times.

Your VPN credentials are not the same as your UDN credentials. There is one set of VPN/P4 credentials and they are issued on a per-project basis. Your technical contact will have this information.

Connectivity Policy

VPN connectivity to Epic comes in one of two ways. The first allows the studio to have up to five open VPN connections directly to Epic's proxy server from internal workstations. The second method allows for the studio to connect their own proxy directly to Epic's depot, from which the studio's developers will connect to their local proxy. Two concurrent VPN connections are allowed from this local proxy to the depot, a primary and a backup.

Please understand that these methods are independent of each other and a studio cannot have both connection types in place. In either case, the number of concurrent Perforce connections on a machine are not limited, just the number of VPN connections from a studio.

VPN setup is the same for your local proxy as it would be for a user.

Supported Clients

The only currently supported client for creating a VPN connection is the AnyConnect VPN Client by Cisco . This client has been tested and verified to run on all versions of Windows.



Some antivirus programs as well as firewalls can cause issues for the VPN connection. Make sure to configure them to allow the VPN connection to be established.

Web Installation

Please note that the following browsers are supported:

  • Internet Explorer

  • Firefox

Other browsers such as Chrome and Safari are not supported; they may work, but have not been tested. This should not be limiting as the browser is only needed for the initial connection.

In order to install the VPN client via the web, you will also need Java installed.

Client Installation and Configuration

NOTE: The IPSEC/TCP VPN client has been phased out. Please use the SSL client. System requirements for the Linux client can be found here .

Windows and Linux Installation via Browser

NOTE: This is a web-based VPN client. It has been reported to be more stable when run in Internet Explorer.

Be sure to disconnect from any existing VPN sessions you have open!

  1. To begin the web installation of the Cisco AnyConnect VPN Client, go to .

    Regional VPN Mirror Sites:


    You may receive a certificate warning if you use one of the old host names. Please use to avoid this warning.

  2. Double-Click on the bottom of the window where it says Internet or Internet zone and then click on "Trusted" and click Add and add this site to your trusted zones.


  3. Login with your existing VPN account info.


  4. The installation process should begin automatically.

    If using Internet Explorer, the ActiveX control will need to be installed. Follow the instructions to allow it to be installed.


  5. The wizard will continue through the process once the ActiveX control is installed. Java is used to complete the installation and must be installed as well.


  6. The installer will be downloaded.


    Note: If using Vista or Windows 7, you will be prompted to allow the installation.

  7. Once the installation is complete, it should auto-connect; and an icon will appear in your Task Tray.


This process installs the AnyConnect client on your PC. This means you can simply run the application to connect in the future. It does not add an entry to the Start Menu in Windows, however. For details on connecting to the VPN manually using AnyConnect, see the Connecting to the VPN via AnyConnect section.

Once you set up the VPN connection, you can continue on to set up Perforce .

Additional Notes

If you are running Windows Vista, the feature that allows you to use the Internet and other local resources that are not on the VPN (while you are connected) will not work. As soon as you disconnect, everything should return to normal.

Even still, if you are still experiencing problems, you can run the following commands at the MS-DOS command prompt:

ipconfig /flushdns

(You may have to run the command prompt as an Administrator.)

Make sure to add the correct localgroups ("Users" and "Interactive") to get everything to work as normal.

Windows Manual Installation

The AnyConnect VPN client can be downloaded from Cisco's website at the following URL:

AnyConnect VPN Client Download

Once downloaded, simply install the application and then proceed to Connecting to the VPN via AnyConnect for details on how to use it to connect to the VPN.

Linux Installation via Console

Please used the installers attached at the bottom of this article.

Connecting to the VPN via AnyConnect

Connecting to the VPN with AnyConnect is a straightforward process.

  1. Run the AnyConnect VPN Client.


  2. Enter the url into the Connect to: field:


  3. Press the Enter key to display the authentication fields:


  4. Enter your VPN connection information (username and password) into the fields:

    username and password

  5. Press the Connect button to connect to the VPN. When the connection is made, the vpn_anyconnect_connected.jpg icon will show in the taskbar.

Once you set up the VPN connection, you can continue on to set up Perforce .

Connecting to the VPN via OpenConnect (Unsupported)

OpenConnect is an open source alternative to AnyConnect. Since this package is maintained with a number of Linux distributions, it is more likely to work with distributions not supported by Cisco. If the following packages are installed, you should be able to connect via OpenConnect:

  • vpnc-script

  • openconnect

These packages can usually be installed via yum (e.g. yum vpnc-script).

This is a sample connection command that allows batch connection:

echo password > openconnect -u vpn_username --passwd-on-stdin --script /etc/vpnc/vpnc-script

East Asian VPN Mirror

If you do not have it already, go to and download the SSL VPN client.

Once installed, you can just add as the address in the client.



Troubleshooting Installing the VPN AnyConnect Client:

In some cases, Windows users have received error messages related to an UTN_USERFirst_Hardware certificate upon trying to install the VPN client. This relates to a trust issue with the existing certificate and the new Cisco certificate. In order to resolve this issue, please use the following steps:

  1. Open a run prompt and type in certmgr.msc.

  2. Expand the tree labeled Third-Party Root Certification Authorities.

  3. Find the certificate on the right labeled UTN_UserFirst_Hardware.

  4. Cut this certificate from this location and paste it into Trusted Publishers.

  5. Re-run the installer.


Whenever you get the following error message, typically reinstalling the client & rebooting the machine should take care of it:

Reason 442: Failed to enable Virtual Adapter.

The following message indicates an authentication problem on the server-side:

Secure VPN Connection terminated by Peer.
Reason 427: Unknown Error Occurred at Peer.

Direct Support

If you are having any problems with connecting to the VPN, please do the following:

  • Post on the Unreal Developer Network with the following information: 1. Your geographic location (Continent, Country, City, etc.). 1. Your internet service provider (if known). 1. Times you have seen this issue; and for how long. 1. A traceroute to

Our IT Department will work to help you resolve the problems in as timely a fashion as possible.

Select Skin

Welcome to the new Unreal Engine 4 Documentation site!

We're working on lots of new features including a feedback system so you can tell us how we are doing. It's not quite ready for use in the wild yet, so head over to the Documentation Feedback forum to tell us about this page or call out any issues you are encountering in the meantime.

We'll be sure to let you know when the new system is up and running.

Post Feedback