Cannot log into 192.168.1.1

Waqar.UK

I tried to log into 192.168.1.1 a few minutes ago. I cannot log into my Pfsense web console anymore. I get told :

Unable to connect

Firefox can’t establish a connection to the server at 192.168.1.1.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

I could a few days ago. all I done is reboot my Virgin media cable modem last week since I was told that I need to do this to gain my speed increase.
I can so far, surf the Internet normally.
How can I solve this?

Thanks in advance to all replies.

KOM

Use standard troubleshooting techniques:

does it happen on more than one browser?
does it happen on more than one LAN client?
have you rebooted your pfSense box lately (aka the Universal Windows Fix)?
have you rebooted your client?

Rebooting your cablemodem would have no effect on your LAN.

chpalmer

C:>ping 192.168.1.1

Waqar.UK

C:\Windows\system32>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Windows\system32>

•does it happen on more than one browser? yes, firefox, google chrome and IE 11 all on Win 7 64
•does it happen on more than one LAN client? I am using a single ethernet port as a lan from my qotom mini pc
•have you rebooted your pfSense box lately (aka the Universal Windows Fix)? no
•have you rebooted your client? no

Waqar.UK

C:\Windows\system32>cd..

C:\Windows>cd..

C:>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
General failure.
General failure.
General failure.
General failure.

Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:>

chpalmer

http://lmgtfy.com/?q=ping+general+failure

Take a peek at some of the answers on this page and see if anything is similar to what you are running.

If your firewall was simply not answering pings you would get a different answer. Like this below. I do not have this address anywhere in my networks so obviously Im getting a time out.

Pinging 192.168.21.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.21.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Maybe try setting your client address up statically and see if things change..

KOM

Yes, that General failure is certainly suspicious. I can't remember if I've ever seen that before. Bad hardware perhaps?

Jessica007

@KOM Those techniques didn't help me unfortunately...

Waqar.UK

@KOM said in Cannot log into 192.168.1.1:

Yes, that General failure is certainly suspicious. I can't remember if I've ever seen that before. Bad hardware perhaps?

I can still surf the Internet, but when I do 'ipconfig':

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>

KOM

Have you rebooted both? Have you tried getting to WebGUI by using another PC or your phone on wifi? Have you gone to the console and tried options 11 and 16?

Waqar.UK

OK, I just tried 192.168.1.1 via my Android phone.

I cabolded textn access my pfsense web console and log on via wireless. But via my wired Ethernet. I cannot.

Waqar.UK

Can access pfsense web console on 192.168.1.1 via my Pocophone F1 Android phone which has Android 9 fully patched.

KOM

I would reboot both your pfSense box and your PC. Something really weird is going on. Since your Internet access is still good, it can't be the NIC or the cable or the pfSense NIC. At least you have a workaround now.

Waqar.UK

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).

Waqar.UK

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>

KOM

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

Waqar.UK

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

KOM

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.

Waqar.UK

How do I do that?

KOM

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?