CUPS, Alpine, and printserving : telnet weirdness
Timothy Murphy
tim at maths.tcd.ie
Sun Nov 2 00:51:26 UTC 2008
Beartooth wrote:
> [btth at Hbsk2 ~]$ telnet 192.168.a.b 631
> Trying 192.168.a.b...
> telnet: connect to address 192.168.a.b: No route to host
> [btth at Hbsk2 ~]$ ssh 192.168.a.b
> btth at 192.168.a.b's password:
> Last login: Thu Oct 30 09:51:51 2008 from 192.168.a.q
> [btth at Msgv ~]$ telnet 192.168.a.c 631
> -bash: telnet: command not found
> [btth at Msgv ~]$ telnet 192.168.a.c 631
> -bash: telnet: command not found
> [btth at Msgv ~]$ telnet 192.168.a.c 631
> -bash: telnet: command not found
> [btth at Msgv ~]$
> ===== ===== ===== =====
>
> In between those, I ran rpm -q telnet on a different gnome-
> terminal tab, and then "yum install telnet" again on a root tab. Both
> assured me telnet was there.
If this occured to me I would start by re-booting.
Incidentally, you have to put in the correct IP address of your server -
192.168.a.b was just supposed to be an indicator.
More information about the users
mailing list