Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Fortclient not connecting over PfSense

    Scheduled Pinned Locked Moved
    Firewalling
    4
    18
    1.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      phoenixfsense @michmoor
      last edited by

      @michmoor
      All the webiste and protocol's works fine.
      I can access the internet without a problem, even now as we speak i am going through the FW.

      Its just the forticlient that doesnt connect.

      M 1 Reply Last reply Reply Quote 0
      • M
        michmoor LAYER 8 Rebel Alliance @phoenixfsense
        last edited by

        @phoenixfsense what error are you getting in the forticlient logs?

        Firewall: NetGate,Palo Alto-VM,Juniper SRX
        Routing: Juniper, Arista, Cisco
        Switching: Juniper, Arista, Cisco
        Wireless: Unifi, Aruba IAP
        JNCIP,CCNP Enterprise

        P 1 Reply Last reply Reply Quote 0
        • P
          phoenixfsense @michmoor
          last edited by

          @michmoor

          When its not Connect..
          08/9/2023 6:05:16 PM Notice VPN id=96566 msg="negotiation information, loc_ip=192.168.88.10 loc_port=500 rem_ip=x.x.x.x rem_port=500 out_if=0 vpn_tunnel=Llo action=negotiate init=local mode=aggressive stage=1 dir=outbound status=success Initiator: sent x.x.x.x aggressive mode message #1 (OK)" vpntunnel=Llo vpntype=ipsec
          8/9/2023 6:05:28 PM Warning VPN id=96561 msg="locip=192.168.88.10 locport=500 remip=x.x.X remport=500 outif=0 vpntunnel=Lit status=negotiate_error No response from the peer, phase1 retransmit reaches maximum count..." vpntunnel=Llo vpntype=ipsec

          when its connecting
          8/9/2023 6:15:14 PM Notice VPN id=96566 msg="negotiation information, loc_ip=192.168.0.102 loc_port=4500 rem_ip=x.x.x.x rem_port=4500 out_if=0 vpn_tunnel=Lol action=negotiate init=local mode=aggressive stage=2 dir=outbound status=success Initiator: sent x.x.x.x aggressive mode message #2 (DONE)" vpntunnel=Lol vpntype=ipsec
          8/9/2023 6:15:14 PM Notice VPN id=96566 msg="negotiation information, loc_ip=192.168.0.102 loc_port=4500 rem_ip=x.x.x.x rem_port=4500 out_if=0 vpn_tunnel=Lol action=negotiate init=remote mode=xauth_client stage=0 dir=inbound status=success Responder: parsed x.x.x.x xauth_client mode message #0 " vpntunnel=Lol vpntype=ipsec
          8/9/2023 6:15:14 PM Notice VPN id=96566 msg="negotiation information, loc_ip=192.168.0.102 loc_port=4500 rem_ip=x.x.x.x rem_port=4500 out_if=0 vpn_tunnel=Lol action=negotiate init=remote mode=xauth_client stage=2 dir=inbound status=success Responder: parsed x.x.x.x xauth_client mode message #2 " vpntunnel=Lol vpntype=ipsec
          8/9/2023 6:15:14 PM Notice VPN id=96566 msg="negotiation information, loc_ip=192.168.0.102 loc_port=4500 rem_ip=x.x.x.x rem_port=4500 out_if=0 vpn_tunnel=Lol action=negotiate init=local mode=xauth_client stage=0 dir=inbound status=success Initiator: parsed x.x.x.x xauth_client mode message #0 (" vpntunnel=Lol vpntype=ipsec
          8/9/2023 6:15:14 PM Notice VPN id=96566 msg="negotiation information, loc_ip=192.168.0.102 loc_port=4500 rem_ip=x.x.x.x rem_port=4500 out_if=0 vpn_tunnel=Lol action=negotiate init=remote mode=xauth_client stage=0 dir=inbound status=success Responder: parsed x.x.x.x xauth_client mode message #0 " vpntunnel=Lol vpntype=ipsec
          8/9/2023 6:15:15 PM Notice VPN id=96566 msg="negotiation information, loc_ip=192.168.0.102 loc_port=4500 rem_ip=x.x.x.x rem_port=4500 out_if=0 vpn_tunnel=Lol action=negotiate init=local mode=quick stage=1 dir=outbound status=success Initiator: sent x.x.x.x quick mode message #1 (OK)" vpntunnel=Lol vpntype=ipsec
          8/9/2023 6:15:15 PM Notice VPN id=96571 msg="locip=192.168.0.102 locport=4500 remip=x.x.x.x remport=4500 outif=0 vpntunnel=Lol action=install_sa, inspi=0x9e4976ec outspi=0x5e53ced5 Initiator: tunnel 192.168.0.102/x.x.x.x install ipsec sa" vpntunnel=Lol vpntype=ipsec
          8/9/2023 6:15:15 PM Notice VPN id=96566 msg="negotiation information, loc_ip=192.168.0.102 loc_port=4500 rem_ip=x.x.x.x rem_port=4500 out_if=0 vpn_tunnel=Lol action=negotiate init=local mode=quick stage=2 dir=outbound status=success Initiator: sent x.x.x.x quick mode message #2 (DONE)" vpntunnel=Lol vpntype=ipsec
          8/9/2023 6:15:15 PM Notice VPN id=96560 msg="VPN tunnel status" vpnstate=connected vpntype=ipsec
          8/9/2023 6:15:16 PM Notice VPN date=2023-08-09 time=18:15:15 logver=1 type=traffic level=notice sessionid=40084692 hostname=ID1 pcdomain= uid=766A3C7F9C0B464492A0A267D11DBB90 devid=FCT8003202609364 fgtserial=N/A emsserial=N/A regip=N/A srcname=ipsec srcproduct=N/A srcip=10.64.96.34 srcport=N/A direction=outbound dstip=x.x.x.x remotename=N/A dstport=4500 user=User1 proto=6 rcvdbyte=N/A sentbyte=13056 utmaction=passthrough utmevent=vpn threat=connect vd=N/A fctver=5.4.2.0860 os="Microsoft Windows 10 Enterprise Edition, 64-bit (build 22621)" usingpolicy="" service= url=N/A userinitiated=0 browsetime=N/A

          I tried allowing port 4500 but still the same results

          V M 2 Replies Last reply Reply Quote 0
          • V
            viragomann @phoenixfsense
            last edited by

            @phoenixfsense
            These log seem to be from different devices.

            Did you any mess with the outbound NAT on pfSense?

            P 1 Reply Last reply Reply Quote 0
            • M
              michmoor LAYER 8 Rebel Alliance @phoenixfsense
              last edited by

              @phoenixfsense Im not really seeing a problem. The 192.168.0.102 device connected fine.
              Your 192.168.88.10 seems to have trouble.
              Thats on a separate VLAN? If so does that any the same access rules as 192.168.0.102

              This is why i asked you to review the firewall rules. Something is clearly different here in your setup.

              Firewall: NetGate,Palo Alto-VM,Juniper SRX
              Routing: Juniper, Arista, Cisco
              Switching: Juniper, Arista, Cisco
              Wireless: Unifi, Aruba IAP
              JNCIP,CCNP Enterprise

              1 Reply Last reply Reply Quote 0
              • P
                phoenixfsense @viragomann
                last edited by

                @viragomann

                Ok Its the same device- the reason why you see two defirent IP address is because I have to bypass the Pfsense or use a mobile router.

                Outbound NAT : Mode Automatic

                V 1 Reply Last reply Reply Quote 0
                • V
                  viragomann @phoenixfsense
                  last edited by

                  @phoenixfsense
                  I expect that the IPSec client use port 4500 for NAT traversal.
                  So I'm wondering, why the not working log shows port 500, but the working shows 4500.

                  1 Reply Last reply Reply Quote 0
                  • M
                    michmoor LAYER 8 Rebel Alliance
                    last edited by

                    Just curious but if you do a WAN side packet capture do you see packets going to your companys vpn gateway?
                    If so there is something they are seeing and not liking.
                    Unfortunately the logs on the client arent very verbose.

                    Firewall: NetGate,Palo Alto-VM,Juniper SRX
                    Routing: Juniper, Arista, Cisco
                    Switching: Juniper, Arista, Cisco
                    Wireless: Unifi, Aruba IAP
                    JNCIP,CCNP Enterprise

                    P 1 Reply Last reply Reply Quote 0
                    • P
                      phoenixfsense @michmoor
                      last edited by

                      @michmoor
                      If that is the case then it would mean that the issue is on the pfsense.
                      This is easy to believe because both my 5G and Mobile LTE are on the same provider.

                      F 1 Reply Last reply Reply Quote 0
                      • F
                        fallmtl67 @phoenixfsense
                        last edited by

                        @phoenixfsense I know it's been a while but I'm experiencing the same issue. I was wondering if you were ever able to resolve the issue and what you did? Thanks.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post