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!
Jerry

---------- 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 success...it 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
TCOM(4) 						   BSD Kernel Interfaces Manual 						   TCOM(4)

NAME
tcom -- multiplexing serial communications interface SYNOPSIS
For 4-port TC-400 series boards: tcom0 at isa? port 0x100 irq 5 com2 at tcom? slave ? com3 at tcom? slave ? com4 at tcom? slave ? com5 at tcom? slave ? For 8-port TC-800 series boards: tcom0 at isa? port 0x100 irq 5 com2 at tcom? slave ? com3 at tcom? slave ? com4 at tcom? slave ? com5 at tcom? slave ? com6 at tcom? slave ? com7 at tcom? slave ? com8 at tcom? slave ? com9 at tcom? slave ? DESCRIPTION
The tcom driver provides support for the Byte Runner Technologies TC-400 and TC-800 series boards that multiplex together up to four or eight EIA RS-232C (CCITT V.28) communications interfaces. Each tcom device is the master device for up to eight com devices. The kernel configuration specifies these com devices as slave devices of the tcom device, as shown in the synopsis. The slave ID given for each com device determines which bit in the interrupt multiplexing regis- ter is tested to find interrupts for that device. The port specification for the tcom device is used to compute the base addresses for the com subdevices and the port for the interrupt multiplexing register. Not all possible configuration options are currently supported (for example, speeds beyond 115200 baud are not currently supported). FILES
/dev/tty?? SEE ALSO
com(4) HISTORY
The tcom driver was written by Jukka Marin. BSD
May 20, 1998 BSD