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

    Cannot log into 192.168.1.1

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    25 Posts 5 Posters 3.3k Views
    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.
    • W
      Waqar.UK
      last edited by

      Hello Kom,

      thanks for sticking with me. I tried a Linux live DVD and tried 192.168.1.1
      it got to the pfsense web gui. I have re-booted both pfsense box and my Windows desktop.
      Still no access to 192.168.1.1 from Windows (firefox, goggle chrome and IE-11).

      1 Reply Last reply Reply Quote 0
      • W
        Waqar.UK
        last edited by

        Microsoft Windows [Version 6.1.7601]
        Copyright (c) 2009 Microsoft Corporation. All rights reserved.

        C:\Windows\system32>ipconfig

        Windows IP Configuration

        Ethernet adapter Local Area Connection 2:

        Media State . . . . . . . . . . . : Media disconnected
        Connection-specific DNS Suffix . :

        Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix . : localdomain
        Link-local IPv6 Address . . . . . : removed for posting
        IPv4 Address. . . . . . . . . . . : 192.168.1.100
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1

        Tunnel adapter isatap.localdomain:

        Media State . . . . . . . . . . . : Media disconnected
        Connection-specific DNS Suffix . : localdomain

        Tunnel adapter removed for posting

        Media State . . . . . . . . . . . : Media disconnected
        Connection-specific DNS Suffix . :

        C:\Windows\system32>ping www.google.com

        Pinging www.google.com [216.58.204.68] with 32 bytes of data:
        General failure.
        Request timed out.
        Reply from 216.58.204.68: bytes=32 time=13ms TTL=55
        Reply from 216.58.204.68: bytes=32 time=11ms TTL=55

        Ping statistics for 216.58.204.68:
        Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
        Approximate round trip times in milli-seconds:
        Minimum = 11ms, Maximum = 13ms, Average = 12ms

        C:\Windows\system32>ping www.google.com

        Pinging www.google.com [216.58.204.68] with 32 bytes of data:
        Reply from 216.58.204.68: bytes=32 time=11ms TTL=55
        Reply from 216.58.204.68: bytes=32 time=12ms TTL=55
        Reply from 216.58.204.68: bytes=32 time=10ms TTL=55
        Reply from 216.58.204.68: bytes=32 time=10ms TTL=55

        Ping statistics for 216.58.204.68:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
        Minimum = 10ms, Maximum = 12ms, Average = 10ms

        C:\Windows\system32>ping www.sky.com

        Pinging e1264.g.akamaiedge.net [104.80.201.170] with 32 bytes of data:
        General failure.
        Reply from 104.80.201.170: bytes=32 time=22ms TTL=57
        Reply from 104.80.201.170: bytes=32 time=22ms TTL=57
        Reply from 104.80.201.170: bytes=32 time=19ms TTL=57

        Ping statistics for 104.80.201.170:
        Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
        Approximate round trip times in milli-seconds:
        Minimum = 19ms, Maximum = 22ms, Average = 21ms

        C:\Windows\system32>ping www.sky.com

        Pinging e1264.g.akamaiedge.net [104.80.201.170] with 32 bytes of data:
        Reply from 104.80.201.170: bytes=32 time=22ms TTL=57
        Reply from 104.80.201.170: bytes=32 time=21ms TTL=57
        Reply from 104.80.201.170: bytes=32 time=17ms TTL=57
        Reply from 104.80.201.170: bytes=32 time=18ms TTL=57

        Ping statistics for 104.80.201.170:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
        Minimum = 17ms, Maximum = 22ms, Average = 19ms

        C:\Windows\system32>ping www.pfsense.com

        Pinging www.pfsense.org [208.123.73.69] with 32 bytes of data:
        General failure.
        Reply from 208.123.73.69: bytes=32 time=126ms TTL=44
        Reply from 208.123.73.69: bytes=32 time=121ms TTL=44
        Reply from 208.123.73.69: bytes=32 time=119ms TTL=44

        Ping statistics for 208.123.73.69:
        Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
        Approximate round trip times in milli-seconds:
        Minimum = 119ms, Maximum = 126ms, Average = 122ms

        C:\Windows\system32>ping www.pfsense.com

        Pinging www.pfsense.org [208.123.73.69] with 32 bytes of data:
        Reply from 208.123.73.69: bytes=32 time=123ms TTL=44
        Reply from 208.123.73.69: bytes=32 time=129ms TTL=44
        Reply from 208.123.73.69: bytes=32 time=117ms TTL=44
        Reply from 208.123.73.69: bytes=32 time=120ms TTL=44

        Ping statistics for 208.123.73.69:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
        Minimum = 117ms, Maximum = 129ms, Average = 122ms

        C:\Windows\system32>ping www.virginmedia.com

        Pinging www.virginmedia.com [213.105.9.24] with 32 bytes of data:
        General failure.
        Reply from 213.105.9.24: bytes=32 time=23ms TTL=245
        Reply from 213.105.9.24: bytes=32 time=21ms TTL=245
        Reply from 213.105.9.24: bytes=32 time=29ms TTL=245

        Ping statistics for 213.105.9.24:
        Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
        Approximate round trip times in milli-seconds:
        Minimum = 21ms, Maximum = 29ms, Average = 24ms

        C:\Windows\system32>ping www.virginmedia.com

        Pinging www.virginmedia.com [213.105.9.24] with 32 bytes of data:
        Reply from 213.105.9.24: bytes=32 time=20ms TTL=245
        Reply from 213.105.9.24: bytes=32 time=23ms TTL=245
        Reply from 213.105.9.24: bytes=32 time=28ms TTL=245
        Reply from 213.105.9.24: bytes=32 time=21ms TTL=245

        Ping statistics for 213.105.9.24:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
        Minimum = 20ms, Maximum = 28ms, Average = 23ms

        C:\Windows\system32>

        1 Reply Last reply Reply Quote 0
        • KOMK
          KOM
          last edited by

          So bizarre. What packages do you have installed? Any IDS like snort or suricata that might have blocked you for some reason?

          1 Reply Last reply Reply Quote 0
          • W
            Waqar.UK
            last edited by

            No packages' have been installed. It is vanilla pfsense.

            1 Reply Last reply Reply Quote 0
            • KOMK
              KOM
              last edited by

              You don't happen to have an IP address conflict on your network, do you? You seem to have a LOT of packet loss. You need to narrow it down to your PC or pfSense. Use pfSense Diagnostics - Ping to ping those same sites and see if you get the same level of loss. That will tell you if it's your link that is flaky, or if it's something within your LAN.

              1 Reply Last reply Reply Quote 0
              • W
                Waqar.UK
                last edited by

                How do I do that?

                1 Reply Last reply Reply Quote 0
                • KOMK
                  KOM
                  last edited by

                  Well, in pfSense, go to the Diagnostics menu and select Ping. Then put those same hosts you tried to ping before into the Hostname field one by one, and see if you get the same level of packet loss. Bump the maximum number of pings to 10 or 20.

                  You didn't answer my question about IP conflict, which might explain the behaviour you're seeing here. Do you have any other clients on your LAN?

                  W 1 Reply Last reply Reply Quote 0
                  • W
                    Waqar.UK
                    last edited by

                    This is getting very strange. I tried my VPN, NordVPN. I chose UK servers. I, while connected to my VPN can connect to my pfsense box. Once dis-connected, I cannot connect.

                    1 Reply Last reply Reply Quote 0
                    • W
                      Waqar.UK @KOM
                      last edited by

                      @KOM said in Cannot log into 192.168.1.1:

                      Well, in pfSense, go to the Diagnostics menu and select Ping. Then put those same hosts you tried to ping before into the Hostname field one by one, and see if you get the same level of packet loss. Bump the maximum number of pings to 10 or 20.

                      You didn't answer my question about IP conflict, which might explain the behaviour you're seeing here. Do you have any other clients on your LAN?

                      Problem solved: In Nord VPN, there is a setting called "invisibility on LAN" I put this on the on position. When I turned this off. I can now access my pfsense box web gui. ☺ 🌞

                      1 Reply Last reply Reply Quote 1
                      • KOMK
                        KOM
                        last edited by

                        Good catch. I never would have figured that one out in a million years.

                        W 1 Reply Last reply Reply Quote 0
                        • W
                          Waqar.UK @KOM
                          last edited by

                          @KOM said in Cannot log into 192.168.1.1:

                          Good catch. I never would have figured that one out in a million years.

                          Thanks again for your help.

                          1 Reply Last reply Reply Quote 0
                          • W
                            walkerkarimo Banned
                            last edited by

                            This post is deleted!
                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.