내보내기(0) 인쇄
모두 확장

How to: Enable Remote Access Manually

Visual Studio 2005

You might have to enable remote access manually if you want to set up a database on a computer other then the Web server, if you want to set up remote access not on the default Web site, or because you have tried to enable it through Visual SourceSafe and have received an error.

To manually enable remote access, you must:

For more information about how to complete the last three steps, see the following procedures.

NoteNote

After running the IIS lockdown tool, remote access may stop working. See the procedure below "To reinstate remote access after running the IIS lockdown tool."

To register ASP.NET V2.0 and configure IIS

  1. If you installed IIS after you install Visual SourceSafe, register ASP.NET V2.0 by running the following command from your framework location, for example, in C:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx:

    aspnet_regiis –i
    
  2. If you are running Windows Server 2003 or 64-bit Windows XP or Server, enable WebDAV and ASP.NET IIS extensions in the IIS MMC snap-in, under Internet Information Services Web Service Extensions.

  3. For 64-bit computers, you must have matching 64-bit versions (the same version number as the 32-bit versions) of the .NET Framework. After you install IIS, do the following:

    1. Register the 64-bit ASP.NET V2.0 by running the following command from your framework location, for example, in C:\WINNT\Microsoft.NET\Framework64\v2.0.xxxxx:

      aspnet_regiis.exe –ir 
      
    2. Put IIS into 32-bit mode by running the following command:

      cscript %systemdrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1 
      
    3. Register the 32-bit ASP.NET by running the following command from your framework \v2.0.xxxxxx location, for example, in C:\WINNT\Microsoft.NET\Framework\v2.0.xxxxxx:

      aspnet_regiis.exe -i –enable 
      
    4. Create a 64-bit WebDAV extension and enable it by running the following command:

      IIsExt /AddFile %systemroot%\syswow64\inetsrv\httpext.dll 1 WEBDAV32 1 “WebDAV (32-bit)” 
      
    5. Map the SourceSafe folder to use the current version of ASP.NET by running the following command, substituting the path to your SourceSafe virtual folder:

      %WINDIR%\Microsoft.NET\Framework\v2.0.xxxxx\aspnet_regiis.exe -s W3SVC/1/ROOT/SourceSafe  
      

To create a SourceSafe Web

  1. In IIS manager, go to the Web site where you want to create a SourceSafe Web.

  2. Add a virtual folder called SourceSafe that points to the VSSWebService folder in your Visual SourceSafe installation folder (for example, c:\Program Files\Microsoft Visual SourceSafe\VSSWebService).

  3. Open the properties for the SourceSafe virtual folder, and on the Virtual Directory tab, under Application Settings, change the Execute Permissions to Scripts only.

  4. Go to the Directory Security tab, and under Anonymous access and authentication control, select Edit.

  5. Under Authenticated access, check the Integrated Windows authentication box at the bottom of the dialog box. Make sure all of the other boxes in this section are clear.

  6. Click OK to save your changes.

  7. Map the virtual folder for your SourceSafe Web by running the following command from your framework location, for example, in C:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx:

    aspnet_iisreg.exe –s SourceSafe_Virtual_Folder
    

To create virtual directories for uploading and downloading files

  1. Go to the file system folder where your database is located.

  2. Create a folder in the database named VssWebUpload.

  3. Create another folder to the database named VssWebDownload.

  4. Edit the srcsafe.ini file for your database, and add the following three lines:

    DownloadVDir = download_virtual_folder_name
    UploadVDir = upload_virtual_folder_name
    Web_Service = http://yourserver.com/SourceSafe/VssService.asmx
    

    The download and upload virtual folders can be any valid virtual folder, for example, YourserverDownloadVdir and YourserverUploadVdir. For the Web_Service entry, make sure that you enter the same URL that your remote users will use.

  5. In IIS manager, go to the SourceSafe Web.

  6. Add a virtual folder with the same name that you entered for the download virtual folder in step 4 (for example, YourserverDownloadVdir), and point to the VssWebDownload folder created in step 3. AllowRead access to this virtual folder.

  7. Add a virtual folder with the same name that you entered for the upload virtual folder in step 4 (for example, YourserverUploadVdir), and point to the VssWebUpload folder created in step 2. Allow Write access to this virtual folder.

  8. Open the Web.config file under the SourceSafe Web, and add the following line directly before the </configuration> tag:

    <appSettings><add key="\\yourserver\yourdb" value="DatabasePath"/></appSettings>
    

    Make sure you enter the same UNC path that your remote users will use.

To reinstate remote access after running the IIS lockdown tool

  1. Right-click httpext.dll (from <windows_directory>\system32\inetsrv\) and choose Properties.

  2. Select the Security tab, and then click Advanced.

  3. On the Permissions tab, select the permission Remote Everyone Deny ACE, and then click Remove.

  4. Click OK twice to save your changes and close the open dialog boxes.

  5. From the folder <windows_directory>\system32\inetsrv\urlscan\, open Urlscan.ini.

  6. Move PUT from the [DenyVerbs] section to the [AllowVerbs] section.

  7. Save Urlscan.ini.

Security

For increased security, you should take the steps described in the following topics:

How to: Set Up Secure Sockets Layer (SSL)

How to: Set Share Permissions for a Database

See Also

커뮤니티 추가 항목

추가
표시:
© 2014 Microsoft