How To Add Additional VPN Endpoints
Connect to the Netflix Global Login as this will ensure your VPN client is being geolocated to the closest gateway. Connecting directly to a specific gateway disallows redundancy in the event there's a failure on a given gateway.
These endpoints can be added to all supported VPN proxy clients. When adding an additional endpoint, choose the one closest to your physical location. Each endpoint’s path has a specific use:
-
emp: Reserved for full-time employees and contractors with a Netflix email account.
-
Note: If you need full-tunnel access, add your account to the vpn-full-tunnel Google Group. For LAN access, request membership to the vpn-lla Google Group.
- Full-tunnel access routes all of your web traffic through the VPN.
- LAN access allows you to connect to other devices, like printers, that are using the same network.
-
Note: If you need full-tunnel access, add your account to the vpn-full-tunnel Google Group. For LAN access, request membership to the vpn-lla Google Group.
-
contractors: Reserved for contingent workers.
- Note: For full-tunnel access, request membership to the vpn-full-tunnel Google Group. For LAN access, request membership to the vpn-lla Google Group.
-
*-split: Indicates an endpoint using a split tunnel connection.
- Split tunnels only route specific web traffic through the VPN. Choose which apps to secure via VPN, and which apps run on an open network.
-
nas: Reserved for employees with a Netflix Animation email account.
- The default endpoint for Netflix Animation is https://studio.pcs.flxvpn.net/anim
- hrc: Reserved for full-time employees and contingent workers with a Netflix email account connecting from a high-risk country. Netflix internal applications can’t be accessed while using this endpoint. For authentication, use your Active Directory credentials.
Endpoint Servers and Locations
| Location | Purpose | Login URL |
| Global | Global login for Netflix Full-Time Employees (FTEs) | https://pcs.flxvpn.net/emp |
| Global | Global login for Netflix FTEs with dedicated split-tunnel profile | https://pcs.flxvpn.net/emp-split |
| Global | Global login for Netflix contingent workers | https://pcs.flxvpn.net/contractors |
| Global | Global login for Netflix contingent workers with dedicated split-tunnel profile | https://pcs.flxvpn.net/contractors-split |
Animation
| Location | Type | Name | Login URL |
| Global | Policy Secure (UAC) | Animation w/ split tunnel | https://studio.pcs.flxvpn.net/anim |
| Global | Policy Secure (UAC) | Animation w/ full tunnel | https://studio.pcs.flxvpn.net/anim-full |
| LAX009 | Policy Secure (UAC) | Animation w/ split tunnel | ttps://lax009.pcs.flxvpn.net/anim |
| LAX009 | Policy Secure (UAC) | Animation w/ full tunnel | https://lax009.pcs.flxvpn.net/anim-full |
| NYC005 | Policy Secure (UAC) | Animation w/ split tunnel | https://nyc005.pcs.flxvpn.net/anim |
| NYC005 | Policy Secure (UAC) | Animation w/ full tunnel | https://nyc005.pcs.flxvpn.net/anim-full |
| WAS001 | Policy Secure (UAC) | Animation w/ split tunnel | https://was001.pcs.flxvpn.net/anim |
| WAS001 | Policy Secure (UAC) | Animation w/ full tunnel | https://was001.pcs.flxvpn.net/anim-full |
Contingent Workers
| Location | Purpose | Login URL |
| Los Angeles, CA (LAX009) | For UCAN contingent workers | http://lax009.pcs.flxvpn.net/contractors |
| San Jose, CA (SJC005) | For UCAN contingent workers | http://sjc005.pcs.flxvpn.net/contractors |
| New York, NY | For UCAN contingent workers | https://nyc005.pcs.flxvpn.net/contractors |
| Washington, DC | For UCAN contingent workers | https://was001.pcs.flxvpn.net/contractors |
| Singapore | For APAC contingent workers | https://sin001.pcs.flxvpn.net/contractors |
| Amsterdam | For EMEA contingent workers | https://ams001.pcs.flxvpn.net/contractors |
| London | For EMEA contingent workers | https://lhr005.pcs.flxvpn.net/contractors |
APAC (FTEs)
| Location | Purpose | Login URL |
| Singapore | Site-specific login for Netflix FTEs | https://sin001.pcs.flxvpn.net/emp |
| Singapore |
Site-specific login for Netflix FTEs dedicated split tunnel profile |
https://sin001.pcs.flxvpn.net/emp-split |
EMEA (FTEs)
| Location | Purpose | Login URL |
| Amsterdam, The Netherlands | Site-specific login for Netflix FTEs | https://ams001.pcs.flxvpn.net/emp |
| Amsterdam, The Netherlands |
Site-specific login for Netflix FTEs Dedicated split tunnel profile |
https://ams001.pcs.flxvpn.net/emp-split |
| Slough, Berkshire, United Kingdom | Site-specific login for Netflix FTEs | https://lhr005.pcs.flxvpn.net/emp |
| Slough, Berkshire, United Kingdom |
Site-specific login for Netflix FTEs
Dedicated split tunnel profile |
https://lhr005.pcs.flxvpn.net/emp-split |
UCAN (FTEs)
| Location | Purpose | Login URL |
| San Jose, CA (SJC005) | Site-specific login for Netflix FTEs | https://sjc005.pcs.flxvpn.net/emp |
| San Jose, CA (SJC005) |
Site-specific login for Netflix FTEs Dedicated split tunnel profile |
https://sjc005.pcs.flxvpn.net/emp-split |
| Los Angeles, CA (LAX009) | Site-specific login for Netflix FTEs | https://lax009.pcs.flxvpn.net/emp |
| Los Angeles, CA (LAX009) |
Site-specific login for Netflix FTEs Dedicated split tunnel profile |
https://lax009.pcs.flxvpn.net/emp-split |
| Washington, DC | Site-specific login for Netflix FTEs | https://was001.pcs.flxvpn.net/emp |
| Washington, DC |
Site-specific login for Netflix FTEs Dedicated split tunnel profile |
https://was001.pcs.flxvpn.net/emp-split |
| New York, NY | Site-specific login for Netflix FTEs | https://nyc005.pcs.flxvpn.net/emp |
| New York, NY |
Site-specific login for Netflix FTEs Dedicated split tunnel profile |
https://nyc005.pcs.flxvpn.net/emp-split |
Emergency Endpoints (FTEs)
In case of emergency (ICE) endpoints are used when Meechum has a service interruption. Use them sparingly. Before adding an ICE endpoint, reach out to askntech@netflix.com or #ntech-help in Slack to be added to gssg-app-icevpn@netflix.com.
| Location | Purpose | Login URL |
| Global | Global login for Netflix FTEs | https://pcs.flxvpn.net/ice |
| San Jose, CA (SJC005) | Site-specific login for Netflix FTEs | https://sjc005.pcs.flxvpn.net/ice |
| Los Angeles, CA (LAX009) | Site-specific login for Netflix FTEs | https://lax009.pcs.flxvpn.net/ice |
| Washington, DC | Site-specific login for Netflix FTEs | https://was001.pcs.flxvpn.net/ice |
| New York, NY | Site-specific login for Netflix FTEs | https://nyc005.pcs.flxvpn.net/ice |
| Amsterdam, The Netherlands | Site-specific login for Netflix FTEs | https://ams001.pcs.flxvpn.net/ice |
| Slough, Berkshire, United Kingdom | Site-specific login for Netflix FTEs | https://lhr005.pcs.flxvpn.net/ice |
| Singapore | Site-specific login for Netflix FTEs | https://sin001.pcs.flxvpn.net/ice |
Add additional Endpoints
- Open Ivanti Secure Access.
- Select the + icon next to Connections on Windows, Ubuntu, ChromeOS, and mobile or at the bottom-left corner on macOS.
- In the Name field, enter a name for the connection.
- In the Server URL, enter the URL for the endpoint.
- Select Add.
- Select Connect next to the newly added endpoint.
| Agent facing Article |
Troubleshoot VPN Connection or Access Issues
This guide provides a structured workflow to troubleshoot and resolve the most common issues with the Netflix VPN. Following these steps will help you quickly categorize a user's problem and apply the correct fix.
Quick Triage with the Decision Tree
Start by obtaining information about the user’s hardware and network connections by using tools like go.netflix.com/oomnitza and VPN and Wi-Fi Metrics Installation for macOS and Windows to determine which troubleshooting path to follow.
- What is the OS version? If not up-to-date, guide the user to update their operating system (found in Oomnitza).
- What is the user’s location (home or public Wi-Fi)? (Potentially found in Oomnitza)
-
What is the Ivanti client version? (Use VPN Metrics.)
- In the Ivanti Secure Access Client, confirm the current endpoint and connection status.
-
Verify the time and date of the laptop is accurate.
- Navigate to Settings, Time & Language, Date & Time.
- In the Date & Time window, verify Set Time Automatically is On.
- What is the current uptime? (Ask user.)
- If the status is Disconnected or it fails during connection with an error, go to the Fixing Connection and Authentication Failures section of this article.
- If the status is Connected, but the user cannot access websites or internal tools, go to the Fixing “Connected but No Access” Errors section of this article.
- If they report the client is crashing, or their computer becomes very slow when connected, go to the Investigating Performance and Client Issues section of this article.
Fixing Connection and Authentication Failures
Use these steps when the Ivanti client will not establish a successful connection.
Check Basic Internet Connectivity (Get Network Diagnostics Logs for Windows and macOS)#
The VPN requires a working internet connection. Ask them to open a web browser and navigate to a public site like netflix.com. If they cannot, they must resolve their local internet issue first.
If they have an internet connection, run a quick network path test from their machine:
- On macOS: Open Terminal and run ping -c 10 pcs.flxvpn.net
- On Windows: Open Command Prompt and run ping pcs.flxvpn.net -n 10 If this test fails, run these commands to test the Domain Name System (DNS):
- On macOS: Open Terminal and run ping -c 10 8.8.8.8
- On Windows: Open Command Prompt and run ping 8.8.8.8 -n
If these steps fail here, go to the Troubleshoot DNS section of this article.
Check Authentication
Authentication failures are common and often simple to fix.
-
Confirm the user is entering their intended Okta credentials.
- If user is still on Duo Mobile, ask them to select the option Send Duo Push.
- Have them attempt a password reset if they are unsure.
- Confirm their MFA method is working correctly and they are approving the prompt.
- Check for any known Okta or SSO (Single Sign On) outages.
Fixing “Connected but No Access” Errors
Use these steps when the client shows "Connected" but network resources are unreachable.
Troubleshoot DNS
A Domain Name System (DNS) issue is the most common cause of this problem. Flushing the device's DNS cache forces it to get fresh records.
-
On macOS:
- Open Terminal.
- Run the command: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
-
On Windows:
- Open Command Prompt as an Administrator.
- Run the command: ipconfig /flushdns
After flushing, test name resolution by running nslookup <internal_resource> (for example, nslookup jira.prod.netflix.net).
Troubleshoot Routing
Verify the user’s computer is sending traffic through the VPN tunnel.
- On macOS: Open Terminal and run netstat -nr | grep utun
- On Windows: Open Command Prompt and run route print
The output should show routes for internal Netflix networks pointing to the VPN interface.
Disable Private Relay (macOS)
A common issue on macOS is Apple's iCloud Private Relay feature, which can interfere with the VPN's split-tunneling configuration.
- Open System Settings.
- Select your Apple ID.
- Select iCloud, then Private Relay.
Verify this feature is turned Off.
Investigating Performance and Client Issues
Address issues like client crashes or severe system slowdowns.
-
Check for High Resource Usage
-
Guide the user to check if the VPN client is using an excessive amount of system resources.
- On macOS: Open Activity Monitor and sort by % CPU and Memory.
- On Windows: Open Task Manager and view the Processes tab.
- If the Ivanti or Pulse Secure process consistently is at the top, note this trend for escalation.
-
Guide the user to check if the VPN client is using an excessive amount of system resources.
-
Perform a Client Reset
-
The client software can enter a bad state. Using the reset tool can resolve this state without a full reinstall.
- Instruct the client to run the Ivanti Reset Tool from their applications.
- Alternatively, guide them to manually stop and restart the VPN service on their machine.
-
The client software can enter a bad state. Using the reset tool can resolve this state without a full reinstall.
-
Reinstall the Ivanti Client
- If the client is unstable or crashing, a clean reinstallation is the final troubleshooting step. Guide them to fully uninstall the Ivanti Secure Access Client, reboot their machine, and then install the latest version.
Log Capture and Escalation
If you cannot resolve the issue after following all relevant steps, you must escalate to the Infrastructure Network Engineering (INE) team with a complete set of diagnostic logs.
Comprehensive Log Capture#
Provide the user with detailed, step-by-step instructions to use the Ivanti client's built-in diagnostic tool to collect and export the logs. On macOS, this process will involve using the get-networkdiaglogs tool that is found in the Managed Software Center if not installed. If installed, it can be found in the list of applications.
What to Attach When Escalating
Your escalation ticket must be complete to receive a fast response. Include this information:
- Summary of issue: Categorize the problem (connection, authentication, access, or performance).
- Troubleshooting performed: A list of all the steps from this guide you have already taken
- Log bundle or command outputs: For Windows and macOS, run the Get Network Diagnostics tool and have the user share the log files. Any other OS, send the text output from any ping, traceroute, or nslookup commands you ran.
- Environment details: Visit go.netflix.com/oomnitza and provide the device operating system and the exact Ivanti client version number.
Comments
0 comments
Please sign in to leave a comment.