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.
| It may be the fact that the service is authenticating the SSPI connection | itself disables the ability to access the network. Part of the | authentication | involves an Impersonate/Revert very quickly to get the user name. Well, isn't this refuted by the fact that CVSROOT/config on the share is demonstrably accessed by CvsNT? A syntax error in this file is duly reported back to the client. This shows that the network is accessed. | It may also just be that the service user doesn't have write access to the | repository, so it can't create the lock files. This is a theory I support. The service is running (for the time being) as a user that has memebership in the administrators group. I've of course made the shared resource fully controllable by anyone. In other words, there are absolutely no reasons (as far as I can see) for this user NOT being allowed write access to the shared repository. Any ideas regarding this? Thanks so far. -- Thomas ************************************************************************* Copyright ERA Technology Ltd. 2003. (www.era.co.uk). All rights reserved. The information supplied in this Commercial Communication should be treated in confidence. No liability whatsoever is accepted for any loss or damage suffered as a result of accessing this message or any attachments. ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service. For more information on a proactive anti-virus service working around the clock, around the globe, visit http://www.messagelabs.com ________________________________________________________________________