Can't telnet and rlogin

[Tarek]

Hallo there,
i'm trying to telnet to a ws. The ws is on the network, with ping I see it. If i try to telnet i have this error:
Trying...
Connected to WS.
Escape character is '^]'.
Local flow controll off
Connection closed by foreign host.
With rlogin I have:
rcmd: Lost connection.
What is the problem?? I'm trying to connect remotely, because the ws is far from the place where i'm.
Any advice? Thanks in advance.

[Alexander M. Ermes]

HI there.
Can you get the remote access checked in :
SAM --> Network and Communications --> System access ? Mostly this is causes the problems with remote access.
Rgds
Alexander M. Ermes

[Alexander M. Ermes]

Hi there.
Sorry, you have to go down one more level from Remote Logins to System Access.
Rgds
Alexander M. Ermes

[Printaporn_1]

First place to start is syslog of the telnet server , any error.

with ping does it stable.
or any duplicate IP message from
netfmt -t 50 -f /var/adm/nettl.LOG00

[Tarek]

Hi Alexander..sorry but i haven't understand. I can telnet to any ws without problems, instead of this one. So is there a way to connect remotely?? If yes which one? If it isn't possible remotely, what should i do locally?? Boot on single user?? And then?? Thanks again

[Frank Li]

And you can check in your profile(~/.profile) and system profile(/etc/profile) , whether there is a "exit" in those file !!!

[Varghese Mathew]

Hi Tarek,

I think there is only on eway in front of you - go to the system (not over the network) ans see for any error - if any , they should be logged in the /var/adm/syslog/syslog.log file. Yoiu can even check the system buffer also for any error messages.

At the workstation you can try stopping the network services and restarting it by using the below command
#/sbin/init.d/net stop
#/sbin/init.d/net start
If no one else have done anything in the server level, it should start working by now.
(You can even try a system reboot, if possible)

Hope this helps

Cheers !!!
Mathew

[Tarek]

My telnet server is OK. I can telnet to any ws I want instead of this. The ping is stable and OK. I issued this command on the telnet server:
netfmt -t 50 -f /var/adm/nettl.LOG00 I had a lot of messages like:
Subsystem: STREAMS
Log Class: ERROR
140 16:30:14 11917212 1 T..5316 11 '00:30:6e:03:ee:e2'
141 16:30:14 11917212 1 T..5316 11 trying to be our address (my ws ip address)!
16:30:14 11917316 1 T..5316 11 IP: Hardware address..

[Frank Li]

Oh , you must miss some device file !

check whether there are some special file under /dev/pts/* ,
if not or does not have /dev/pts dir , use :

insf -d pts -e
insf -d tels -e


to create it . and telnet/rlogin should be okay.

[Vincenzo Restuccia]

See /var/adm/inetd.sec.

[Pedro Sousa]

Hi Tarek.

Try the following:

inetd -k (this will kill the current inetd daemon)
inetd -l (this will start it again with logging enable)

good luck.

[Victor_5]

ftp and rlogin are controlled by inetd daemon.

1. check /etc/inetd.conf
you should see something like this
ftp stream tcp nowait root /usr/lbin/ftpd ftpd
login stream tcp nowait root /usr/lbin/rlogind rlogind

2. check /etc/services and make sure the related ports are not commented

3. check /var/adm/inetd.sec
It is a security file which can allow selected clients to access one or more internet services, make sure your ws in this case is not in the list.

At the same time, check /var/adm/syslog/syslog.log to see any hint.

Hope this can helps.

[Jack Werner]

Could be the remote WS /etc/services file does not recognize/support telnet or rlogin services. Is there any way you can check this?

[Scott Painter]

guys,
If he puts his ip in the targets hosts file will that prevent a possible reverse dns lookup from causing it to time out. Maybe this isn't the case here.

[ICT Infrastructure]

I don't really know what that error message means.

140 16:30:14 11917212 1 T..5316 11 '00:30:6e:03:ee:e2'
141 16:30:14 11917212 1 T..5316 11 trying to be our address (my ws ip address)!
16:30:14 11917316 1 T..5316 11 IP: Hardware address..

But to me it suggests a duplicate IP on your network ....

[Magdi KAMAL]

Hi Tarek,

Try to shutdown your server and ping the same IP address, I would say there is an ip conflict on your net.

Magdi

[Magdi KAMAL]

Hi again,

Or disconnect your server from the net, and ping the same ip address ( it's more better than shutdowning !!!).

Magdi