I ended up being escalated to the highest level of support engineer. Also as per comments on the same thread, I disabled TLS 1.0 and rebooted with no change. No change.Īs per this post here I checked for this update. I have verified the credentials, and I have disabled IPv6. If you look at the settings of the adapter in network and sharing center, you can see that the properties of the fortissl is “ISDN Channel Disconnected PPoP WAN Adapter”Īs per advice on this forum I have removed and reinstalled the VPN Client. On computers with this issue, if you go to device manager, you can see in the network devices there are several “WAN Miniports” and most of them have errors where the system could not load the drivers. While it is good to know this fixes it, I do not want to rampage around nuking machines just because the VPN wont connect.
One of the computers was local, and due to the urgency of that user’s situation, we ended up nuking and paving the computer, which fixed the issue. It should also be noted that some 100 other users running on 7 and 8 have no issues with this connection. This leads me to suspect the issue is with the computer, not the firewall or it’s configuration. All present the same behavior, and they are over a range of firmware versions. We have several firewalls of Fortigate’s, ranging from a 50D to an 80D. I can ping both the DNS name of the firewall and the IP. I have also used this user’s credentials on my own computer and it works just fine, so the issue is with the computer, not with the user account. These are known good credentials, and I have used other known good credentials of my own. When it does this, event viewer logs error 633 or error 631 (it seems to toggle between the two) and error 720.
When dialing into the VPN on a specific machine, it either hangs at 98% for a long time and then fails, or it says “connected” and then immediately “disconnected.” This issue has hit two machines running windows 8.1 圆4 with all updates as of Monday.
0 kommentar(er)
