The AT&T Global Network Client (AGNC) enables highly secured mobile access to corporate networks through AT&T Mobile Remote Access VPN Services (ANIRA and AVTS) and access to AT&T Wi-Fi hotspots all over the world from your Android device.
PLEASE NOTE: You must have AT&T Mobile Remote Access Service, either VPN or Wi-Fi, to use this application. Please contact your company's IT department for information about VPN access and for your login credentials. For new AT&T Mobile Remote Access Service (MRAS), VPN and/or Wi-Fi, please contact your AT&T Sales Representative.
The AT&T Global Network Client for Android supports establishing a VPN connection to the AT&T Network Based IPSEC Remote Access (ANIRA) service, as well as the AT&T VPN Tunneling Service (AVTS) to an AT&T SIG with any Android device running Android 4.0 or later using the AT&T managed VPN SSL-T service option.
The AT&T Global Network Client for Android can also establish VPN connections using IPSEC to ANIRA, AVTS to a SIG, and AVTS to an AT&T managed Cisco VPN gateway using any of the following AT&T devices. Other carriers' devices may not support VPN capability due to differences in their implementations of the Android operating system.
• Samsung Galaxy Express
• Samsung Galaxy S III (Android 4.1)
• Samsung Note II (Android 4.1)
• Samsung Galaxy Rugby Pro
• Samsung Galaxy Tab 2
• Samsung Galaxy S 4
• LG Optimus G
• LG Optimus G Pro
• LG Nitro™
• LG Escape™
• MOTOROLA ATRIX™ 2
• MOTOROLA ATRIX™ HD
• NEC Vigor
• Pantech Discover
AT&T Mobile Remote Access Services Wi-Fi capabilities are compatible with all Android 3.1 and later devices.
The AT&T Global Network (AGN) Client also includes a searchable directory of AT&T hotspots in the US and over 80 countries worldwide and a map locator of nearby AT&T hotspots.
Please see the AT&T Global Network Client (netclient) web site at http://www.corp.att.com/agnc/android/ for documentation and additional details on client usage, setup and configuration.
Fix for POODLE SSL vulnerability (force SSL-T VPN to use TLSv1 instead of SSLv3)