Hi, the subject explains everything.
This morning I installed the newest update. Since then noone can start a vpn-connection. Me neither - and I am sure, that my logon is correct. And the others can't be all wrong also.
Everything else works, and in the office I can logon as administrator - everything looks fine.
The LDAP-Server is running, and hasn't been changed at all, not even rebootet.
I rebootet the FortiGate again, just in case - didn't help.
We use FortiTokens, but it is not asking for the token - already a problem with the logon.
Any Ideas?
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hello,
Could you please have a look at this discussion?:
Regards,
Hello,
Could you please have a look at this discussion?:
Regards,
Hi @TZ1
Are you using LDAPs port 636 on your FGT or plain ldap port 389?
If yes maybe this KB will help.
If not try to run the below debug commands on FGT CLI:
diag debug cons time enable
diag debug application fnbamd -1
diag debug application sslvpn -1
diag debug enable
Hi, It is 636.
In Name - Servername - IP/Name - IP-address.
Looks good so far, but if I activate Server Identity Check it looses contact to the server.
The server identity check option is used when enable/disable against its certificate and subject alternative name(s).
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1633 | |
1063 | |
751 | |
443 | |
210 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.