Search Results

Search found 4 results on 1 pages for 'user23419'.

Page 1/1 | 1 

• Including ISA server into domain

  - by user23419

  Is it problem-free to include existing ISA server into existing domain? All the rules at the moment are based upon IP addresses, All Users.

  Read the article

• 403 in Response to OPTIONS when updating working copy having full access

  - by user23419

  There is an SVN repository (single repository) http://example.net/svn The repository contains several projects (directories): http://example.net/svn/Project1 http://example.net/svn/Project2 User has full access to Project1 directory and has no access neither to root nor to Project2. Everything works fine for a while: user checks out http://example.net/svn/Project1, commits and updates it successfully. But sometimes trying to update leads to the following error: Command: Update Error: Server sent unexpected return value (403 Forbidden) in response to OPTIONS Error: request for 'http://example.net/svn' Finished! Why does TortoiseSVN request something in the root??? I have noticed that this happens after somebody else committed copy or move operation. Checking out http://example.net/svn/Project1 helps till next time... The main question: How to set up access rights for user to avoid these errors? Note, it's not an option to grant user any read or write access right on the root directory for security reasons.

  Read the article

• Including file server into domain

  - by user23419

  We have a file server in our LAN. Windows 2003 Server. It was not included into our domain. Every user has local account on that server, and NTFS permissions are granted to those local accounts. Now we have established a domain controller. Every user has got a domain account. How to include file server into domain so that the permissions would transfer from local accounts to domain accounts? Is it possible to automate this process somehow?

  Read the article

• Including existing ISA server into domain

  - by user23419

  Is there any problem or pitfall including ISA server into domain after ISA was installed and configured and worked for a while? All the rules at the moment are based upon IP addresses, All Users. Addendum 1 ISA is an edge firewall, so it is connected to one Internal network (this is where domain is) and to the Internet provider (External Network). Addendum 2 I'm absolutely sure ISA should be a member of the domain.

  Read the article

1