Network Configurations

Considering their location, client machines can be local or remote. Local clients are those that can access the server using a Local Area Network (LAN). This is the local development site where the server resides and from where the majority of the work is accomplished.

Sometimes, however, there are situations in which users need to connect from remote locations. Maybe they work from home or are in a different location and need to make a change to the database.

Local users can access the SourceSafe server directly through the LAN connection, while remote users can reach it through the XML Web service, or through a Virtual Private Network.

Accessing the Server using the LAN Connection

At the local development site the clients use the LAN access configuration to access the Visual SourceSafe server database. The following figure illustrates this network configuration:

Accessing the Server using the LAN Connection

In the LAN access configuration, the LAN booster service is used to increase the file access speeds in Visual Studio. This is the fastest way to access the SourceSafe database. However, if users are required to access the database from remote locations, they can do so by using one of the following remote network access methods.

Accessing the Server through a Virtual Private Network

An old method to remotely connect to the SourceSafe server is by using a Virtual Private Network (VPN) connection. A VPN connection has the ability to connect the remote clients to the LAN at the local development site. This type of connection

creates what is called a virtual tunnel between the clients and the server, making them appear to be physically connected to the LAN. The connection speed, however, is determined by the speed of the user's internet connection.

The following figure illustrates the VPN access configuration:

Accessing the Server through a Virtual Private Network

The remote clients connect via the VPN tunnel to the VPN Server and have access to the local network through this server as if they were working from the local development site. Connection security is achieved by using an encrypted VPN tunnel.

Note

Giving unauthorized remote users access to the Local Area Network from the local development site presents a security risk. Use special security policies for VPN connections.

Although this illustration shows two separate server machines (the SourceSafe server and the VPN server) their services can be combined into a single machine acting as both SourceSafe server and VPN server. Also, the VPN server can be replaced with a router supporting VPN connections.

Accessing SourceSafe through HTTP/HTTPS

The new native method in Visual SourceSafe 2005 that allows remote connections over the Internet uses the XML Web service. The service communicates over a simple HTTP or a Secure Socket Layer (SSL) HTTPS connection. This connection can be filtered through a network firewall for increased security.

The following figure illustrates this network access configuration:

Accessing SourceSafe through HTTP/HTTPS

The remote clients use the public Internet to access the XML Web service to connect to the SourceSafe server. The firewall can be used to filter unauthorized connection attempts according to the local security policy.

Note

Remote access is only accessible using the Visual SourceSafe internet plug-in in Visual Studio. Third-party tools similar to the SourceSafe Explorer can be written to make use of the VSS service and provide stand-alone access to VSS databases.

Security can be strengthened by encrypting the client-server connections using the SSL protocol. This protocol is used for secure document transmission over the public Internet by providing authentication and data encryption. The administration appendixes describe in detail how to set up this remote configuration.

For maximum flexibility you can use a combination of these network access methods.

上一章目录下一章