LabMice.net - The Windows 2000\XP\.NET Resource Index
Home | About Us | Search

Last Updated December 10, 2003

File Management
  Compression
  Dfs
  EFS
  File Replication Service
  Folder Redirection
  Offline Folders
  WFP
  Utilities

Disk Management
  Where to Start
  Defragmentation
  Disk Drives
  Disk Management
  Disk Recovery
  Dynamic Disks
  File Systems
  RAID
  Remote Storage
  Removable Storage
  Storage (SANS)
  Troubleshooting

File Shares

Where to Start...
How to Close All Files Opened by Network Clients from the Command Line
Microsoft Knowledge Base Article: 290585 - This article describes how to close all open files on a Windows NT 4.0-based computer or Windows 2000-based computer from the command line. You can use this command to close files on the computer where the files reside, which you may find most useful when you run it prior to backup procedures in environments where users do not log off, disconnect, or close files prior to scheduled backup procedures. This command only affects files that are open from SMB clients. It does not affect interprocess communication (IPC) or remote procedure call (RPC) connections, HTTP requests, or files that are in use by FTP clients

HOW TO: Connect to Shared Folders Over the Network (on a Domain)
Microsoft Knowledge Base Article: 300856 - This step-by-step guide describes how users can connect to shared folders on a computer in a Windows 2000-based domain. A Windows 2000-based computer can function in either a domain environment with centralized security and management or as a stand-alone computer. If a Windows 2000-based computer is configured as a stand-alone computer, it can join other stand-alone computers in a workgroup. One of the main reasons for doing this is to share files and folders over the network. This document assumes that the computers are running TCP/IP as the network protocol.

HOW TO: Create and Delete Hidden or Administrative Shares on Client Computers
Microsoft Knowledge Base Article: 314984 - This step-by-step article describes how to create and delete hidden or administrative shares on Windows XP Professional-based, Windows 2000 Professional-based, and Windows NT 4.0 Workstation-based computers. A hidden share is identified by a dollar sign ($) at the end of the share name. Hidden shares are not listed when you look through the shares on a computer or use the net view command. The versions of Windows that are listed at the beginning of this article create hidden administrative shares that administrators, programs, and services can use to manage the computer environment on the network.

How to Prevent the Creation of Administrative Shares on Windows NT 4.0 and Windows 2000 
Microsoft Knowledge Base Article: 288164 -This article explains how to prevent creation of the administrative shares on Microsoft Windows NT Server 4.0 and Windows 2000.

HOW TO: Remotely Share Resources in Windows 2000 
Microsoft Knowledge Base Article: 286515 - This article describes how to remotely share resources on Windows 2000-based computers.

HOW TO: Restore Administrative Shares That Have Been Deleted 
Microsoft Knowledge Base Article: 318755 - This step-by-step article describes how to restore administrative shares that have been deleted accidentally. If the administrative shares have been deleted, you can use either Registry Editor or the Poledit utility to configure Windows to automatically create the administrative shares.

HOW TO: Share Files and Folders Over a Network (Domain)
Microsoft Knowledge Base Article: 301198 - This step-by-step guide describes how to share folders on a Windows 2000-based computer that is part of a domain.

HOW TO: Share Files and Folders Over a Network for Windows 2000 Workgroups 
Microsoft Knowledge Base Article: 301281 - This step-by-step guide describes the process of sharing folders on a computer that is part of a workgroup, configuring security for the shared folders and the subfolders and files they contain, and connecting over the network to shared folders 

Saving and Restoring Existing Windows NT Shares 
Microsoft Knowledge Base Article: 125996 - If you need to: reinstall Windows NT over an existing installation (a clean install, not an upgrade); move all of your data drives from one server to another; or install Windows NT to another directory or drive on a computer that already has Windows NT installed, you can save the share names that exist on the original Windows NT installation, including any permissions assigned to those shares 

Security Considerations When Implementing Clustered File Shares 
Microsoft Knowledge Base Article: 254219 - This article describes how to administer file share security in Windows 2000 clustering, and to a limited extent Windows NT 4.0 Enterprise Server.

 
Cannot View Windows 95/98 File Share from Windows 2000 
Microsoft Knowledge Base Article: 263648 - When you attempt to use a Windows 2000-based computer to connect to a file share on a computer that is running Windows 95 or Windows 98, you may receive the following error message:

Windows 2000 Professional and Windows Server 2003 Client Cannot Connect to Network File and Printer Shares
Microsoft Knowledge Base Article: 285018 - Your Windows 2000 Professional-based or Windows Server 2003-based client computer may not be able to connect to file or printer shares on your local network. This behavior can occur when the Windows 2000 Professional-based or Windows Server 2003-based client is running a third-party personal firewall program

Unbinding Client for Microsoft Networks Does Not Disable Shares
Microsoft Knowledge Base Article: 228010 - When you unbind the Client for Microsoft Networks, you do not disable shares on your computer.

Entire contents
© 1999-2003 LabMice.net and TechTarget
All rights reserved

This site and its contents are Copyright 1999-2003 by LabMice.net. Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with LabMice.net. The products referenced in this site are provided by parties other than LabMice.net. LabMice.net makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.