Telnet Users via VPN - Remote Disconnects

[Laurie_2]

Hi All,

My end-users via VPN get logged into Unix and then get a remote disconnect. This happens randomly (Yuck).

And then if they try to re- telnet in it say:

Can't Connect

We have no VPN connect errors.
Our networking person thinks
it the unix (black sheep).

We have DSN commented out in
the nsswitch.conf file.

In our resolv.conf file
we have our name servers
define. Local users no problems with telnet (QVT).

In syslog we get these errors:

getpid: peer died: Error 0
telnetd[18219]: Error checking child termination status: erro
r 4: Interrupted system call

Any clues...
Laurie

[Chris Vail]

Without a network sniffer, and someone who knows how to use it, you probably won't be able to convince your network guy that the problem is not the unix box. The 'remote peer disconnected' comment in the syslog indicates that the problem came from outside the unix box.

If internal (non-VPN) users have no trouble, this is another argument in the favor of this. But without a network trace that specifically catches a terminated connection, you won't find your smoking gun. The fact that this happens randomly only adds to the frustration.


Good Luck
Chris

[Jeff Schussele]

How are users authenticating at your network - CheckPoint? Are they checking the logs on the FW? Are the users coming OUT of a FW before coming into your network? Are all FWs encountered up to date w/IP-SEC firmware? Much too much going on here to quickly point the finger at any ONE thing!
This is a typical network admin ploy.....

Rgds,
Jeff

[harry d brown jr]

Laurie,

http://www.dutchworks.nl/htbin/hpsysadmin?h=3&dn=63483&q=getpid:%20peer%20died&fh

found it in this thread from Stefan Farrelly:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc489663ce855d511abcd0090277a778c,00.html

live free or die
harry

[Helen French · Accepted solution]

Hi Laurie,

Check this out:

http://us-support.external.hp.com/cki/bin/doc.pl/sid=fc1a60e4113b2a5c85/screen=ckiDisplayDocument?docId=500000000092173

HTH,
Shiju

[Dan Rosen]

Laurie - we see the same thing here, but what we found is that you are more likely to see a disconnect over Broadband (Cable or DSL) than our modem users.

My BELIEF (and I am looking for evidence and a way to fix it) is the fact that broadband is not "always on". DSL still establishes and break connections throughout a session. The reconnect time is only like ~200 milliseconds, but it is enough for telnet to be unhappy and terminate the users sessions.

I am looking to change a setting so that telnet has a longer timeout for non-connection.