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

Conference jamin::pw95ift

Title:	PATHWORKS for Windows 95
Notice:	PWW95 1.0A Available -- See notes 3.39 and 8.7
Moderator:	JAMIN::SYSTEMROM

Created:	Thu Nov 17 1994
Last Modified:	Thu Jun 05 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	646
Total number of notes:	2900

609.0. "Changing Password after Migration happens, 95 clients" by ACISS2::BRANSTEIN (Never mess with another man's rhubarb) Fri Jan 24 1997 14:51

    I have a customer that will be migrating from Pathworks V4 server to
    Pathworks V5.0D eco3 server.  They have many Windows 95 systems.  They
    also have various Windows 3.1 clients ranging from V4.1 to V6.0.  The
    VMS Usernames are in the format (Lastname_FM), where F= Firstname
    Initial and M=Middle Intitial.  The WIN95 users are participating in a
    NT DOMAIN where their Account names are stricly Corporate Intitials. 
    We have been able to run tests against a test server.  When the initial
    LM account is created by PWRK$UPGRADE procedure the password is not 
    copied from VMS to the account.  I have not been able to successfully 
    change the password from the WIN95 client via the DOS Command 
    NET PASS \\Server.  How can the WIN 95 user change their password? 
    Also, what is the password initially set to?
    
    BTW, the LM account is created with INITIALS HOSTMAPPING to the VMS
    ACCOUNT.  And the Server is set to Backward compatible.
    
    Any help would be appreciated.  Converting this weekend.
    
    Regards,
    Gary

T.R Title User Personal
Name Date Lines

609.1 VMSNET::P_NUNEZ Fri Jan 24 1997 16:18 26

T.R	Title	User	Personal Name	Date	Lines
609.1		VMSNET::P_NUNEZ		`Fri Jan 24 1997 16:18`	26
	NET PASSWORD \\server needs the original password, which you don't have. And I don't think the original password is known (it might even be null?). This issue is one big reason why there is a backwards compatability mode - but bcm only helps clients running DEC basic redir. You may be stuck with initially setting the lanman account passwords manually for win95 users. It wouldn't be too difficult to write a dcl hack to do it for you. You could send the output from $ NET USER to a file and then parse it to pass the usernames to the command: $ define/user sys$output userlist.txt $ net user $ open/read users userlist.txt $rloop: $ read/end=done users username $ newpassword = f$extract(0,14,username) $ NET USER 'username' 'newpassword' $ goto rloop $done: Of course you could get real creative with newpassword... Paul

    
    NET PASSWORD \\server needs the original password, which you don't
    have.  And I don't think the original password is known (it might even
    be null?).  This issue is one big reason why there is a backwards
    compatability mode - but bcm only helps clients running DEC basic
    redir.  
    
    You may be stuck with initially setting the lanman account passwords
    manually for win95 users.  It wouldn't be too difficult to write a dcl
    hack to do it for you.  You could send the output from $ NET USER to a
    file and then parse it to pass the usernames to the command:
    
    	$ define/user sys$output userlist.txt
    	$ net user
    	$ open/read users userlist.txt 
        $rloop:
    	$ read/end=done users username
    	$ newpassword = f$extract(0,14,username)
    	$ NET USER 'username' 'newpassword'
    	$ goto rloop
    	$done:
    
    
    Of course you could get real creative with newpassword...
    
    Paul