I agree that this is an issue with the printer's IP address. I have a few of these. I'm too lazy to write down all the steps to deal with this, but I made a video of how to view and set the IP.
https://www.youtube.com/watch?v=eJvNbBbrsgU You can find the IP address your internal network uses by running the "ifconfig" command on the command line: $ ifconfig eth0 Link encap:Ethernet HWaddr 40:40:72:FD:A5:B0 inet addr:192.168.1.59 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::4240:72ff:fefd:a5b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:163214907 errors:0 dropped:0 overruns:0 frame:0 TX packets:223887222 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12206629277 (11.3 GiB) TX bytes:193416766812 (180.1 GiB) Interrupt:24 note the line stating "inet addr:" - this is the IP you should emulate. don't use the same one for your printer, use one that won't ever be used elsewhere on your network. 254 is a good bet because it's the highest, and most networks don't reach the highest number. but it's not guaranteed. You seem an intrepid type, so hopefully this gives you the right direction to pursue. You should be able to ping the IP address once it's set properly: $ ping 192.168.1.254 PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data. 64 bytes from 192.168.1.254: icmp_seq=1 ttl=49 time=62.8 ms 64 bytes from 192.168.1.254: icmp_seq=2 ttl=49 time=61.5 ms 64 bytes from 192.168.1.254: icmp_seq=3 ttl=49 time=62.3 ms 64 bytes from 192.168.1.254: icmp_seq=4 ttl=49 time=60.8 ms ^C --- 192.168.1.254 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 60.873/61.901/62.810/0.749 ms If you can't, you're still having a network problem, don't bother messing with your printer configs until this is resolved and you get ping responses. -wes On Thu, Nov 5, 2015 at 9:41 PM, Charles <[email protected]> wrote: > On 11/05/2015 07:06 PM, John Bartley K7AAY [email protected] wrote: > <snip> > > Charles, a Penguinista could also remotely access your system and, with > > you at the system to unplug/replug if needed, help you solve your issue > > without schlepping out 26. > > I really like these > remote screen connections & "virtual network connections", John. > > I have used them before; > & with a good teckie on the other end, > frequently problems can quickly be remedied. > > But, under such a set-up, i think i would need > one of the fellas here to agree to try to > work with me in solving my printer-problem with it. > > And this technology is great for curing probs in a single-computer; > but when networking & printers are involved, > it frequently seems that live-people need to be in the room. > > > Here's a list of remote access apps > > https://en.wikipedia.org/wiki/Comparison_of_remote_desktop_software and > > there are free remote client and server apps for Linux. > > Very nice. > I would be happy to install one of these > if any-one here was willing to > dive more deeply in-to the difficulties of my system. > > Cz ... > > _______________________________________________ > > PLUG mailing list > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
