Configure client-side offline file settings
The Offline Files feature of Windows 2000 and later enables users to maintain a local copy of a shared folder so they can work with the folder and its contents when the server is unavailable. However, you might prefer to disable offline folders in your network for security reasons or simply to avoid the problems that will inevitably crop up when users try to take advantage of offline folders.
You can configure client-side settings to control offline files, either manually or through group policy. To configure offline files manually, open any folder on the client computer, choose Tools | Folder Options, and then click the Offline Files tab. This is where you can enable or disable offline files altogether. You can also configure how to synchronize offline files, specify the size of the offline files cache, and configure a few other minor options.
In situations where you need to configure a number of offline settings on multiple computers, you can turn to local or group policy to apply the settings. The policies are located in the Administrative Templates | Network | Offline Files branch of both the Computer Configuration and User Configuration policy branches. You can set a variety of settings that disable offline files, prevent the user from making offline file setting changes, and fully configure offline file behavior.
Windows 2000 Server
Direct Web traffic with host headers
When a Web client such as Internet Explorer or Netscape sends a request to a server for a Web page, the client typically does so using the fully qualified host name of the server, such as www.microsoft.com.
When Internet Information Services (IIS) receives the request, it examines the host header in the request to determine how it should respond. For example, in the request for www.microsoft.com/something/page.html, the host header is www.microsoft.com. IIS looks in the properties for the sites it maintains and serves the one that matches.
Each Web site in IIS has three identifying properties: IP address, port, and host header. At least one of these properties must be unique for each site. For example, multiple sites on the same server can use the same IP address and port, but each must have a unique host header. To direct traffic to a specific Web site, specify the appropriate host header in the site's properties.
For example, perhaps local clients can't access an internal Web site because of the way the firewall handles in-network requests for the server's public IP address. Rather than change the firewall configuration, add a DNS host record named local that points to the local IP address of the server.
Then, modify the properties of the site to add local.yourdomain.tld to the site, specifying your own public Internet domain in place of yourdomain.tld. Local clients can then connect to http://local.yourdomain.tld to access the site from behind the firewall.