Show:
VPN for Onboarding
Gear
AnyConnect
Access
100

Do we send contractors an AnyConnect installer?

Template:

After receiving your network credentials, please use the following link to open Outlook Web Access and retrieve your VPN login instructions.

https://mail.viasat.com

If VPN access was requested on your behalf and if it has been setup, you will have a message in your inbox with login instructions.

Please contact the IT Service Desk if you have any questions or issues do not reply to this email.

100

Questions if reporter says jumpboxes don't work..

1. Ping test to validate

2. Check to see if they are powered on... this would go to desktop if power is off

100

Unable to connect to VPN - cert validation error.

This error is due to the users laptop/desktop not having the correct Viasat issues machine certificate. We see these more often with FOUO users. This issue can also because on Mac books by the certificate not being trusted.

  1. For Windows computers verify computer in the proper workstation group in ARS. ("FOUO Workstations" for FOUO users and "Workstations" for all corporate VPN users.
  2. If Macbooks make sure they are enrolled in JAMF/JSS. Manual enrollment in JSS/JAMF
100

Flash won't work on my VPN - please help!

Flash is EOL and will not be supported ...

200

What is allowed by default on new contractor VPN?

The following services/applications are allowed by default on all new partner VPNs, and and all additional access is added on an approval (POC and security) basis:

  • Viasat E-Mail (webmail and/or outlook)

  • Slack

  • DNS

  • Jabber

  • SSO

  • Internet access

200

Can't connect to VPN (connection issues)

This error is typically caused by the users ISP DNS servers not returning the correct VPN node. More information can be found here: How GSLB/Route 53 Works and Potential Issues

  1. Have the user perform a nslookup for the vpn server they are connecting. If working correctly it should return the VPN closest to the geographically.
    1. Corporate VPN: harrier.viasat.com
    2. FOUO VPN: osprey.viasat.com
    3. Data Center VPN: pandion.viasat.com
    4. Partner VPN: hawk.viasat.com
  2. Have the user change their DNS server to google DNS  (8.8.8.8)
  3. Have the user install the multi-node AnyConnect client and manually select what VPN they want to connect to. How the Multinode VPN Profiles works and Installation Instructions
200

Access to MACH3 VPN

Route for approval

Provide profile information

https://wiki.viasat.com/display/IT/Data+Center+VPN+Information


300

Where to find Partner VPN information?

https://wiki.viasat.com/display/ITEUPNET/Partner+VPN+Info+and+Access+Request+Form


300

How to get multi-node VPN and why this may help?

The Multinode VPN is embedded in all new AnyConnect Apps and available in (Windows) Software Center or (Mac) Self Service, both available offline, off VPN. 

The Multinode profile is by default, in Software Center/Self Service, part of the general AnyConnect App, for Windows and Mac, start with the AnyConnect Uninstall App, then once complete do a fresh Install of the AnyConnect App. 

The Uninstall/Install process takes 4-5 minutes off the VPN

Helps due to connecting to a node that is closest geographically to the end user or by allowing them to choose another node if they have difficulties or IT has an outage.

300

How do I get BAN VPN connection?

IT does not support BAN VPN

https://wiki.viasat.com/display/NSEng/Instructions+for+New+Users+-+BAN

For support on the BAN VPN you will need to reach out to the GSD Admins (more in the link) gsdadmins@viasat.com.

400

Error: Failed to load compliance module - help!

This error is typically caused by a corrupt file or improper uninstall/reinstall of the AnyConnect client.

  1. Have the user reboot and see if the problem is resolved.
  2. If a reboot does not fix the problem then a complete uninstall and reinstall of the AnyConnect is required. You will need to follow the exact steps here: How to properly uninstall Cisco AnyConnect
500

Error: "COA Initiated" - help!

We typical see this error on the Partner and Data Center VPNs.

  1. Partner VPN: This issue is caused by the DACL not getting pushed correctly. Assign case to EUPN.
  2. Data Center VPN: This is caused by the user not being the correct AD Group. Please verify they are in the proper AD group for the VPN they are trying to connect to. Data Center VPN's (DC VPN)