[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::windows-nt

Title:Windows NT
Notice:See note 15.0 for HCL location
Moderator:TARKIN::LIN.com::FOLEY
Created:Thu Oct 31 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6086
Total number of notes:31449

5617.0. "Dial Up networking problem with NT 4.0" by TUXEDO::FRIDAY (DCE: The real world is distributed too.) Tue Jan 28 1997 10:22

    I'm running Windows NT 4.0 on my Starion 942 at home
    and am having problems getting Dial Up Networking
    to work as smoothly as it should.
    
    I've successfully set it up so that it dials
    my ISP (ultranet).  However, after making
    the connection the only way I can avoid dropping
    the connection is by having a terminal window
    pop up, into which I have to type responses for
    login: and password:.  Then it goes on to
    validating name and password and logging onto the
    network, and everything is fine.
    
    However, I want to avoid the terminal window, but
    don't seem to be able to.  In the options selection
    I've tried all three possibilities: None, terminal
    window (which works, but which I don't want) and
    Run this script.
    
    I've looked at the script and the comments in it
    imply that it will automatically supply whatever
    name and password I've previously told Dial Up
    Networking to use.  But making this selection
    doesn't work either.
    
    I've probably mis-configured something, but
    I don't know what it is.  The error messages
    I get when the connection gets dropped are not
    particularily helpful.
    
    When I run Windows95 on my system Dial Up Networking
    never brings up a terminal window.  I want NT 4.0
    to work the same way.
    
    Suggestions are appreciated.
    
    Thanks in advance,
      Rich
T.RTitleUserPersonal
Name
DateLines
5617.1PYRO::RONRon S. van ZuylenTue Jan 28 1997 11:164
    You need to create (or modify) a script that is appropriate for your ISP.
    There is no "standard" login sequence.
    
    --Ron
5617.2BHAJEE::JAERVINENOra, the Old Rural AmateurTue Jan 28 1997 12:5619
    I think there are some sample scripts for the usual cases (Compuserve,
    "standard" Unix whatever that is, etc.). I believe Ultranet uses Alphas
    - probably Unix but I don't know for sure). You can make the script
    supply the password you've define for the dial-up session.
    
    A simple sample script for Unix looks like this:
    
    proc main
    
       waitfor "login:"
       transmit $USERID, raw
       transmit "^M"
    
       waitfor "Password: "
       transmit $PASSWORD, raw
       transmit "^M"
    
    endproc
    
5617.3DECserver scriptODIXIE::SIMPSONTPC = world's biggest con job!Wed Jan 29 1997 05:22109
    Here is the script that I use to login via a DECserver/PPP.  I
    understand what you are saying about the terminal window.  I can't
    figure out how to stop the terminal window from popping up while the
    script runs, either...
    
    ;
    ; This is a script file that demonstrates how
    ; to establish a PPP connection with a DECserver host
    ;
    ; A script file must have a 'main' procedure.
    ; All script execution starts with this 'main'
    ; procedure.
    ;
    
    ; Main entry point to script
    ;
    proc main
    
       ; set screen keyboard off
       ; Change these variables to customize for your
       ; specific Internet service provider
    
       integer nTries = 3
    
       ; This is the password prompt and timeout values
    
       string szPWprompt = "#"
       integer nPWTimeout = 3
    
       ; This is the prompt once your password is verified
       string szLoginPrompt = "username"
    
       ; This is the prompt once your username is entered
       string szLocalPrompt = "Local>"
    
       ; DECserver username
       string szUserName="SIMPSON"
    
       ; DECserver password
       string szPassword="password goes here"
    
       ; This connects to the DECserver PPP service
       string szConnect = "Connect PPP"
    
       ; -----------------------------------------------------
    
       ; Delay for n seconds first to make sure the
       ; host doesn't get confused when we send the
       ; carriage-return.
    
       delay 1
       transmit "^M"
    
       ; Attempt to login at most 'nTries' times
    
       while 0 < nTries do
    
          ; Wait for the remote password prompt before entering
          ; the password, timeout after x seconds
    
          waitfor szPWprompt then DoLogin 
            until nPWTimeout
          ; no password prompt, exit script
          goto BailOut
    
    DoLogin:
          ; We have the prompt, now send the password
    
          transmit szPassword
          transmit "^M"
    
          ; Wait for the username prompt, then send username information
          waitfor szLoginPrompt then DoUserName
            until nPWTimeout
    
    TryAgain:
          transmit "^M"        ; ping
          nTries = nTries - 1
    
    
       endwhile
       goto BailOut
    
    DoUserName:
       transmit szUserName
       transmit "^M"
    
       ; Wait for the username prompt, then send username information
       waitfor szLocalPrompt then ServiceConnect
       until nPWTimeout
    
    ServiceConnect:
       transmit szConnect
       transmit "^M"
    
       goto Done
    
    BailOut:
       ; Something isn't responding.  Halt the script
       ; and let the user handle it manually.
    
       set screen keyboard on
       halt
    
    Done:
       ;delay 3
    
    endproc
    
5617.4MEIS::MCNULTYFri Jan 31 1997 10:5415
    I dial into Ultranet from NT 4.0 without using a
    (after connection) terminal window.
    
    I will check the details tonight but I'm sure the Script
    option is set to "None" and under Server tab set to
    "PPP - Windows NT, Windows 95 Internet ???" (I forget the exact
    wording here but there are other options available including SLIP).
    Network protocols set to just TCP/IP with (obviously ?) dynamic IP
    address assignment.
    
    Reply or drop a line if you are still having problems and I will
    check/send you my exact settings.
    
    -gerry
     
5617.5PYRO::RONRon S. van ZuylenFri Jan 31 1997 11:048
    It depends on the ISP.  Some use real PPP authentication (PAP,
    CHAP, etc.) and some use interactive terminal style login.
    
    If it needs interactive terminal login, you'll need to make a script if
    you want it automated.  And, yes, the terminal window will pop up while
    it runs.  (Why is this a big deal?)
    
    --Ron
5617.6CAMPY::ADEYIs there a &#039;Life for Dummies&#039;?Fri Feb 28 1997 06:5810
    Before I added multiple numbers in the Dial Up Networking Monitor,
    whenever I would fire up a client while not connected, Dial Up
    Networking would automatically come up and ask if I wanted to dial
    the number. Now it doesn't do this anymore (since I added more numbers)
    and I can't figure out how to get this capability back. 
    
    Any help is appreciated.
    
    Ken....
    
5617.7No response from after dialup terminalVMSNET::M_MACIOLEKFour54 Camaro/Only way to flyThu Mar 06 1997 13:5413
    What are some of the possible causes of the following:
    
    NT4.0, fire up dial up networking, call the PPP server, get the
    "after dialup terminal" deal, but I can't enter anything.  No
    pound sign, no nothing.  I can go to dos and run procom with NT4.0.
    
    Boot up NT3.51 and it works fine.
    
    I'm going to try and run a script from .3 I think to see if I can
    avoid the problem.... but I'd like to figure out what the problem is.
    
    Regards,
    MadMike
5617.8VMSNET::M_MACIOLEKFour54 Camaro/Only way to flyWed Mar 12 1997 11:3928
    I used the script mentioned in .3, modified for my ppp server.
    All I get is a pop up box after a few seconds that says
    
    "The script has halted".
    I press "ok" and...  the regular error I was getting before pops up
    (error 630, or 619)... all ports connected or something.
    
    Right now I'm dialed in using nt3.51 ras.  Same modem, same ppp
    service, and all is fine.
    
    If I go to 4.0, it croaks.  I've tried generic modem, hayes accura
    14400, 144 + fax144... let NT select the hardware, deinstalled,
    reinstalled, reinstalled RAS, pop into hyperterm and dial in ok, pop into
    procom and call the PPP server.... but no RAS, or dialup networking.
    
    I've also tried a different modem, and lowered the speed on both...
    
    The thing that is bugging me is nt4.0 can see 3 of my disks.
    NT 3.51 can't see one of my 1.2GB drives... and I'm being slightly
    cautious here...
    
    I can't find enough information about the dialup routine to be able
    to figure out where the goof up is, like how does the hand off to/from
    the after dial terminal happen, what program and/or DLL's are in use...
    
    MadMike