From owner-freebsd-bugs  Tue Mar 25 19:30:07 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA10476
          for bugs-outgoing; Tue, 25 Mar 1997 19:30:07 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA10460;
          Tue, 25 Mar 1997 19:30:04 -0800 (PST)
Date: Tue, 25 Mar 1997 19:30:04 -0800 (PST)
Message-Id: <199703260330.TAA10460@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Mike Pritchard <mpp>
Subject: Re: bin/2256 PPP doesn't close w/NT client
Reply-To: Mike Pritchard <mpp>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/2256; it has been noted by GNATS.

From: Mike Pritchard <mpp>
To: freebsd-gnats-submit
Cc:  Subject: Re: bin/2256 PPP doesn't close w/NT client
Date: Tue, 25 Mar 1997 19:25:12 -0800 (PST)

 Feedback from the originator:
 
 Greg Bedrossian wrote:
 > 
 > Hello Mike,
 > 
 > Thank you for following up on this strange issue.
 > 
 > The problem still persists. I have had to set up an NT server to  
 > accommodate NT users who need to dial in.
 > 
 > The version of FreeBSD I am using is 2.1.5.
 > 
 > I have not tried a newer version as of yet. What is available?
 > 
 > To add to my problems,  the scripting tool within Win95 does not  
 > negotiate a correct sequence when loging into our FreeBSD server to  
 > get a ppp connection. It has to be stepped. I overcame this problem  
 > by adding 1sec delays in between the commands. However,  at  
 > "endproc" it will hang there waiting for a response from the FreeBSD  
 > host until you press continue in the dialogue box of the script's  
 > login sequence. I am being told by subscribers that they don't seem  
 > to have this problem using the same script with other ISPs.  It  
 > seems to me that pppd has a timing problem at the I/O side of it.  
 > This could explain why it does not shutdown properly with NT clients  
 > and now this other problem of loging in via a script! Though, I am  
 > not sure of any of it.
 > 
 > This is presenting a serious embarrassment for me as I am losing my  
 > subscribers. Yet I just cannot see where the problem may be, as so  
 > much of it works well, and there are no problems reported by NeXT  
 > users.
 > 
 > 
 > Regards
 > 
 > 
 > kgb