Re: CUPS, Alpine, and printserving : telnet weirdness

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Beartooth wrote:


> [btth@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@Hbsk2 ~]$ ssh 192.168.a.b
> btth@xxxxxxxxxxx's password:
> Last login: Thu Oct 30 09:51:51 2008 from 192.168.a.q
> [btth@Msgv ~]$ telnet 192.168.a.c 631
> -bash: telnet: command not found
> [btth@Msgv ~]$ telnet 192.168.a.c 631
> -bash: telnet: command not found
> [btth@Msgv ~]$ telnet 192.168.a.c 631
> -bash: telnet: command not found
> [btth@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.

 


-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux