Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Thanks Bo, I'll try these steps and get back to you, I'll try the sspi method first! Ariz "Bo Berglund" <bosse at agiusa.com> wrote in message news:b7qvmh$g0e$1 at sisko.nodomain.org... > Your setup is to say the least "unconventional".... > I would really recommend that you change this setup so that the users are > given proper workstation login names (different for each user). It is not > such a big job given the low number of workstations you are managing. Just > walk around to them and add one user login on each one (in user manager). > Then also add the same users to the PC where the CVSNT server is located > using the same passwords. If you like you can set the user names as the > computers even though I would not do that myself. > > When this has been done you can use the sspi protocol which is the best > one for internal Windows use. It really needs no additional steps because > the user login will be the CVS identifier too. > > However, > if you insist that you *must* use the Administrator login on all > workstations (a very strange practice) then you are left with pserver > only... > In this case you must do the following: > > 1) On the CVSNT server PC you must create a new proper login account, call > it CVSUser or some such thing. THis will be used as the account CVSNT uses > for repository operations and must be a real existing NT account. Don't > use Administrator here!!!! > > 2) Then you must use the cvs passwd command to add the "real" pserver > users by this command (one for each one of your CVS users, example shows > charlie): > cvs passwd -a charlie -r CVSUser > You will have to enter the password of each user, this is a CVS password > only so you can invent whetever you like. You must be an administrator for > CVS to do this so it is best done on the command prompt of the CVSNT > server PC. > > 3) On your workstations the users must set up a CVSROOT connection string > like this: > :pserver:charlie at cvsserver:/repository > How this is done varies depending on cvs client, for example on WinCvs 1.3 > there is a GUI dialog that splits the components of this into several > entries. > > 4) Each user must log in using the command cvs login before he can check > out a new module from the CVS server. Afterwards he is not needed to log > in again if he just works in this module. > > HTH, > > Bo > > > AKM wrote: > > > Hi > > > Sorry for my ignorance but I am completely new to CVS and Source Control. I > > have read the documentation but I am having trouble starting off, I'll give > > a brief description of my service. > > > I have around 5 NT/2000 workstations and one XP pro Workstation; my main > > server for running the internet proxy server is on a Win 2000 server. We are > > not on any domain, we have our own workgroup and every machine belongs to > > the workgroup. All users log on as administrator and the method of > > identification of the user is through PC name. > > > I have installed the CVS server onto one of the Win 2000 server > > workstations, this is not the server that host's the proxy but just a > > worstation used by a user. I have installed wincvs and tortoise on my XP > > home PC. > > > Now how do I create users on the CVS server using sspi or ssh? There are no > > user names for logging on to the workgroup, just PC names, all users log on > > as admin. How do I create a repository and just basically how do I start and > > have 3 users use the repository. > > > I'm not getting much help from the docs for my kind of set-up. Should I use > > Pserver? I don't need to distribute my repository over the internet or WAN. > > > Thanks so much in advance > > Ariz > >