Telnet service_limit error

Previously I posted Inactive TELNET session timeout, How To Check Number of SSH and Telnet session and today I would like to share something related to TELNET again. In fact, I know telnet is NOT secure.

Referring to /var/log/xinetd.log(telnet parked under xinetd services), if you found something look like FAIL: telnet service_limit mean telnet instances are over limit.

09/8/26@10:43:23: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:23: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:24: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:24: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:25: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:25: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:26: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:26: FAIL: telnet service_limit from=192.168.10.180
09/8/26@10:43:27: FAIL: telnet service_limit from=192.168.10.180

Possibly Related Posts:

August 26, 2009 · Filed Under Open Source, Tips

Comment

How To Capture PUTTY Session Log

PuTTY is a free implementation of Telnet and SSH for Win32 and Unix platforms, along with an xterm terminal emulator. It is written and maintained primarily by Simon Tatham.

Here I would like to share How To Capture PUTTY Session Log.

1. To capture a session with PuTTY, open up a PUTTY.
2. Look for Category Session -> Logging
3. Under Session Logging, choose “All session output” and key in your desire log filename(default is putty.log).

4. This should create the file in the location you choose and start loggin everyting from the session.
5. For capture Cisco Router or Switches(I tried with Nexus 1000V on VMware vSphere), type ’show running-config’.

Read more