[cvsnt] Re: sspi protocol problem!!

Raheel softwarengineeer at gawab.com
Mon Sep 13 14:12:44 BST 2004


Hi Erik, thank you so much. I just can't believe that the problem was in defining my cvsroot. Before, i define it like:
Set cvsroot = :sspi:server_address:/repos_prefix

and whenever i did cvs login, it displays:

Logging in to :sspi:bob at server_address:2401:/test
CVS password: ******

and i thought that it always getting user id from currently logged-in user from the client machine. hoooof!!!! What the nightmare it was!!! At least i save my butt.

Thanks to anyone who helped me. 

Raheel.


  ----- Original Message ----- 
  From: Warren, Erik 
  To: Raheel ; cvsnt at cvsnt.org 
  Sent: Monday, September 13, 2004 5:25 PM
  Subject: RE: [cvsnt] Re: sspi protocol problem!!


  If you are authenticating against a user ID local to the server then
  you may need to set your cvsroot on the client as:
  (if "bob" is the user id, "ralph" is the server and "ourcode" is the repository)
  CVSROOT=:sspi:bob at ralph:/ourcode

  Using this format for sspi requires that you login to cvs the first time you connect.
  All subsequent connections will use the cached info.

  Erik W. Warren 
  Sr. Engineer - Flt. Ops. Engineering 
  Delta Air Lines 
  Dept. 088 
  P.O. Box 20706 
  Atlanta, GA 30320-6001 
  Ph (404) 715-7229 
  fax (404) 715-7202 
  erik.warren at delta.com 

    -----Original Message-----
    From: Raheel [mailto:softwarengineeer at gawab.com]
    Sent: Saturday, September 11, 2004 2:48 AM
    To: Warren, Erik; cvsnt at cvsnt.org
    Subject: Re: [cvsnt] Re: sspi protocol problem!!


    Thanks Erik. 

    I did that exactly as you told me, but still i am getting
    "Authentication protocol rejected access" error when try to login. I also
    try it with "local users instead of domain users" option unchecked but with
    no luck. Its really frustrating for me now why I am not getting thru it.
    There is a firewall installed at my client side (cvs clients) and our cvs
    server domain is different from where we are currently at, i.e. cvs clients.
    But the error message indicates that it has something to do with user's
    rights on server machine. The user that i am using to connect to cvs server,
    is currently in administrators group and also I issue the right that you have 
    mentioned in ur post to the same user.

    still waiting for some light ...!!

    Raheel.

----------------------------------------------------------------------------



    ----- Original Message -----
    From: "Warren, Erik" <Erik.Warren at delta.com>
    To: "Raheel" <softwarengineeer at gawab.com>; <cvsnt at cvsnt.org>
    Sent: Friday, September 10, 2004 5:44 PM
    Subject: RE: [cvsnt] Re: sspi protocol problem!!


    Raheel,

    In NT4.0 the User Manager is used to set this right.  User Manager may be
    located in your start menu under Administrative Tools.  However, if it is
    not just find the program using windows explorer and run it.  The file name
    is musrmgr.exe and is typically located in the system32 folder.

    When you open the user manager from the "Policies" menu select "User
    Rights..."
    A form appears with a dropdown list of rights. Below that is a listbox which
    displays who has the right displayed.
    Select the right you are interested in and add or remove users or groups
    from the list of those who have this right.

    Regarding NAV professional,  NAV Corporate edition is running on the server
    and it actively scans all folders and files including the CVSNT repository.
    Thus far I have not experienced any problems that I am aware of due to NAV.

    Erik W. Warren
    Sr. Engineer - Flt. Ops. Engineering
    Delta Air Lines
    Dept. 088
    P.O. Box 20706
    Atlanta, GA 30320-6001
    Ph (404) 715-7229
    fax (404) 715-7202
    erik.warren at delta.com



    -----Original Message-----
    From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf Of
    Raheel
    Sent: Thursday, September 09, 2004 2:03 AM
    To: cvsnt at cvsnt.org
    Subject: Re: [cvsnt] Re: sspi protocol problem!!


    hello Erik

    I checked my security logs on my NT4 workstation (i.e. cvs server). Nothing
    is there, however I still want to know that in NT4 workstation where should
    I enable the right that is, "Access this computer from network". I tried in
    administrative tools but no luck. Secondly, as your other reply suggests
    that you have no problem with NAV installed at NT4 workstation, i think you
    might have unshield the repositories folders from your AV software, Isn't it
    the case??

    Raheel.

    ----------------------------------------------------------------------------
    ----


    ----- Original Message -----
    From: "Warren, Erik" <Erik.Warren at delta.com>
    To: <cvsnt at cvsnt.org>
    Sent: Wednesday, September 08, 2004 5:11 PM
    Subject: RE: [cvsnt] Re: sspi protocol problem!!


    I was unable to use sspi when I first set up my CVSNT server
    and I remember how frustrating it was to read posts about
    how simple it was to use sspi and how well it worked.
    I was finally able to find out the problem by reading the security
    log in the event viewer on my CVSNT server.  My problem
    was that the "Access this computer from network" right had
    been denied for all groups except local admins.  The security
    log specifically listed that this right was missing any time
    an attempt to login to CVSNT was made using sspi.
    Once I knew what the problem was it was simple to add this
    right back for the group that CVSNT users were in.

    The bottom line is that the security log in event viewer on the
    CVSNT server may have additional information on why a login
    attempt failed.

    Erik W. Warren
    Sr. Engineer - Flt. Ops. Engineering
    Delta Air Lines
    Dept. 088
    P.O. Box 20706
    Atlanta, GA 30320-6001
    Ph (404) 715-7229
    fax (404) 715-7202
    erik.warren at delta.com


    Tony Hoyle wrote:

    > If you're not logged into the domain you might need to do a cvs login
    > anyway, if you've not got cached credentials connecting you to the
    > machine.  If the login is rejecting you it's most likely the wrong
    > password.

    Could there technically be any other reasons that would bring up this
    error message? Specific access privileges on the server or anything
    like that? I think I remember something similar being reported a while
    back where it wasn't an incorrect password but I couldn't find it at
    the moment... maybe the server for some reason has trouble associating
    the account that's logging in with the existing account on the server?
    What would be able to cause this? How would one go about verifying this?

    Cheers,

    --
    Oliver
    ----  ------------------
    JID:  ogiesen at jabber.org
    ICQ:  18777742 (http://wwp.icq.com/18777742)
    _______________________________________________
    cvsnt mailing list
    cvsnt at cvsnt.org
    http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
    _______________________________________________
    cvsnt mailing list
    cvsnt at cvsnt.org
    http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
    _______________________________________________
    cvsnt mailing list
    cvsnt at cvsnt.org
    http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt




More information about the cvsnt mailing list