Testing Guide for VPN Requirement#
Testing period: October 22, 2026– January 11, 2027
VPN access requirement begins: January 11, 2027
Northwestern IT is preparing to update access requirements to improve basic security measures for Quest, the university’s high-performance computing service. Similarly to several Northwestern services, including the Quest Analytics Nodes and Quest OnDemand, all Quest users will be required to use Northwestern GlobalProtect VPN to connect to Quest login nodes while off-campus beginning January 11, 2027. Users who are on the Northwestern campus network (excluding Guest Wi-Fi) or Northwestern Medicine network will continue to be able to access login nodes without connecting to VPN separately.
The change is not expected to have a large impact on most users. However, the following are example workflows that may be affected:
Off-campus servers and lab workstations: Scripts or services running on a lab computer, instrument, or server located outside the campus network that transfer data to Quest automatically
Off-campus tools and dashboards: Tools or dashboards that connect to Quest from off-campus without a person actively controlling them
Processes running over an extended period on off-campus servers: Processes that start while connected to VPN but later need to reconnect, copy files, monitor jobs, or retrieve results after the VPN connection has dropped
External collaborators: External users who need to connect to Quest but may not be able to obtain access to the Northwestern GlobalProtect VPN
By testing before the change, you can find out whether the VPN requirement affects your usual way of working with Quest and make any needed adjustments in advance.
See the Northwestern GlobalProtect VPN documentation for instructions on installing and using the VPN.
Once installed, connect to GlobalProtect using your Net ID and password before starting any Quest session. If you have questions about VPN setup itself (as opposed to Quest access), contact consultant@northwestern.edu .
How to test your workflows#
Connect to the Northwestern GlobalProtect VPN from the same location and device you normally use when working off campus.
Run your usual Quest workflow from start to finish. Include any steps for logging in, transferring files, submitting jobs, using interactive tools, monitoring job status, and retrieving results.
Repeat the workflow but intentionally disconnect from the VPN partway through a representative step, such as during a file transfer, while using an interactive session, after submitting a job, or while monitoring output. Because GlobalProtect VPN sessions have a 16-hour time limit, also test any workflow that may run longer than a single VPN session.
Reconnect to the VPN and check whether the workflow can resume or be restarted cleanly.
Record what you tested, what worked, what failed, and any error messages or unexpected behavior you observed.
Report any issues you encountered to the Quest support team at quest-help@northwestern.edu with a description of your workflow tests and results.
Example workflows to consider testing with the GlobalProtect VPN#
SSH, SCP, SFTP, rsync, or other command-line connections to Quest login nodes from off campus
Scheduled or unattended file transfers between Quest and external systems, lab computers, instruments, cloud storage, or personal workstations that are outside the campus network.
Long-running transfers to or from Quest login nodes that may be affected by VPN timeouts or network interruptions
Automated scripts, tools, or dashboards that connect to Quest from off campus
What to look for during testing#
Whether you can connect to Quest successfully while on VPN
Whether file transfers complete, pause, fail, or need to be restarted after a VPN interruption
Whether scripts or automated tools fail because they cannot establish or re-establish a connection
Whether performance, latency, or connection stability changes noticeably while using VPN
Reporting issues#
If you encounter problems while testing, please contact the Quest support team at quest-help@northwestern.edu with a description of the workflow and what went wrong.