From owner-freebsd-ports  Fri Dec 20 06:20:05 1996
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id GAA21556
          for ports-outgoing; Fri, 20 Dec 1996 06:20:05 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id GAA21542;
          Fri, 20 Dec 1996 06:20:03 -0800 (PST)
Resent-Date: Fri, 20 Dec 1996 06:20:03 -0800 (PST)
Resent-Message-Id: <199612201420.GAA21542@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-ports
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org,
        Received:(from nobody@localhost) by.freefall.freebsd.org.id.GAA21474;Fri; (8.8.4/8.8.4);,
        20 Dec 1996 06:18:50.-0800 (PST)
Message-Id: <199612201418.GAA21474@freefall.freebsd.org>
Date: Fri, 20 Dec 1996 06:18:50 -0800 (PST)
From: greg@gcsl.co.uk
To: freebsd-gnats-submit@freebsd.org
X-Send-Pr-Version: www-1.0
Subject: ports/2256: PPP process on port will not close when an NT user has diconnected after a session.
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         2256
>Category:       ports
>Synopsis:       PPP process on port will not close when an NT user has diconnected after a session.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-ports
>State:          open
>Class:          support
>Submitter-Id:   current-users
>Arrival-Date:   Fri Dec 20 06:20:01 PST 1996
>Last-Modified:
>Originator:     Greg Bedrossian
>Organization:
General Computer Systems
>Release:        FreeBSD 4.4
>Environment:
FreeBSD popeye.gcsl.co.uk 2.1.5 RELEASE FreeBSD 2.1.5 RELEASE #0:
Thu Nov 21 16:05:56 1996 root@popeye.gcsl.co.uk:/usr/src/sys/compile/
POPEYE
>Description:
POPEYE is a pop server running several serial ports on PPP. When a 
customer dials in from an NT machine to get a PPP connection, after he
has finished and signs off, the particular PPP port stays open with the 
pppd-x process still running. It has to be killed manually otherwise the
next caller is confronted with a security violation and can enter the 
system without a login and password. This does not happen with Win95 or 
other type of OS dialing in.
>How-To-Repeat:
Well - as above!
>Fix:
Unknown as of yet. Several attempts to re program the modems has not so
far yielded fruit. The problem is consistant. It happens every time an
NT user dials in.

WE ARE STUMPED! ANY SUGGESTIONS???
>Audit-Trail:
>Unformatted: