Conference jamin::pathworks32

187.0. "PPP broke after PW-32 installation" by CPEEDY::COOK (Just say NO to that AccViO! - Java!!!) Wed Mar 26 1997 12:20

    
    After installing PW-32 (and PowerTerm) on my NT 4.0 (SP2)
    system at home, I then encountered a problem in using my
    already existing PPP/dialup setup.  The two symptoms were:
    
    (1) After completing the PPP-session authentication to the
    terminal-server,  I didn't see the now-familiar msg saying
    "authenticating you on the network..." etc.  The modem-lights
    indicated that carrier was established, but I saw no read/write
    indications that any data was moving.  I next checked that status
    of the dialup-connection and saw that no protocol(s) had been
    negotiated.   After poking around and trying to re-dial, I saw
    new messages like '...no more buffers...', etc.  Sorry, I didn't
    write down the exact text of these msgs.
    
    As luck would have it, I guessed at a workaround, and it cleared
    up the problem.  The workaround was to *Remove* the LAT-protocol
    from the system (via the network/control-panel option).  After doing
    that (and rebooting), my subsequent attempt to make a PPP-dialout
    connection worked.
    
    You may be wondering why I had chosen LAT protocol during my
    PW-32 installation?  (No good reason...just because it was there.)
    
    Here's some more gory detail:
    
    The machine contains both an ethernet-card, and a modem, and both
    were configured and working in NT.  (I have a 3-mode ethernet network
    at home.)  TCP/IP (and NETBEUI, and probably even IPX) are configured
    as transports.
    
    Here's how I did the PW-32/PowerTerm installation:
    
    I chose 'custom' install for PW-32, selecting LAT and dial-up support,
    but *not* selecting DECNet support.  That all appeared normal...the
    machine rebooted as expected after the transports reconfigured
    themselves.  Then I installed PowerTerm...no reboot was asked about
    so the machine was not rebooted.  I did not ever attempt to use/test
    any of the new functionality.  I left the machine powered up.
    
    It was the next evening, when I tried to make/use the PPP support,
    that I encountered the problem.
    
    My (wild) guess is that maybe LAT got (erroneously?) bound to dialup
    support and that removing it fixed something???  Hell, I don't know.
    
    I'm just happy to have my PPP connections working again...
    
    						Dave
    
    P.S. Is this QAR material?
    

> I chose 'custom' install for PW-32, selecting LAT and dial-up support,
> but *not* selecting DECNet support.

	By "dial-up support" do you mean "Remote Access"?  Did you read 
	the release note that says you must select DECnet when you select
	"Remote Access" for NT 4.0?

    
    >>>By "dial-up support" do you mean "Remote Access"?
    	
    	Yes, no doubt that's what I meant to say.
    
    >>>Did you read the release note that says you must select DECnet 
    >>>when you select "Remote Access" for NT 4.0?
    
    	No.  (But, if there is a hierarchy of x depends on y, one would
    	  have hoped that the install-process would have enforced it
    	  and just notified me.  But, I guess that's why there's a
    	  warning about custom-installations being restricted to
    	  'advanced/informed' users...and, clearly, I don't qualify.)
    
    
    	My real intent was to just install enough to get PowerTerm
    	working over dialup, and when I tried installing *only*
    	PowerTerm, it wouldn't function.  Again, it's my fault for
    	not clearly reading/re-reading the instructions in one of these
    	notes about PowerTerm's dependencies and how get it's
    	Telnet-functionality working.  (And, I chose LAT just as an
    	afterthought...because it was there.)
    
    	The basic intent of my base note was really just a heads-up
    	to point out some non-robustness of custom-install, etc, but
    	your group may be well aware of the those flaws.
    
    
    						Dave
    
    

    
    To rectify my own error, here is a pointer to the recommended way
    to get base-support for PowerTerm, assuming that is the *only*
    support that is wanted:
    
    See note 89.1 in this conference, which says base-support for PowerTerm
    is available by choosing *none* of the 3 options under the custom-install
    option.
    
    I haven't tried it yet.  (And, to be safe, anyone else trying to
    install same should probably consult that note for details.)
    
    
    						Dave

    re. .-1 
    
    FWIW, that's what I did; I "deselected/unhighlighted" DECnet (click on
    it once) - then click Next.  Selected LAT and VT320.  After that
    install completed, I installed PowerTerm and have used both VT320 and
    PowerTerm successfully (guess I was just lucky, eh?)...
    
    Paul