Goofy telnet issue

Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Goofy telnet issue
# 1  
Old 06-17-2011
Goofy telnet issue

Greetings! My name is Jerry. I am a long time IBM i-series (AS/400) admin. I am the solo IT guy at a $50M company, we run mostly Windows servers on virtual machines, I do have one i-series, and one p-series.
Recently, we have decided to go with a legacy product that is proven and bulletproof, it runs on AIX, so I dusted my P5 off and fired it up. It immediately came online and I was able to telnet and log in from local, and through a port forward on 23 through my Sonicwall firewall.
The port forwarding did work a couple times throughout the day, and MAY have coincided with bringing the machine up with a manual IPL.
Everything looks right on the firewall, and I have redone it 4 times, I am no stranger to setting up virtual servers on Sonicwall.
I am wondering, since we have changed ISP's since we last used this server, if it is possible it has some sort of built in firewall or ip address filtering not allowing it to take connections from outside my local network?
Anybody seen something like this before?
If you think you would like to take a look in my box, PM me, I am give you connection info.
Thanks in advance!

---------- Post updated 06-17-11 at 10:21 AM ---------- Previous update was 06-16-11 at 09:45 PM ----------

It appears as though the system has full connectivity immediately after a reboot. But loses telnet ability to client outside my local network after a half hour or so...
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Telnet issue

In the below script, i want to check telnet port status of list of servers, here where ever port working i am getting output. where ever port is not working (where ever trying) there it's command stuck, there it's needed manual interruption like ctrl+c. without interception i want run this... (1 Reply)
Discussion started by: rajiv
1 Replies

2. Red Hat

Telnet issue

Hi All! for lab purposes i need to run telnet server on my RedHat 7 machine. i installed the package: telnet-server using yum. i read that i need to edit the telnet file under /etc/xinetd.d the problem is that there is no telnet file in that folder. the telnet server install completed... (9 Replies)
Discussion started by: guy3145
9 Replies

3. Linux

Infuriating Telnet Issue

Hi, Recently I've been working a lot with telnet for various reasons (obsolete, I realise). However, I've run into an issue. With most telnet clients, login is possible. However, with a few, typing is possible until I try to hit enter. For example, I try to type "admin" as the username and... (5 Replies)
Discussion started by: FreddoT
5 Replies

4. HP-UX

[SOLVED] Telnet timeout issue

I have telnet configured in /etc/inetd.conf as below: telnet stream tcp6 nowait root /usr/lbin/telnetd telnetd -b /etc/issue -n20 When i restart the service telnetd shows with only the -b option: ps -ef|grep telnetd|grep -v grep root 24397 1 0 10:42:35 pts/ta 0:00... (1 Reply)
Discussion started by: Tommyk
1 Replies

5. Solaris

Telnet issue

Hi Gurus, I have solaris 10 server where I can telnet to one host and port <20011> with no problem..but when I am trying to telnet to another host same port (port is listening) I am not getting any just says trying.... Now that I have both hosts listed in the /etc/hosts file,... (4 Replies)
Discussion started by: mohullah
4 Replies

6. Shell Programming and Scripting

urgent help needed in telnet issue

Hi, Whenever i am trying to telnet to server i am getting frequent error Authorized Login: prtsrc's Password: /dev/pts/171: Password read timed out -- possible noise on port when i am rerunning the same it is working fine thanks, sam (2 Replies)
Discussion started by: sam99
2 Replies

7. Shell Programming and Scripting

telnet issue

Hi , i am a beginner in AIX. please find my doubt I am calling the below script named test_1 by " sh test_1 | telnet " cmd1="var1=100" echo open $Infahost sleep 1 echo $Infaftplogin sleep 1 echo $Infaftppasswd sleep 1 echo $cmd1 sleep 5 echo $var1 sleep 5 echo exit (11 Replies)
Discussion started by: sam99
11 Replies

8. Solaris

Telnet issue E5500/V480

Our old E5500 was just turned off (planned :rolleyes: ) and the application was moved to a V480. Now if I login to the V480 and try to sudo to root my connection hangs, and I can not telnet to the E5500 after it was powered on again. I get "connection refused". Telnet to this machine was... (5 Replies)
Discussion started by: kjbaumann
5 Replies

9. Windows & DOS: Issues & Discussions

Here's a goofy question...

I was just wondering if there would be any way to port the X Window system to DOS. I know, why do that when its designed for Unix and Linux. However, I have a laptop that for some reason, won't take Linux, but it will take DOS. I don't like the GUI's that I can find on the internet for DOS, but... (7 Replies)
Discussion started by: Shadowmane
7 Replies
Login or Register to Ask a Question
KAS_INTERACTIVE(8)					       AFS Command Reference						KAS_INTERACTIVE(8)

kas_interactive - Enters interactive mode SYNOPSIS
kas interactive [-admin_username <admin principal to use for authentication>] [-password_for_admin <admin password>] [-cell <cell name>] [-servers <explicit list of authentication servers>+] [-noauth] [-help] kas i [-a <admin principal to use for authentication>] [-p <admin password>] [-c <cell name>] [-s <explicit list of authentication servers>+] [-n] [-h] DESCRIPTION
The kas interactive command establishes an interactive session for the issuer of the command. By default, the command interpreter establishes an authenticated connection for the user logged into the local file system with all of the Authentication Servers listed in the local /etc/openafs/CellServDB file for the cell named in the local /etc/openafs/ThisCell file. To specify an alternate identity, cell name, or list of Authentication Servers, include the -admin_username, -cell, or -servers arguments respectively. Interactive mode lasts for six hours unless the maximum ticket lifetime for the issuer or the Authentication Server's Ticket Granting Service is shorter. There are two other ways to enter interactive mode, in addition to the kas interactive command: o Type the kas command at the shell prompt without any operation code. If appropriate, include one or more of the -admin_username, -password_for_admin, -cell, and -servers arguments. o Type the kas command followed by a user name and cell name, separated by an "@" sign (for example: kas, to establish a connection under the specified identity with the Authentication Servers listed in the local /etc/openafs/CellServDB file for the indicated cell. If appropriate, provide the -servers argument to specify an alternate list of Authentication Server machines that belong to the indicated cell. There are several consequences of entering interactive mode: o The "ka>" prompt replaces the system (shell) prompt. When typing commands at this prompt, provide only the operation code (omit the command suite name, kas). o The command interpreter does not prompt for the issuer's password. The issuer's identity and password, the relevant cell, and the set of Authentication Server machines specified when entering interactive mode apply to all commands issued during the session. They cannot be changed without leaving the session, except by using the kas noauthentication command to replace the current authenticated connections with unauthenticated ones. The -admin_username, -password_for_admin, -cell, and -servers arguments are ignored if provided on a command issued during interactive mode. To establish an unauthenticated connection to the Authentication Server, include the -noauth flag or provide an incorrect password. Unless authorization checking is disabled on each Authentication Server machine involved, however, it is not possible to perform any privileged operations within such a session. To end the current authenticated connection and establish an unauthenticated one, issue the kas noauthentication command. To leave interactive mode and return to the regular shell prompt, issue the kas quit command. OPTIONS
-admin_username <admin principal> Specifies the user identity under which to authenticate with the Authentication Server for execution of the command. For more details, see kas(8). -password_for_admin <admin password> Specifies the password of the command's issuer. If it is omitted (as recommended), the kas command interpreter prompts for it and does not echo it visibly. For more details, see kas(8). -cell <cell name> Names the cell in which to run the command. For more details, see kas(8). -servers <authentication servers>+ Names each machine running an Authentication Server with which to establish a connection. For more details, see kas(8). -noauth Assigns the unprivileged identity "anonymous" to the issuer. For more details, see kas(8). -help Prints the online help for this command. All other valid options are ignored. EXAMPLES
The following example shows a user entering interactive mode as the privileged user "admin". % kas interactive admin Password for admin: I<admin_password> ka> PRIVILEGE REQUIRED
kas(8), kas_noauthentication(8), kas_quit(8) COPYRIGHT
IBM Corporation 2000. <> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 KAS_INTERACTIVE(8)