On Wed, 2026-01-07 at 08:26 +1100, Stephen Morris wrote: > Following on from another thread raised about Chrome not seeing > printers I have tried to connect to cups to verify that my printer was > available (I believed it was as I have done printing from other apps) > and I am getting connection timeouts on 192.168.1.1:631 and > 192.168.1.1:630 (I couldn't remember the exact port for cups). Why would > this timeout be occuring from both Chrome and Firefox? A ping of > 192.168.1.1 doesn't produce any results either, the behaviour of ping on > that address makes it look like ping has hung. >
Various things only respond to localhost (127.0.0.1) by default, so they're deliberately not accessible in another way (even on the same machine). You can change that if you want LAN-wide control. Bear in mind any security implications if something outside can traverse into your LAN. Ping only tests the TCP/IP stack, it can only be used to try and test whether there is a computer on a network address (if the stack responds). It says nothing about whether any servers on that system are working or not. i.e. You can ping a PC, you cannot ping the mail server software. Some firewalls block pings, believing it's a security problem. Usually it is not, miscreants have other ways to tell if something is at an address that doesn't rely on ping. And a simple no-answer is not the same as an address not in use kind of response. Some also block all ICMP traffic, and end up breaking networking in the process. There's various network handshaking traffic that relies on it. If you want pings to work, you can modify your firewall to allow it (globally, or just within your LAN). -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 (yes, this is the output from uname for this PC when I posted) Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
