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

Conference utrop1::linkworks_v3

Title:LinkWorks V3.0 Notes Conference
Notice:LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues
Moderator:tacklr.apd.dec.com::TACK_Lm::TACK_L
Created:Tue Jun 28 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:8338

2136.0. "OS-Login for NT 3.51 not working" by FRAIS::MSCHULZ (Michael Schulz) Thu Feb 20 1997 14:50

I installed two demo-systems for LinkWorks:
System A - Intel: Windows NT 3.51 (Service Pack 4) 
		  Oracle V7.2.2
		  LinkWorks V3.0.8
System B - Intel: Windows NT 4.0
		  SQLServer V6.5
		  LinkWorks V3.0.8

On System B OS-Login works, on System A not (Error-message like "You cannot 
login now - try later").

I enabled OS-Login on both systems as mentioned in the Release Notes 3.0.8 
(Dec96).

Is this feature available only for NT 4.0 / SQLServer 6.x ?

Michael



T.RTitleUserPersonal
Name
DateLines
2136.1IJSAPL::MONNINK_HFri Feb 21 1997 07:265
    Michael,
    
    Running this at home and it works fine, so 3.51 should work.
    
    Han
2136.2suppdc.uto.dec.com::PETERS_MMon Mar 03 1997 13:014
Just a stupid question. Did you install the December version
also on your Windows NT 3.51 systems?

Martin
2136.3FRAIS::MSCHULZMichael SchulzWed Mar 05 1997 10:205
Yes, I did (NTIORA.EXE from IJSAPL::DISK$LNX:[KIS.NTX308.DEC96REL]).

I tried it (OS-Login) yesterday again in different ways without any success.

Michael
2136.4UTROP1::elec6.uto.dec.com::HIELKEMA_MWed Mar 05 1997 13:027
I got the message  "You cannot login now - try later" also.
I forgot to give the group to which the user is added the Access Right
"Log on locally". After I have done that, it was OK.
Have you checked that?

Minne

2136.5FRAIS::MSCHULZMichael SchulzWed Mar 05 1997 14:224
I've checked it. Group to which user is assigned has the right "Log on locally".

Michael

2136.6Grant 'Act as part of the operating system' to the group 'op'EPS::ESTESThu Mar 20 1997 20:5939
    We saw this problem as well with the December release.  The fix is in
    the release notes!                             
    
    We had not granted the "Act as part of the operating system" priviledge
    to the the 'op' group.  See item 1 below from page 51 of the release
    notes. 
    
    Two additional notes:  This is an "Advanced" priviledge and you must
    check the "Show advanced user rights" check box. If 
    the LinkWorks service is running you must restart it after granting 
    this right. 
    
    Regards
    
       Stu Estes 
    
    From page 51 of the December release notes.
    
    1 Use the Windows NT User Manager For Domains to add the Access Right
    'Act as part of operating system' to the user group op.
    2 Add a new user. Do not require him to change his password the first
    time he logs in.
    3 The group to which the user is added must have the Access Right Log
    on Locally.
    4 Restart the Windows NT server.
    5 On the client, add a new user with the same login ID as the Windows
    NT user. At this point the login ID in LinkWorks, the OS-Login ID in
    LinkWorks, and the Windows NT login ID of the user should all be the
    same.
    6 Commit changes and exit the system administratation.