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 firstname.lastname@example.org.
Your a daisy Bo, it worked a treat once I changed the password on the server to the same as the client machine. Thanks, /Dec "Bo Berglund" <bo.berglund at telia.com> skrev i meddelandet news:e6tmh3hhtd5knimrfjot8145bl4mhcr904 at 4ax.com... > On Sun, 21 Oct 2007 00:01:01 +0200, "DubbySw" > <declan.swords at telia.com> wrote: > >>Hi All, >>I'm installing CVS on a network server. >>It installs fine and can be used by the server to itself. >>If I then install the cvsnt client on an XP box I cannot get it to >>connect. >> >>I suspect it has to do with the fact that the workstations on the network >>all have local logins >>i.e. no domain setup. Is this the root of my problem? >> >>I've put in all users in the passwd file. Adjusted config file auth = no. >>This is what I get >> >>C:\>cvs -d :sspi:192.168.0.2:/test login >>Logging in to :sspi:lan at 192.168.0.2:2401:/test >>CVS Password: >>cvs [login aborted]: authorization failed: server 192.168.0.2 rejected >>access to /test >> > > The passwd file is only valid for pserver and sserver protocols. > SSPI uses windows authentication and therefore your users must be > known by the CVSNT server. Add the users as local users and set the > passwords to match and you will be fine. > > BTW, this is exactly like you would have been forced to do if you used > a Windows Workgroup PC as a file server and the other PC users wanted > to connect to the server shares (runnong NTFS as file system of course > and with "simple file sharing" disabled). > > HTH > > /Bo > (Bo Berglund, developer in Sweden)