How to Connect FortiClient VPN to Your Work Network
Your FortiClient screen may look different from a coworker’s. What you can see and edit can depend on how the device is managed. Use your organization’s setup instructions and record what happens before sign-in, during authentication, and when opening the first internal resource.
About 3 min read
Confirm the profile your employer issued
Ask IT where to obtain the client, which version the organization supports, and how it assigns your VPN profile. Fortinet’s documentation distinguishes connections provisioned through EMS from locally configured ones. An administrator can hide Remote Access or restrict editing. If the company entry is missing, check device enrollment and profile delivery with IT.
The available connection modes depend on the client and gateway versions. Fortinet’s documentation says FortiOS 7.6.3 and later no longer support SSL VPN tunnel mode. If your organization has moved to IPsec or another mode, use the new instructions supplied by IT.
Sign in and open a designated test resource
- 01Launch the approved client and choose the profile issued by IT. Check that it isn’t an older profile with a similar name.
- 02Follow the company’s sign-in flow. It might use an enterprise account, MFA, browser-based single sign-on, or a certificate.
- 03Once the client reports a connection, open an internal resource designated by IT.
- 04Record whether the resource opens. Follow your organization’s instructions for ending or maintaining the VPN session.
If sign-in opens a browser, watch for the return to the client. A loop back to the sign-in page is useful evidence for IT. Record the time and exact prompt instead of repeatedly submitting codes.
Use the symptom to choose what to verify
| Symptom | Next check |
|---|---|
| Remote Access or the corporate profile is missing | Ask IT to verify the client version, device enrollment, and EMS policy |
| The profile appears but authentication fails | Record the account type and exact error, and confirm the organization’s approved entry point |
| The client connects but the target resource won’t open | Record the app, time, and whether a second approved resource works so IT can check policy and routing |
Pause if a certificate or device-compliance warning appears. Ask the administrator to review it with the device’s protections enabled.
Give IT a report it can act on
Include the OS, client version, profile name, network type, time zone, exact message, and result from a second approved resource. For example, “The Windows client reported Connected at 10:20 Beijing time. The ticketing app timed out, while the designated intranet test page loaded.” That gives the team a specific resource and time to investigate.
Frequently asked questions
Why can a coworker add profiles while I can’t?
EMS can control feature visibility and personal VPN configurations. Ask IT what policy applies to your device.
Should I start by checking my public IP?
Verify the authorized work resource first. Public IP changes depend on the organization’s routing policy.