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.
To see what services are listing globally vs what services are
listening on localhost, you can use the ss command. For example:
tcameron@case:~$ ss -tnlp | grep 631
LISTEN 0 4096 127.0.0.1:631 0.0.0.0:*
LISTEN 0 4096 [::1]:631 [::]:*
tcameron@case:~$
You can see that cups is listening on 631, but only on localhost
(127.0.0.1).
-----------------------
You can also use nmap to check a specific port. My machine is
172.31.100.4, so I ran two scans: One on the external interface
(172.31.100.4), and one on the loopback (127.0.0.1):
tcameron@case:~$ nmap 172.31.100.4 -p 631
Starting Nmap 7.92 ( https://nmap.org ) at 2026-01-08 13:32 CST
Nmap scan report for case.xxx.com (172.31.100.4)
Host is up (0.00011s latency).
PORT STATE SERVICE
631/tcp closed ipp
Nmap done: 1 IP address (1 host up) scanned in 0.02 seconds
-----------------------
tcameron@case:~$ nmap 127.0.0.1 -p 631
Starting Nmap 7.92 ( https://nmap.org ) at 2026-01-08 13:32 CST
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00010s latency).
PORT STATE SERVICE
631/tcp open ipp
Nmap done: 1 IP address (1 host up) scanned in 0.02 seconds
-----------------------
Hope this helps.
Thanks Thomas, I'll check these out. My issue was I stupidly used the
wrong IP address for localhost, I had stupidly used the gateway address
of my previous router, and when that didn't work I tried the gateway
address of my current router which also didn't work. If I had used the
commands you have shown they would both have said the first IP address I
tried didn't exist but that the second IP address I tried did exist
which at the time wouldn't have helped me identify that for what I was
trying to do I was using the wrong address.
regards,
BEGIN:VCARD
VERSION:4.0
N:Morris;Stephen;;;
FN:Stephen Morris
EMAIL;PREF=1;TYPE=home:[email protected]
END:VCARD
--
_______________________________________________
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
