Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About AdminTS
AdminTS
Just browsing
Member since May 28, 2024
9 hours ago
Community Record
10
Posts
0
Kudos
0
Solutions
Badges
12 hours ago
I was finally able to solve the problem. I'd be happy to tell you how I finally managed to do it. We have several WLAN networks and some of them were set up with VLAN tagging and not as bridged, but tunneled to a concentrator. We had to set this up so that all devices received the correct IP addresses. We briefly deleted this configuration and then undid it. Since then, we have also been able to establish a VPN connection. Everything works as it should. However, the VPN connection does not work on the smartphone. No matter whether with Cisco AnyConnect or Android's own VPN solution. I'm still in the dark at the moment.
... View more
May 28 2024
8:10 AM
I have deactivated the Windows firewall or the antivirus and nothing has changed.
... View more
May 28 2024
8:03 AM
No, unfortunately I don't see any records regarding VPN on the MX. This means that the connection does not even reach the MX. But because all clients cannot connect, the problem must not be with the clients or the MX. But I can't imagine there being a problem with the ISP router either.
... View more
May 28 2024
7:32 AM
I have also often read that Windows updates can lead to problems. Then I wasn't imagining it because of the ports. It wouldn't make much sense to open ports for Ipsec anyway. We can't set port forwarding on the ISP router, as it no longer operates as a router, but only forwards the Internet (bridge mode).
... View more
May 28 2024
6:57 AM
Even if you set up a VPN connection again with Powershell, it will not solve the problem. At least I am convinced that it will. In the end, it depends on the same thing whether you add the VPN manually or with Powershell.
... View more
May 28 2024
6:44 AM
Unfortunately, I cannot say how to deal with Powershell. I don't have enough experience. However, we have deleted and recreated the VPN that we set up under Windows several times. We assume that there is no error there.
... View more
May 28 2024
6:13 AM
I have already tested whether other clients also have problems with VPN. We can't connect to other clients either. So it can't be due to the clients.
... View more
May 28 2024
5:38 AM
We have set up the client VPN connection in MX64. No connection seems to be established with several clients. We have learned that the ports UDP 500 and UDP 4500 must be released. In the input rules in Layer 3, the two ports have been released (but when we check the ports, they are still considered closed). Our Internet router is running in bridge mode, just for information. We noticed that the VPN connection or no attempts arrive on the MX, which means that it must be due to the clients or do you agree? We therefore don't think that we need to make any further adjustments to the firewall. Although we have also enabled the ports in the clients, nothing else happens. Error 789 keeps appearing in the events in Windows. We can safely rule out the possibility of an input error. We have also tried to set up port forwarding for both ports in the MX. However, we cannot enter or save the public IP address of the MX as the destination. A message appears stating that this IP address has not been configured as a subnet. Are we making a mistake in the whole thing?
... View more
Labels:
- Labels:
-
Client VPN
-
Firewall
© 2024 Cisco Systems, Inc.
