Abstract: Generally a computer network includes a file server (22), a network (26), and several client workstations (24). Specific network software provides a name server ("NS") (122) to resolve network-name requests. The computer network can also include a proxy for a network service, e.g. a network infrastructure cache (72) that stores files copied from the server (22). Automatic network-name-services configuration adds to this:1. a traffic-monitor module (132) that identifies shared network services, and collects service use data;2. a dynamic redirection service ("DRS") module (126) that receives the collected data, extracts therefrom pairs of client workstations (24) and services, employs a performance metric to order those pairs, and compiles a list (138) of workstations (24) and services that are assigned to the proxy; and3.

Abstract: A network-infrastructure cache ("NI Cache") transparently provides proxy file services to a plurality of client workstations concurrently requesting access to file data stored on a server. The NI Cache includes a network interface that connects to a digital computer network. A file-request service-module of the NI Cache receives and responds to network-file-services-protocol requests from workstations through the network interface. A cache, also included in the NI Cache, stores data that is transmitted back to the workstations. A file-request generation-module, also included in the NI Cache, transmits requests for data to the server, and receives responses from the server that include data missing from the cache.

Abstract: A client (24) in a digital computer network that employs server-driven consistency accesses a file (26) that a caching site (22) supplies from an image of the file (26) projected from a server (28). When the file (26) becomes inactive, the site (22) saves the file onto local permanent storage together with file metadata. A subsequent request to the site (22) to access the file (26) retrieves from local storage the metatadata, including a file-last-write-time attribute. The caching site (22) compares the locally retrieved file-last-write-time attribute with a server supplied file-last-write-time attribute. If the two attributes are identical, then the caching site: 1. reconnects to the projected file image present in storage at the site (22); 2. re-establishes server-driven consistency over the projected file image at the caching site (22); and 3. uses data from the file image retrieved from local storage to respond to a subsequent read request from the client (24).