Hi,

I'm administraiting the HPUX 11i system on HP rp5400 server.
I've got a problem after my user activity. He accidently pasted a lot of 
text from his clipboard to the telnet terminal window. This caused that 
nobody is able to telnet or ftp the server. Just after connecting the 
server I receive a message 'Your telnet connection has terminated'. Syslog 
does not notice telnet trys. Ftp try gives 'Connection closed by foreign 
host' and 'Ftp: Exit on signal 11' in syslog.log.
What's interesting, when I telnet another HPUX server (same as main, the 
same network segment), I can telnet my server from it. But I can't telnet 
my server from any windows mashine.

I would appreciate any help.
Regards,
Rafi

dkoleary@attbi.com wrote:
>>What's interesting, when I telnet another HPUX server (same as main, the 
>>same network segment), I can telnet my server from it. But I can't telnet 
>>my server from any windows mashine.
> 
> 
> Your situation sounds *really* squirrelly.  There's nothing
> short of a system crash that a user should be able to do to mess
> up the system.  Was your cohort root when he pasted all that 
> stuff into the telnet window?  That might explain the root cause
> of the problem (no pun intended).
> 
> Your last point there is probably pointing to the issue.  I am 
> assuming your windows systems are not on the same network segment
> as the UNIX systems.  If you can telnet into the broke system 
> from another one on the same network segment but cannot from
> a system on a different network segment, it points to a routing
> issue.  Check your default route on the broke box; I'm betting
> it got messed up during the paste debacle.
> 
> HTH;
> 
> Doug
> 
> --------
> Senior UNIX Admin
> O'Leary Computer Enterprises
> dkoleary@attbi.com (w) 630-904-6098 (h) 630-248-2749
> resume:  http://home.attbi.com/~dkoleary/resume.html
sounds like a buffer overflow to me, DOH!, are the patches for telnet up 
to date?

Alan Johnson <adjtech@ulster.net> wrote:
> sounds like a buffer overflow to me, DOH!, are the patches for telnet up 
> to date?

Certainly could be; but, I would think that would mess up either the 
single telnet session, which apparently it did, or *all* telnet sessions,
which, according to the OP, it didn't.

That being said, patches are the first thing HP support is going to 
ask about.

--------
Senior UNIX Admin
O'Leary Computer Enterprises
dkoleary@attbi.com (w) 630-904-6098 (h) 630-248-2749
resume:  http://home.attbi.com/~dkoleary/resume.html

Hi,
The problem seems to be fixed.
In /etc/hosts there was an alias for loopback 127.0.0.1 different then a 
hostname.
It works now, although I still don't understand what it really was.
(By the way, The windows mashine I couldn't telnet from is also on the same 
network segment).

Best Regards,
Rafi

On Tue, 22 Jul 2003 16:39:34 GMT, <dkoleary@attbi.com> wrote:

>> What's interesting, when I telnet another HPUX server (same as main, the 
>> same network segment), I can telnet my server from it. But I can't 
>> telnet my server from any windows mashine.
>
> Your situation sounds *really* squirrelly.  There's nothing
> short of a system crash that a user should be able to do to mess
> up the system.  Was your cohort root when he pasted all that stuff into 
> the telnet window?  That might explain the root cause
> of the problem (no pun intended).
>
> Your last point there is probably pointing to the issue.  I am assuming 
> your windows systems are not on the same network segment
> as the UNIX systems.  If you can telnet into the broke system from 
> another one on the same network segment but cannot from
> a system on a different network segment, it points to a routing
> issue.  Check your default route on the broke box; I'm betting
> it got messed up during the paste debacle.
>
> HTH;
>
> Doug
>
> --------
> Senior UNIX Admin
> O'Leary Computer Enterprises
> dkoleary@attbi.com (w) 630-904-6098 (h) 630-248-2749
> resume:  http://home.attbi.com/~dkoleary/resume.html
>