On 9/12/21 4:58 PM, Carlos E. R. wrote:
El 2021-09-12 a las 15:19 -0400, Douglas McGarrett escribió:
On 9/12/21 6:24 AM, Carlos E. R. wrote:
On 12/09/2021 00.40, Douglas McGarrett wrote:
I am not familiar with the value of the third number in the ips. I seem to remember that 5 or 6 years ago, all my ips had a 1 in the third position; now they all seem to want a 0.
Well, your router changed, didn't it? Then the numbers can change, 0 and 1 are typical, but it could be 132, or 83, or 200, for instance.
...
I found in the printer manual, a way to get a status sheet from the printer's control panel. It shows that the original static ip address that was set back around 2016 is still in effect. I suspect that whatever is supposed to decode that from a ping has been blown out, since it does not respond to a ping at that ip. Now I mentioned earlier that the third number in the ip addresses on my network now is 0, where it used to be 1, and one of the correspondents here suggested that this is router dependent. Will the router not interrogate an address with a 1 in the third position? (The old router was destroyed in the lightning strike--I can't put it back and try it!) It seems that there are unknown failures in the printer, in addition to the one already found--the FAX line is zapped. comments?
Tell what that IP in the printed paper is. That information is important and you hide it from us.
If it is not 192.168.0.something, the printer will not respond to pings and you have to reconfigure it using its panel.
We're going round in circles. The printer was set up to be 192.168.1.26 back around 2016 or so, and it worked that way--even in OpenSUSE Tumbleweed-- but I could never get it (or the HP, either) to work in Leap, either before or after the lightning strike. As I mentioned previously in this track, all of the items on the lan were originally set up with 1 in the third position, and now it seems that everything (except, of course, this printer) wants to have a 0 in that position. I discovered the hard way that it is EXTREMELY difficult to enter anything into the printer via its control panel. Is there any reason you know of that I should not be able to ping 192.158.1.26 on the lan? Such a ping does not respond: linux1:~ # ping 192.168.1.26 PING 192.168.1.26 (192.168.1.26) 56(84) bytes of data. ^C --- 192.168.1.26 ping statistics --- 14 packets transmitted, 0 received, 100% packet loss, time 13295ms --doug
-- Cheers Carlos E. R.
(from openSUSE 15.2 (Legolas))