Hi guys, Windows 11, I connect to vpn FortiClient 7.0.7.0345 but the route print output is apipa.
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.
These case was solved after Windows update.
If the client is stuck on APIPA than something is wrong with the DHCP server/scopes or the network you have configured for that VPN.
Hi Yimc,
You might need to run Packet capture using "Wireshark" or some other tools, to find whether the DHCP handshake process is completed or stuck at some point. Below are the four messages exchanged during this process.
1. Discover : Client broadcast to find available DHCP servers.
2. Offer: If the DHCP server is available, then it responds with available address and options.
3. Request: Client requests offered address.
4. Ack: Server acknowledges client's requests for address information.
regards,
Sheikh
hi Sheikh! Thanks to help me,
Is works in Windows 10! I will try wireshark, I didn't know it!
Assuming this is SSL-VPN (can you confirm?), I remember seeing the client default to APIPA when the IP to be assigned was in conflict with another interface's IP/subnet.
Can you please check what IP ranges the FortiGate is using to assign IPs to clients, and then verify that it doesn't overlap with the subnet of any other interface on that client?
My team did this, but the problem still exists.
I connect to the VPN, still get APIPA IP, I can't reach the machines via mstsc or ping.
About Wireshark , what you need to help me?
I don't think that wiresharking is particularly helpful in this case, as the IP is not assigned through DHCP (it's assigned through some HTTPS-like communication in SSL-VPN itself).
You may want to inspect your FortiClient's debug logs (switch to debug level) + FortiGate's sslvpn debug outputs, gathered while the issue is being reproduced.
If you have an EMS license, consider reaching out to TAC through a support ticket (provide the EMS serial number) for assistance.
These case was solved after Windows update.
Hello,
Having exactly the same issue since 5 months. Connection to Forticlient is successful, but the network adapter keep Apipa address. Tested exactly the same username and parameter on Windows 10, it work.
Forticlient have been uninstalled many times, network adapter disabled, Windows is up to date.
Forticlient VPN Version 7.2.4.0972
Windows 11 22H2 Build no 22621.3296
Thanks in advance for your help.
i have the same issue and condition, do you already have solved that problem?, may you share the solution. thanks for your help.
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 |
---|---|
1712 | |
1093 | |
752 | |
447 | |
231 |
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.