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

Conference noted::pwv50ift

Title:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:CPEEDY::KENNEDY
Created:Fri Dec 18 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4319
Total number of notes:18478

4139.0. "$NET LOGON security problem?" by STKAI1::BLUNDBERG (It's the monster!!!) Mon Feb 03 1997 06:49

    I think I'm going crazy :-)
    
    If someone can give some troubleshooting hints on this strange problem
    I'd be grateful since right now I'm stuck.
    
    A customer has upgraded his server to V5.0E and is now able to log in
    to his LAN Manager accounts with ANY password.
    I logged on to the customers system and tried it out and I just
    couldn't believe it but he was right.
    
    When I did the following thing from VMS-prompt and specified an
    incorrect password on a number of admin-privilegied accounts including 
    ADMIN itself I was successfully logged on even though I typed an
    incorrect password.
    
            $net logon admin
            Type your password: <incorrect password>
            The server \\ABY successfully logged you on as admin.
            Your privilege level on this domain is ADMIN.
            The last time you logged on was 01-23-97 09:00AM.
    
    What could cause this kind of strange behaviour?
    
    The questions never stop coming do they?
    
    Regards
    
    Bjorn
                                                    
T.RTitleUserPersonal
Name
DateLines
4139.1AH YEAH BUTSIOG::FITZMAURICEMon Feb 03 1997 08:4013
    
    Yes, even through previous versions you could do this at a OpenVMS
    level provided you were logged into OpenVMS with a suitable 
    privileged account such as SYSTEM. I allways assumed it was
    a feature ?
    
    If you attempt the logon as you describe from a client pc it
    will not allow you connect without the proper password. So really
    it's not a big issue right ?
    
    Eamonn Fitzmaurice,
    
    
4139.2Still confused.STKAI1::BLUNDBERGIt&#039;s the monster!!!Mon Feb 03 1997 09:3125
    Strange...
    
    my VAX/VMS V6.2 V5.0E server does not work like that
    
    $set proc/priv=all
    $net logon admin
    Type your password: <incorrect password>
    
    Error 86 has occurred.
    The network password entered is incorrect.
    $
    
    If I log on with the correct password it works OK
    
    $net logon admin
    Type your password: <correct password>
    The server \\GUMMAN successfully logged you on as admin.
    Your privilege level on this domain is ADMIN.
    The last time you logged on was 02-03-97 02:00PM.
    $
    
    Now I'm really confused
    
    Bjorn
    
4139.3UTRTSC::EISINKNo Kipling apes todayMon Feb 03 1997 13:322
    and what about putting everything on the command line?
    
4139.4Normal behaviour?STKAI1::BLUNDBERGIt&#039;s the monster!!!Tue Feb 04 1997 03:027
    Told the customer that it's what to be expected from this product
    and he bought it...seems like he's planning a merge to Windows NT like 
    everybody else.
    
    Thanks for your help
    
    Bjorn
4139.5You wont believe this...VMSNET::P_NUNEZTue Feb 04 1997 14:3214
    Bjorn,
    
    I know why you got the error:
    
    Error 86 has occurred.
    The network password entered is incorrect.
    
    you GUEST account password isn't null.  Honest to god.  Try it.  Go
    back to the system and reproduce the error, then do $ lmuser -mp ""
    guest, then try to logon again as admin with an invalid password...
    
    Goofy, eh?
    
    Paul
4139.6PATRLR::MCCUSKERWed Feb 05 1997 14:372
Not that goofey actually.  We use the guest account frequently to query the
server for information.  Thats why we need it to have a NULL password.