[opensuse-support] lost hplip printing
tumbleweed uptodate hplip-3.18.6-1.1.x86_64 HP OfficeJet Pro 8620 configured wireless static 192.168.1.12 printer worked fine until yesterday and the only changes I have made are tumbleweed updates using dup. can print to this printer from three windows 10 machines can ping 192.168.1.12 from three windows 10 machines cannot ping from 3 tw and one 42.2 box hp-setup cannot detect printer, 192.168.1.12, on my network from 4 openSUSE boxes. firewall off makes no difference I can setup the printer from yast and from localhost:631 but cannot print. I am lost, what to do next? fwiw, I have another networked printer, 192.168.1.197, HP OfficeJet Pro 8615, and can print to it from all boxes and can ping it from all boxes. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On Mon, Oct 15, 2018 at 12:08 PM Patrick Shanahan <paka@opensuse.org> wrote:
tumbleweed uptodate hplip-3.18.6-1.1.x86_64 HP OfficeJet Pro 8620
configured wireless static 192.168.1.12
printer worked fine until yesterday and the only changes I have made are tumbleweed updates using dup.
can print to this printer from three windows 10 machines can ping 192.168.1.12 from three windows 10 machines
cannot ping from 3 tw and one 42.2 box
hp-setup cannot detect printer, 192.168.1.12, on my network from 4 openSUSE boxes.
firewall off makes no difference
I can setup the printer from yast and from localhost:631 but cannot print.
I am lost, what to do next?
fwiw, I have another networked printer, 192.168.1.197, HP OfficeJet Pro 8615, and can print to it from all boxes and can ping it from all boxes.
tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
Last time this happened I just deleted the printer and readded it via the HP utility. I was beating my head against the wall until I did that. Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND 927.0875Mhz and 441.125 analog 441.600 DMR Repeaters Taft Ca. openSUSE Tumbleweed KDE Plasma with Packman -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Steven Hess <flamebait@gmail.com> [10-15-18 15:32]:
On Mon, Oct 15, 2018 at 12:08 PM Patrick Shanahan <paka@opensuse.org> wrote:
tumbleweed uptodate hplip-3.18.6-1.1.x86_64 HP OfficeJet Pro 8620
configured wireless static 192.168.1.12
printer worked fine until yesterday and the only changes I have made are tumbleweed updates using dup.
can print to this printer from three windows 10 machines can ping 192.168.1.12 from three windows 10 machines
cannot ping from 3 tw and one 42.2 box
hp-setup cannot detect printer, 192.168.1.12, on my network from 4 openSUSE boxes.
firewall off makes no difference
I can setup the printer from yast and from localhost:631 but cannot print.
I am lost, what to do next?
fwiw, I have another networked printer, 192.168.1.197, HP OfficeJet Pro 8615, and can print to it from all boxes and can ping it from all boxes.
Last time this happened I just deleted the printer and readded it via the HP utility. I was beating my head against the wall until I did that.
yes, I did that in an earlier effort and it failed. above is since that. at that time I only had problems with print failing for the 8620 on 192.168.1.12. but I cannot get it back with hp-setup or the web browser. I get "HPLIP cannot detect printers in your network" and direction to a less than helpful web site, http://hplipopensource.com/node/374 and stopping the firewall makes no difference. the ports are open anyway. arp shows: 192.168.1.12 ether 6c:c2:17:1d:2f:26 C enp0s25 ip n: 192.168.1.12 dev enp0s25 lladdr 6c:c2:17:1d:2f:26 PROBE ip neighbor show dev enp0s25: 192.168.1.12 FAILED tks, but still lost... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.21.1810152139571.8260@Telcontar.valinor> On Monday, 2018-10-15 at 15:08 -0400, Patrick Shanahan wrote:
tumbleweed uptodate hplip-3.18.6-1.1.x86_64 HP OfficeJet Pro 8620
configured wireless static 192.168.1.12
printer worked fine until yesterday and the only changes I have made are tumbleweed updates using dup.
can print to this printer from three windows 10 machines can ping 192.168.1.12 from three windows 10 machines
cannot ping from 3 tw and one 42.2 box
That rules out cups stack or hplip. I assume you can ping other machines? Ah, yes, I see you can print to another printer. This printer is on wifi?
hp-setup cannot detect printer, 192.168.1.12, on my network from 4 openSUSE boxes.
firewall off makes no difference
I can setup the printer from yast and from localhost:631 but cannot print.
I am lost, what to do next?
fwiw, I have another networked printer, 192.168.1.197, HP OfficeJet Pro 8615, and can print to it from all boxes and can ping it from all boxes.
tks,
I would reboot the printer, first of all. My HP printer sometimes does that, refuse to print and needs a kick. Next, I would check the configuration of the printer to ensure that it is still 192.168.1.12 - if it changed, I guess Windows can find it anyway. Next, try ping to the printer. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlvE7koACgkQtTMYHG2NR9VqvACggCC9swhPHLqII3NFoSOgsI67 Nv4An0iHRpNm1Xl3t4icMUTY5STZgHT+ =louO -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [10-15-18 15:45]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Content-ID: <alpine.LSU.2.21.1810152139571.8260@Telcontar.valinor>
On Monday, 2018-10-15 at 15:08 -0400, Patrick Shanahan wrote:
tumbleweed uptodate hplip-3.18.6-1.1.x86_64 HP OfficeJet Pro 8620
configured wireless static 192.168.1.12
printer worked fine until yesterday and the only changes I have made are tumbleweed updates using dup.
can print to this printer from three windows 10 machines can ping 192.168.1.12 from three windows 10 machines
cannot ping from 3 tw and one 42.2 box
That rules out cups stack or hplip.
I assume you can ping other machines? Ah, yes, I see you can print to another printer.
This printer is on wifi?
yes, both are. the 8620/192.168.1.12 failed to print and in trying to reconfigure, I removed the printer using the hplip interface, but cannot reconfigure or read subject printer.
hp-setup cannot detect printer, 192.168.1.12, on my network from 4 openSUSE boxes.
firewall off makes no difference
I can setup the printer from yast and from localhost:631 but cannot print.
I am lost, what to do next?
fwiw, I have another networked printer, 192.168.1.197, HP OfficeJet Pro 8615, and can print to it from all boxes and can ping it from all boxes.
tks,
I would reboot the printer, first of all.
have done that several times, doing again, also removed power cord. I waited >15 minutes and reattached power and started device ip n show: 192.168.1.12 dev enp0s25 lladdr 6c:c2:17:1d:2f:26 REACHABLE but changes in about 60 seconds to: 192.168.1.12 dev enp0s25 lladdr 6c:c2:17:1d:2f:26 STALE and no change in efforts with hp-setup
My HP printer sometimes does that, refuse to print and needs a kick.
Next, I would check the configuration of the printer to ensure that it is still 192.168.1.12 - if it changed, I guess Windows can find it anyway.
I deliberately changed it earlier with same result from all boxes (192.168.1.75) and changed it back.
Next, try ping to the printer.
believe I said that. can from several windows 10 boxes but cannot from any linux box. and still cannot after repowering. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
* Patrick Shanahan <paka@opensuse.org> [10-15-18 16:12]:
* Carlos E. R. <robin.listas@telefonica.net> [10-15-18 15:45]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Content-ID: <alpine.LSU.2.21.1810152139571.8260@Telcontar.valinor>
On Monday, 2018-10-15 at 15:08 -0400, Patrick Shanahan wrote:
tumbleweed uptodate hplip-3.18.6-1.1.x86_64 HP OfficeJet Pro 8620
configured wireless static 192.168.1.12
printer worked fine until yesterday and the only changes I have made are tumbleweed updates using dup.
can print to this printer from three windows 10 machines can ping 192.168.1.12 from three windows 10 machines
cannot ping from 3 tw and one 42.2 box
That rules out cups stack or hplip.
I assume you can ping other machines? Ah, yes, I see you can print to another printer.
This printer is on wifi?
yes, both are.
the 8620/192.168.1.12 failed to print and in trying to reconfigure, I removed the printer using the hplip interface, but cannot reconfigure or read subject printer.
hp-setup cannot detect printer, 192.168.1.12, on my network from 4 openSUSE boxes.
firewall off makes no difference
I can setup the printer from yast and from localhost:631 but cannot print.
I am lost, what to do next?
fwiw, I have another networked printer, 192.168.1.197, HP OfficeJet Pro 8615, and can print to it from all boxes and can ping it from all boxes.
tks,
I would reboot the printer, first of all.
have done that several times, doing again, also removed power cord. I waited >15 minutes and reattached power and started device
ip n show: 192.168.1.12 dev enp0s25 lladdr 6c:c2:17:1d:2f:26 REACHABLE but changes in about 60 seconds to: 192.168.1.12 dev enp0s25 lladdr 6c:c2:17:1d:2f:26 STALE
and about another 60 seconds: 192.168.1.12 dev enp0s25 FAILED
and no change in efforts with hp-setup
My HP printer sometimes does that, refuse to print and needs a kick.
Next, I would check the configuration of the printer to ensure that it is still 192.168.1.12 - if it changed, I guess Windows can find it anyway.
I deliberately changed it earlier with same result from all boxes (192.168.1.75) and changed it back.
Next, try ping to the printer.
believe I said that. can from several windows 10 boxes but cannot from any linux box.
and still cannot after repowering.
tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 15/10/2018 22.10, Patrick Shanahan wrote:
* Carlos E. R. <> [10-15-18 15:45]>> On Monday, 2018-10-15 at 15:08 -0400, Patrick Shanahan wrote:
tumbleweed uptodate hplip-3.18.6-1.1.x86_64 HP OfficeJet Pro 8620
configured wireless static 192.168.1.12
printer worked fine until yesterday and the only changes I have made are tumbleweed updates using dup.
can print to this printer from three windows 10 machines can ping 192.168.1.12 from three windows 10 machines
cannot ping from 3 tw and one 42.2 box
That rules out cups stack or hplip.
I assume you can ping other machines? Ah, yes, I see you can print to another printer.
This printer is on wifi?
yes, both are.
the 8620/192.168.1.12 failed to print and in trying to reconfigure, I removed the printer using the hplip interface, but cannot reconfigure or read subject printer.
No, I don't think this is an hplip issue, as long as you can not even ping the printer.
hp-setup cannot detect printer, 192.168.1.12, on my network from 4 openSUSE boxes.
firewall off makes no difference
I can setup the printer from yast and from localhost:631 but cannot print.
I am lost, what to do next?
fwiw, I have another networked printer, 192.168.1.197, HP OfficeJet Pro 8615, and can print to it from all boxes and can ping it from all boxes.
tks,
I would reboot the printer, first of all.
have done that several times, doing again, also removed power cord. I waited >15 minutes and reattached power and started device
ip n show: 192.168.1.12 dev enp0s25 lladdr 6c:c2:17:1d:2f:26 REACHABLE but changes in about 60 seconds to: 192.168.1.12 dev enp0s25 lladdr 6c:c2:17:1d:2f:26 STALE
and no change in efforts with hp-setup
My HP printer sometimes does that, refuse to print and needs a kick.
Next, I would check the configuration of the printer to ensure that it is still 192.168.1.12 - if it changed, I guess Windows can find it anyway.
I deliberately changed it earlier with same result from all boxes (192.168.1.75) and changed it back.
I meant using the printer panel itself, not the computer. You should also be able to browse to http://192.168.1.12 in firefox or similar.
Next, try ping to the printer.
believe I said that. can from several windows 10 boxes but cannot from any linux box.
and still cannot after repowering.
Well, you have a network issue. You could try then a traceroute. Try also to reboot the WiFi access point and/or router. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [10-15-18 16:35]:
On 15/10/2018 22.10, Patrick Shanahan wrote:
* Carlos E. R. <> [10-15-18 15:45]>> On Monday, 2018-10-15 at 15:08 -0400, Patrick Shanahan wrote:
tumbleweed uptodate hplip-3.18.6-1.1.x86_64 HP OfficeJet Pro 8620
configured wireless static 192.168.1.12
printer worked fine until yesterday and the only changes I have made are tumbleweed updates using dup.
can print to this printer from three windows 10 machines can ping 192.168.1.12 from three windows 10 machines
cannot ping from 3 tw and one 42.2 box
That rules out cups stack or hplip.
I assume you can ping other machines? Ah, yes, I see you can print to another printer.
This printer is on wifi?
yes, both are.
the 8620/192.168.1.12 failed to print and in trying to reconfigure, I removed the printer using the hplip interface, but cannot reconfigure or read subject printer.
No, I don't think this is an hplip issue, as long as you can not even ping the printer.
hp-setup cannot detect printer, 192.168.1.12, on my network from 4 openSUSE boxes.
firewall off makes no difference
I can setup the printer from yast and from localhost:631 but cannot print.
I am lost, what to do next?
fwiw, I have another networked printer, 192.168.1.197, HP OfficeJet Pro 8615, and can print to it from all boxes and can ping it from all boxes.
tks,
I would reboot the printer, first of all.
have done that several times, doing again, also removed power cord. I waited >15 minutes and reattached power and started device
ip n show: 192.168.1.12 dev enp0s25 lladdr 6c:c2:17:1d:2f:26 REACHABLE but changes in about 60 seconds to: 192.168.1.12 dev enp0s25 lladdr 6c:c2:17:1d:2f:26 STALE
and no change in efforts with hp-setup
My HP printer sometimes does that, refuse to print and needs a kick.
Next, I would check the configuration of the printer to ensure that it is still 192.168.1.12 - if it changed, I guess Windows can find it anyway.
I deliberately changed it earlier with same result from all boxes (192.168.1.75) and changed it back.
I meant using the printer panel itself, not the computer.
yes, using the printer panel. changed from static ..12 to automatic ..75. still could not ping 192.168.1.75, nor access with browser or with hp-setup.
You should also be able to browse to http://192.168.1.12 in firefox or similar.
cannot ping and cannot browse http://192.168.1.12 nor 192.168.1.75
Next, try ping to the printer.
believe I said that. can from several windows 10 boxes but cannot from any linux box.
and still cannot after repowering.
Well, you have a network issue. You could try then a traceroute. Try also to reboot the WiFi access point and/or router.
will try rebooting the router but windows boxes can ping and browse and print to 192.168.1.12. connect cat5 and suddenly can ping and browser and hp-setup. disconnected cable after set up, hplip shows printer and "device communication error". rebooting router, will report back. disconnected cable ok, network starting, waiting for wireless ahhh, can ping from wired machine, and others that's dumb, stupid, ignorant and fscked up! why would a linux based router allow windows access and deny linux systems? now setup completes and printing is working. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 15/10/2018 23.37, Patrick Shanahan wrote:
* Carlos E. R. <> [10-15-18 16:35]:
On 15/10/2018 22.10, Patrick Shanahan wrote:
* Carlos E. R. <> [10-15-18 15:45]>> On Monday, 2018-10-15 at 15:08 -0400, Patrick Shanahan wrote:
I meant using the printer panel itself, not the computer.
yes, using the printer panel. changed from static ..12 to automatic ..75.
still could not ping 192.168.1.75, nor access with browser or with hp-setup.
You should also be able to browse to http://192.168.1.12 in firefox or similar.
cannot ping and cannot browse http://192.168.1.12 nor 192.168.1.75
Next, try ping to the printer.
believe I said that. can from several windows 10 boxes but cannot from any linux box.
and still cannot after repowering.
Well, you have a network issue. You could try then a traceroute. Try also to reboot the WiFi access point and/or router.
will try rebooting the router but windows boxes can ping and browse and print to 192.168.1.12.
Yeah, I know.
connect cat5 and suddenly can ping and browser and hp-setup. disconnected cable after set up, hplip shows printer and "device communication error".
rebooting router, will report back. disconnected cable
ok, network starting, waiting for wireless
ahhh, can ping from wired machine, and others
that's dumb, stupid, ignorant and fscked up!
why would a linux based router allow windows access and deny linux systems?
I assume a cheap router, like mine. Well, they are crap... mine hangs now and then, has to be power cycled. A pain for remote access, I have a power strip that can power cycle the router controlled from another machine. Why it affected Linux hosts and not Windows hosts is a mystery. Maybe because they only tested with Windows hosts. Sometimes my phone says no wifi, or that the wifi has no internet. The other day Windows said that. Reboot the WiFi access point, and back to normal. Go figure.
now setup completes and printing is working.
tks,
Welcome :-) -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [10-15-18 18:05]: [...]
I assume a cheap router, like mine. Well, they are crap... mine hangs now and then, has to be power cycled. A pain for remote access, I have a power strip that can power cycle the router controlled from another machine.
Why it affected Linux hosts and not Windows hosts is a mystery. Maybe because they only tested with Windows hosts.
Sometimes my phone says no wifi, or that the wifi has no internet. The other day Windows said that. Reboot the WiFi access point, and back to normal. Go figure.
now setup completes and printing is working.
tks,
Welcome :-)
biggest provider of internet access in the USA, at&t. service is crap, been there about 18 months and on sixth router, 4 in 10 days. everyone one had different problem and all supposedly new. none would allow moving the router's passthru ssh port. two would not pass http(s). current one apparently just fails when it feels like it. fwiw, roadrunner equipment caused me the fewest problems in the past 20 years and was the most configurable. also the most costly :(. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 16/10/2018 00.24, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [10-15-18 18:05]: [...]
I assume a cheap router, like mine. Well, they are crap... mine hangs now and then, has to be power cycled. A pain for remote access, I have a power strip that can power cycle the router controlled from another machine.
Why it affected Linux hosts and not Windows hosts is a mystery. Maybe because they only tested with Windows hosts.
Sometimes my phone says no wifi, or that the wifi has no internet. The other day Windows said that. Reboot the WiFi access point, and back to normal. Go figure.
now setup completes and printing is working.
tks,
Welcome :-)
biggest provider of internet access in the USA, at&t. service is crap, been there about 18 months and on sixth router, 4 in 10 days. everyone one had different problem and all supposedly new. none would allow moving the router's passthru ssh port. two would not pass http(s).
Maybe you can place your own router. :-? I can't, the setup is difficult to replicate and not documented.
current one apparently just fails when it feels like it.
Well, if rebooting the issue, and there are not other issues... count your blessings. Maybe if many people complain they'll issue some other model.
fwiw, roadrunner equipment caused me the fewest problems in the past 20 years and was the most configurable. also the most costly :(.
An administrator I met (business admin, not computer admin) told me, when I was young, that cheap turns out to be expensive. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
* Carlos E. R. <robin.listas@telefonica.net> [10-15-18 20:02]:
On 16/10/2018 00.24, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [10-15-18 18:05]: [...]
I assume a cheap router, like mine. Well, they are crap... mine hangs now and then, has to be power cycled. A pain for remote access, I have a power strip that can power cycle the router controlled from another machine.
Why it affected Linux hosts and not Windows hosts is a mystery. Maybe because they only tested with Windows hosts.
Sometimes my phone says no wifi, or that the wifi has no internet. The other day Windows said that. Reboot the WiFi access point, and back to normal. Go figure.
now setup completes and printing is working.
tks,
Welcome :-)
biggest provider of internet access in the USA, at&t. service is crap, been there about 18 months and on sixth router, 4 in 10 days. everyone one had different problem and all supposedly new. none would allow moving the router's passthru ssh port. two would not pass http(s).
Maybe you can place your own router. :-? I can't, the setup is difficult to replicate and not documented.
current one apparently just fails when it feels like it.
Well, if rebooting the issue, and there are not other issues... count your blessings.
Maybe if many people complain they'll issue some other model.
fwiw, roadrunner equipment caused me the fewest problems in the past 20 years and was the most configurable. also the most costly :(.
An administrator I met (business admin, not computer admin) told me, when I was young, that cheap turns out to be expensive.
unfortunately, this turn out to be what one really needs vs what one is willing to pay. the salve provided by the difference is cost soothes much of the pain coming from lack of quality control. but that salve does not cease one from advertising the discomfort caused by at&t's lack of quality. even navigating their menu system is a pain in the ass. almost as bad as their chat system with people looking up the discription of your problem on their cheat-sheets and giving you answers about mowing your lawn or trimming the shrubs. no idea about technical matters and don't have any idea who or where to elevate your conversation. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 16/10/2018 02.51, Patrick Shanahan wrote:
* Carlos E. R. <> [10-15-18 20:02]:
On 16/10/2018 00.24, Patrick Shanahan wrote:
* Carlos E. R. <> [10-15-18 18:05]:
...
Maybe you can place your own router. :-? I can't, the setup is difficult to replicate and not documented.
current one apparently just fails when it feels like it.
Well, if rebooting the issue, and there are not other issues... count your blessings.
Maybe if many people complain they'll issue some other model.
fwiw, roadrunner equipment caused me the fewest problems in the past 20 years and was the most configurable. also the most costly :(.
An administrator I met (business admin, not computer admin) told me, when I was young, that cheap turns out to be expensive.
unfortunately, this turn out to be what one really needs vs what one is willing to pay. the salve provided by the difference is cost soothes much of the pain coming from lack of quality control.
but that salve does not cease one from advertising the discomfort caused by at&t's lack of quality.
Ah, yes, I do similarly :-)
even navigating their menu system is a pain in the ass. almost as bad as their chat system with people looking up the discription of your problem on their cheat-sheets and giving you answers about mowing your lawn or trimming the shrubs. no idea about technical matters and don't have any idea who or where to elevate your conversation.
Ah, here Telefónica chat system is better quality usually (not always). At least on the forum I can get answers from people that know after some days, and if they say they do some thing they really do it - something that is not that certain via phone. Telefonica was participated at the start (1924) by ITT (International Telephone & Telegraph); I thought it was AT&T or Bell. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [10-16-18 08:22]:
On 16/10/2018 02.51, Patrick Shanahan wrote:
* Carlos E. R. <> [10-15-18 20:02]:
On 16/10/2018 00.24, Patrick Shanahan wrote:
* Carlos E. R. <> [10-15-18 18:05]:
...
Maybe you can place your own router. :-? I can't, the setup is difficult to replicate and not documented.
current one apparently just fails when it feels like it.
Well, if rebooting the issue, and there are not other issues... count your blessings.
Maybe if many people complain they'll issue some other model.
fwiw, roadrunner equipment caused me the fewest problems in the past 20 years and was the most configurable. also the most costly :(.
An administrator I met (business admin, not computer admin) told me, when I was young, that cheap turns out to be expensive.
unfortunately, this turn out to be what one really needs vs what one is willing to pay. the salve provided by the difference is cost soothes much of the pain coming from lack of quality control.
but that salve does not cease one from advertising the discomfort caused by at&t's lack of quality.
Ah, yes, I do similarly :-)
even navigating their menu system is a pain in the ass. almost as bad as their chat system with people looking up the discription of your problem on their cheat-sheets and giving you answers about mowing your lawn or trimming the shrubs. no idea about technical matters and don't have any idea who or where to elevate your conversation.
Ah, here Telefónica chat system is better quality usually (not always). At least on the forum I can get answers from people that know after some days, and if they say they do some thing they really do it - something that is not that certain via phone.
Telefonica was participated at the start (1924) by ITT (International Telephone & Telegraph); I thought it was AT&T or Bell.
at&t and bell are pretty much the same thing. bell held a monopoly on telephone service in the USA and was broken up in 1982. the at&t company was purchased by one of the resulting smaller entities, Southwestern Bell. we have wandered off-topic. further discussion should be moved there... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
participants (3)
-
Carlos E. R. -
Patrick Shanahan -
Steven Hess