1:43 p.m.
Does anyone experienced the same problem as I did. I was using telnet
for connecting to some machine but now in FC3t2 I always get this
telnet kosh
Trying 130.#.#.#...
telnet: connect to address 130.#.#.#: Connection timed out
telnet: Unable to connect to remote host: Connection timed out
Where's the problem? Is it somehow related to SELinux?
(ssh to another machime still works)
RAT
2:27 p.m.
Am Mi, den 06.10.2004 schrieb RAT um 20:43:
http://fedora.linux.duke.edu/wiki/PostIsOffTopic
Does anyone experienced the same problem as I did. I was using
telnet
for connecting to some machine but now in FC3t2 I always get this
telnet kosh
Trying 130.#.#.#...
telnet: connect to address 130.#.#.#: Connection timed out
telnet: Unable to connect to remote host: Connection timed out
Where's the problem? Is it somehow related to SELinux?
No telnet daemon running?
(ssh to another machime still works)
Use SSH and avoid the telnet daemon under any circumstance.
RAT
Alexander
--
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.8-1.521smp
Serendipity 21:26:12 up 6 days, 23:52, load average: 1.49, 1.51, 1.42
3:43 p.m.
RAT wrote:
Does anyone experienced the same problem as I did. I was using
telnet
for connecting to some machine but now in FC3t2 I always get this
telnet kosh
Trying 130.#.#.#...
telnet: connect to address 130.#.#.#: Connection timed out
telnet: Unable to connect to remote host: Connection timed out
Where's the problem? Is it somehow related to SELinux?
(ssh to another machime still works)
RAT
Does the default firewall setup block port 23 (or whatever the default
telnet port is)?
Neil
--
/***************************************************
*Neil Horman
*Software Engineer
*Red Hat, Inc.
*nhorman(a)redhat.com
*gpg keyid: 1024D / 0x92A74FA1
*http://pgp.mit.edu
***************************************************/
4:01 p.m.
There is something wrong with the telnet server. When you try to use
it does not prompt you for a username & password you get this:
[root@sendfinder vmwareboy]# telnet 192.168.1.10
Trying 192.168.1.10...
Connected to 192.168.1.10.
Escape character is '^]'.
Fedora Core release Rawhide (Rawhide)
Kernel 2.6.9 on an x86_64
Login incorrect
Login incorrect
Login incorrect
Login incorrect
and your stuck...we have a bug!!
Though I do not advocate the use of telnet, but there are a few
cases....and I mean few...that people do have to use it. But if you
are using it you need to find a way to get away from it!
On Wed, 06 Oct 2004 16:43:55 -0400, Neil Horman <nhorman(a)redhat.com> wrote:
RAT wrote:
> Does anyone experienced the same problem as I did. I was using telnet
> for connecting to some machine but now in FC3t2 I always get this
>
> telnet kosh
> Trying 130.#.#.#...
> telnet: connect to address 130.#.#.#: Connection timed out
> telnet: Unable to connect to remote host: Connection timed out
>
> Where's the problem? Is it somehow related to SELinux?
>
> (ssh to another machime still works)
>
> RAT
>
Does the default firewall setup block port 23 (or whatever the default
telnet port is)?
Neil
--
/***************************************************
*Neil Horman
*Software Engineer
*Red Hat, Inc.
*nhorman(a)redhat.com
*gpg keyid: 1024D / 0x92A74FA1
*http://pgp.mit.edu
***************************************************/
--
fedora-devel-list mailing list
fedora-devel-list(a)redhat.com
http://www.redhat.com/mailman/listinfo/fedora-devel-list
6:48 p.m.
This is actually caused by the util-linux-2.12a-pamstart.patch
in the util-linux rpm. It seems to want to use 'remote' instead
of 'login'. No idea why or how exactly that works. Making a
copy of /etc/pam.d/login to /etc/pam.d/remote might work, though
I honestly have no idea, I just recompiled it with that patch
disabled.
There is something wrong with the telnet server. When you try to use
it does not prompt you for a username & password you get this:
[root@sendfinder vmwareboy]# telnet 192.168.1.10
Trying 192.168.1.10...
Connected to 192.168.1.10.
Escape character is '^]'.
Fedora Core release Rawhide (Rawhide)
Kernel 2.6.9 on an x86_64
Login incorrect
Login incorrect
Login incorrect
Login incorrect
and your stuck...we have a bug!!
Though I do not advocate the use of telnet, but there are a few
cases....and I mean few...that people do have to use it. But if you
are using it you need to find a way to get away from it!
3:40 p.m.
Another anoyance is that you now have to put options nodots (or
something like it) in resolv to get those local machine names resolved
from (ex) dnsmasq...
ons, 06.10.2004 kl. 20.43 skrev RAT:
Does anyone experienced the same problem as I did. I was using
telnet
for connecting to some machine but now in FC3t2 I always get this
telnet kosh
Trying 130.#.#.#...
telnet: connect to address 130.#.#.#: Connection timed out
telnet: Unable to connect to remote host: Connection timed out
Where's the problem? Is it somehow related to SELinux?
(ssh to another machime still works)
RAT
7156
days inactive
7157
days old
5 comments
6 participants
participants (6)
-
Alexander Dalloz -
Jerone Young -
Kyrre Ness Sjobak -
Neil Horman -
RAT -
vallimar＠sexorcisto.net