[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

4153.0. "Old accounst/ext. auth" by STKAI1::PTORLIND () Wed Feb 12 1997 14:41

    Hi !!
    
    We have gotten a strange problem with the new external authentication 
    feature .
    
    Config is this, 1 NT3.51 server PDC, 1 PW V5.0E Member, running AVMS v7.1 
    and 1 PW V5.0D Member. The 5.0E server used to run V5.0D
     
    When setting up the extauth flag to a vms user on the V5.0E server that
    is already Lanman hostmaped, and then trying to do a 
    set host to that system the Opcom message states ther is no such user.
    
    All the accounts has been created from the beginning with the
    $net user   /add   command from the vms prompt.
    
    What we have found out is this, all the old lanmanager accounts, we
    have to do a set host and specify the username with uppercase
    characters, otherwise it says no such user on the vms console.
    If we create a new account from the 5.0E server with the 
    $net user  /add   command. It works fine with either uppercase or
    lowercase characters in the username.
    
    If we create a new lanmanager account from the 5.0D server with 
    $net user  /add     
    We get the problem with that we have to specify the vms username 
    with uppercase characters.
    
    So...
    1. All 400 user accounts that has been created with the $net user  
       /add from the beginning dont work as supposed to.
    2. All accounts that is created now, new ones, with $net user   /add
       from the V5.0D server works like the old ones as stated in 1.
    3. The only accounts that work with external authentication are 
       the new ones we create with $net user   /add   on the V5.0E server.
    
    
    My question is, i hope this is not the way it is supposed to be ??
    
    
    
    Anyone ??
    
    
    Per Torlind / PATHWORKS support, Sweden
    
    
T.RTitleUserPersonal
Name
DateLines
4153.1CorrectionBULAN::peoto.soo.dec.com::ptorlindThu Feb 13 1997 06:5124
Hi again !!

Forget .0, customer lied once again. After some 
investigation it turned out to be this....

He pushed in a new V5.0E server into the domain
with an NT 3.51 PDC. All user accounts was replicated.
At that time he had already created about 200 vms user 
user accounts so they were host mapped.
But then he created vms accounts same username as the
lanmanager accounts and thought they would be hostmapped
automatically. NOT. So the one that had problem with 
External Auth. was the one that had hostmap=pwrk$default.

So, finally to the last question. Is there any NET command
or with lmuser tool to modify the accounts so they are host
mapped with the vms user account. Admin interface
is not an option since customer wants to make a batch job
to fix this.


Anyone ??

Per Torlind / PATHWORKS support, Sweden
4153.2VMSNET::P_NUNEZThu Feb 13 1997 09:4222
    
    As long as you have the following lines in lanman.ini [vmsserver]
    section:
    
    applyhostmapcomment = yes
    hostmapmode = if_exist_else_default   ! (other values are valid as well)
    
    then you can set the Comment field of the LANMAN account to
    HOSTMAP=<uafAcct> and it'll set the host mapping for you.  Note that
    the actually setting of the hostmap field doesn't occur until you zoom
    on the account in ADMIN or the user establishes a new _session_ with
    the server.
    
    For a new user:
    
    	$ NET USER PTORLIND PASSWORD /COMMENT:"HOSTMAP=PTORLIND" /ADD
        
    or for an existing user:
    
    	$ NET USER PTORLIND /COMMENT:"HOSTMAP=PTORLIND" 
    
    Paul
4153.3GREATBULAN::peoto.soo.dec.com::ptorlindThu Feb 13 1997 12:0420
Hi !! 


YES, thats it. I had been trying the 
$net user ptorlind /comment:"hostmap=ptorlind"

But it turned out to be parameter applyhostmapcomment
in lanman.ini that was the missing part. I even had
the pw server administrator guide dusted off from 
the book shelf here and looked in it. Missed that one.

Great, thanks, we will satisfy one more customer.




Regards.


Per Torlind / PATWHORKS support, "snowing" Sweden