Navigation

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

    [SOLVED] Can't connect to Web Config

    Installation and Upgrades
    2
    3
    471
    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.
    • K
      KalanVryce last edited by

      Fresh load on an older HP P4 SFF box.
      WAN: On-Board Broadcom Gigabit NIC
      LAN: PCI Realtek Gigabit NIC

      WAN connected to current network just for configuring getting IPv4 192.168.5.116
      Laptop (Macbook Pro) connected directly to the LAN NIC getting IPv4 192.168.1.100 can't ping the gateway, can't ping/browse external sites.  I tried a second machine (Win10) gets IPv4 192.168.1.101 still no internal/external connectivity.  Tried Chrome, Firefox in both MacOS and Windows, tried Safari on MacOS and Edge in Windows and also Disabled AV and Firewalls.

      I can ping out from the pfSense console without issue I have reset interfaces, restarted webConfigurator, restarted the machine, reloaded the machine tried disabling checksum offloading from this other thread ( https://forum.pfsense.org/index.php?topic=80891.msg447139#msg447139 ) however as the NIC restarts they are turned back on.

      1 Reply Last reply Reply Quote 0
      • K
        KalanVryce last edited by

        Ok…. so just as an FYI if anyone else has this issue I was able to resolve it by choosing the "Reset to factory defaults" option a fresh install and several reloads didn't resolve it but out of curiosity I gave it a try and it worked... why I don't know but perhaps a bug in 2.3.2 ISO?

        1 Reply Last reply Reply Quote 0
        • D
          dsp3 last edited by

          @KalanVryce:

          Ok…. so just as an FYI if anyone else has this issue I was able to resolve it by choosing the "Reset to factory defaults" option a fresh install and several reloads didn't resolve it but out of curiosity I gave it a try and it worked... why I don't know but perhaps a bug in 2.3.2 ISO?

          It didn't work for me. Exact same issue. Reset to factory gives same result, but thanks for sharing!

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