Regardless of the past, now, in the future, resource sharing is one of the important applications of the network. Through resource sharing, we can implement the exchange of file materials. Windows XP is now the most popular operating system. Today, we will look at how to share files under Windows XP, while making a solution for Windows 98 and Window 2000 systems.
How to share a Windows XP operating system?
First, use the Windows XP shared folder and set permissions This article describes how to share folders and files on the network using Windows XP. Mainly for the following aspects:
1, Microsoft network file and print sharing
2, Microsoft network files and print shared components allow computers in the network to access resources on other computers through the Microsoft network. This component will be installed and enabled by default. Files and print shared components are applied by the TCP / IP protocol to connect to the unit, which you must share the local folder for the functions provided by this component.
3, the files of the Microsoft network and the print shared components are equivalent to the server services in Windows NT 4.0.
To share folders with other users on the network, perform the following steps:
Open "My Documents" in Windows Explorer. Click "Start", "All Programs", "Accessories", "Windows Resource Browser".
Click on the folder you wish to share.
In the File and Folder Task bar, click Share this folder.
In the Properties dialog box, select the "Shared this folder" radio box (Figure 1) to share a folder with other users on the network.
Figure 1. Sharing folder on the network
To modify the network sharing name of the folder, enter a new name for the folder in the Shared Name text box. This operation does not have any effect on the folder name on your local computer. Explanation: Shared features are not available for Documents and Settings, Program Files, and Windows System folders. In addition, you cannot share the folder in other users' configuration files.
To set, view, modify, or delete files and folder permissions, follow these steps:
Open Windows Explorer and locate the file or folder you want to set permissions. To open the Windows Explorer, click "Start", "All Programs", "Accessories", "Windows Resource Browser".
Right-click on the file or folder you locate, select "Properties" in the subsequent shortcut menu and click the Security tab (as shown in Figure 2).
Figure 2. Settings files and folder permissions
To set permissions to groups or users who are not displayed in the Group or User Name list, click Add. Enter groups or user names you want to set permissions and click OK.
As shown in Figure 2, if you need to modify or delete permissions for existing groups or users, click the appropriate group or user name and perform any of the following:
To allow or reject certain permissions, in the Permissions list, the Allow or Reject check box is selected. To delete a group or user from the Group or User Name list box, click Delete. Description
In Windows XP Professional, the Everyone group is not included in anonymous login. You can only set files and folder permissions on drives that use NTFS file systems to format.
To modify some permissions, you must be the owner of the corresponding file or folder, or have administrative privileges granted by the file or folder owner.
Group or users with specific folders "full control" permission can delete files or subfolders from this folder without considering what permissions protected by the corresponding file or folder.
If the authority check box for a specific group or user is disabled, or the "Delete" button is not used, it means that the permissions of the corresponding file or folder are inherited from the parent folder. By default, when a new group or user is added, the group or user will have "Read and Execute", "View Folder Content", and "Read" permissions. Second, the sharing between the same machine is designed for a single machine multi-user. If you just share disk (optical drives) or folders in this unit, just drag the drive or folder to "C: / Documents and Settings / All User / Shared Document" in Windows Explorer. . Windows XP is really copying the contents of the disk or folder to the Shared Document, so when the shared file is too much, a large amount of local hard disk space will take up. However, this also has its advantages, that is, even if the user destroys the file in the Sharing Document, it is not impact that the source file is influenced, thereby improving the security of the data.
I personally think that this practical significance of this sharing is not big, because the security of the Windows system is relatively poor, we can access each partition at will. Even if you don't share it, others can log in into your computer, all secrets are still in a light.
Third, the implementation of local area network sharing
On the LAN Other Computers running a Windows operating system, remote sharing of files and disks can be implemented via online neighborhood.
Usually, as long as the computer is connected to the local area network, and the correct IP address information is configured, Windows is only required to run a while, you can discover all the working groups and computers in the network. For Windows ME, Windows 2000, and Windows XP, it is also possible to discover the folders available in the network and display it in the network neighbors of the Windows Explorer. The user can do, just double-click and open the folder you interested in.
Note: If you can't find a computer to share resources in an online neighbor, you can use the computer's way to find the computer using the name of the computer. In addition, IP addresses of the same network segment should be used between the shared computers, otherwise, it will not be found between each other.
4. How to remove file sharing restrictions in Windows XP systems
Do you have this situation: On the computer installed in Windows XP, even if the network connection and sharing settings are correct (such as the IP address belonging to the same subnet, the NetBIOS on TCP / IP is enabled, the firewall software does not have a file Shared 135, 137, 138, 139 and other ports), users who use other systems (including Windows 9X / ME / 2000 / XP, etc.) are still unable to access the computer. How should we solve this problem?
By default, Windows XP's local security settings require all users to access all guests. At the same time, the user rights assignment in the Windows XP Security Policy is prohibited from accessing the system through the network. Those two mutually contradictive security strategies have led to other users within the network to access the Windows XP's computer through the network. You can solve the following methods.
Method 1: Limit the guest account
Click "Start → Run", enter "GPEDIT.MSC" in the "Run" dialog, open the Group Policy Editor, and select Computer Configuration → Windows Settings → Security Settings → Local Policy → User Rights Assignment ", double click "Reject to access this computer" policy from the network, delete the "Guest" account inside. This other users can use the guest account to access the computer using the Windows XP system over the network.
Method 2: Change the network access mode
Open the Group Policy Editor, select Computer Configuration → Windows Settings → Security Settings → Local Policy → Security Options ", double-click Network Access: Local Account Sharing and Security Mode" Policy, will set the default setting "Only guest - local Users have passed the guest authentication ", change to" Classic: Local users verify their own authentication. " Now, when other users access the computer using Windows XP via the network, they can log in with their own "identity" (provided that this account in Windows XP is correct).
When the strategy changes, the file sharing method has changed, and after the "Classic: Local User is verified by its own authentication", we can limit the number of users who simultaneously access the shared file and can target different users. Set different access rights.
However, we may also encounter another problem. When the user's password is empty, the access will still be rejected. It turns out that there is an "account: the local account using the blank password" policy is allowed to enable it by default, and the user who refuses the priority in the Windows XP security policy, the password is empty by network access It is disabled when using Windows XP. We will solve the problem as long as we stop this strategy. 5. How to share encrypted files in Windows XP
This section describes how to share access to files that use the Windows XP Encryption File System (EFS). Encryption is a process that converts data to other people that cannot read. If the data is stored on the hard disk, you can use Windows XP EFS automatic encrypted data.
How to share access to encrypted files
Note: Only the user of the administrator group or the user encrypts the file can add users to the file. If you are not allowed to add a user to an encrypted file, you will receive the following error message:
EFSADU Error In Adding New User (s). Error Code 5.
You can keep file encrypted security while allowing specific users to access your encrypted files. To allow access to your encrypted files, do the following: Right-click Encrypted File, and then click Properties.
Click General tab (if you have not selected), then click Advanced.
Click Details, and then click Add.
Select the user who wants to share the encrypted file, and then click OK.
After adding the user, click on three times.
The second part of WIN 98 can not access Win XP solutions in the LAN, often encountered a shared directory with Win 2000, and the Win 98 is unable to access the Win2000 shared directory, in Microsoft The official website can find the answer, prompt to open the win2000 Guest user.
However, after Win XP came out, the same is also facing this problem, and some people find this method. The shared directory accessing the XP from the online neighbor is not necessarily allowed. What is the reason? This question has also been plagued for a few days, but later discovered the answer to the question, maybe this is a bug of Win XP.
When the system guest user is turned on, click "Start" "Run", enter GPEDIT.MSC, you can call the Group Policy Editor, in the Local Computer Policy / Computer Configuration / Windows Settings / Security Settings / Local Policy / User Rights Assignment / Reject From Network Access this computer, you can see a Guest user! If you delete guest users here, other computers can view this computer's shared directory from the online neighbor.
Note: Chinese WIN XP, uses traditional login mode and turn off "using simple file sharing" in the Folder option.
The third part of WIN 2000 cannot access Win XP reasons and solutions Because everyone used the operating system may be different, the Mutual access of the Windows system is normal, but sometimes 2000 systems cannot access the XP system. What is going on? Let's take a look at the problem. now, many people have used Win2000 and WinXP to network, but there are many netizens in specific uses to browse online neighbors in Win2000 and WinXP, especially when there are Win9x and WinME workstations in the network. It is especially obvious. Sometimes it takes more than 10 minutes to open the online neighbor, and it is often reported. So what is the slow-selling person? There are two main reasons for the pen. a, network protocol configuration problem, B, WIN XP program task problem. But if other Windows computers can't see WinXP computer in the online neighbor, it is possible that the user lock and security policy are not set. At this time, you need to start from the following aspects. I have encountered similar problems before, but in a large number of networking experiments, I have summed up a set of effective solutions, and now I will give you a professor. 1. Installation and setting of the network protocol. Install the NetBeui protocol in WinXP, you have not mistaken, you have to install the NetBeui protocol in WinXP. Microsoft only supports TCP / IP protocols and NWLINK IPX / SPX / NetBIOS compatible protocols in WinXP, officially announced no longer support NetBeui protocol. However, in the actual use of small LAN, the two protocols supported by Microsoft are not satisfactory. For example, in the process of solving the slow problem of online neighbors, the author uses many ways, although the speed of online neighbors is better, but is still as snail; in addition, when setting up multi-block protocols, customers and service bindings, this There are also bugs, and multiple network cards must be bind all protocols (except NWLINK NetBIOS), customers and services. Even if you cancel some binding restart, the system will automatically add, this obviously does not satisfy well. The actual needs in network construction. When the note is installed in WinXP, the above two problems have been successfully resolved. There is 3 files in the "/ valueadd / msft / net / netbeui" directory of the WinXP installation CD, where "NetBeui.txt" is an installation instructions, and the other two is the file required to install the NetBeui protocol. The specific steps of the installation are as follows: copy "nbf.sys" to "% systemroot% / system32 / drivers /" directory; copy "Netnbf.inf" to "% systemroot% / inf /" directory; in the network In the Connection property, click the Install button to install the NetBeui protocol. Note:% systemroot% is a WinXP installation directory, such as the author's WinXP installation, in the F: / Windows directory, you should replace% SystemRoot% in F: / Windows. 2. Set up other network protocols in WinXP to suggest that if your LAN does not have to be used to install the NetBeui protocol. Netbeui in a small LAN (network with 200 left and right computers) is the least amount of memory, the fastest speed, the NWLINK IPX / SPX / NetBIOS compatible protocol should be deleted. If your local area network is going to INTERNET, you must install the TCP / IP protocol. However, for the quick access to the network, it is recommended to specify the IP address of each workstation (unless there is a DHCP server in the network), the workstation always constantly looks for the DHCP server to slow the network speed.
Off It is very inconvenient in many actual network applications. other Windows computer network protocol
Careful users may have discovered that there is a "Setting Home or Small Office Network" wizard in WinXP online neighbors, which can easily set the local area network sharing, Internet connection, and small LAN. The wizard also provides a network installation floppy disk for other Windows computers connected to WinXP.
However, the author does not advocate the installation of the floppy disk using this network. On other Windows computers connected to WinXP, just install the NetBeui protocol and set the web flag. To connect the Internet, just install the TCP / IP protocol and specify the IP address. This is exactly the same as the setup of the traditional local area network, it is recommended to use the IPX / SPX compatible protocol.
Second, completely disabling WinXP plan tasks
When you browse online neighbors in WinXP and Win2000, the system will delay for 30 seconds, and Windows will use this time to search for remote computers to have a specified planned task (even possibilities to search for search). If there is no reaction when the network is searching, it will fall into the unlimited waiting. For more than 10 minutes, it is not surprising. The following is a specific solution.
1. Turn off WinXP plan task service (task scheduler)
You can open the "Task Scheduler" Properties dialog box to "Control Panel / Manage Tools / Services", click the Stop button to stop the service, then set the start-up type to "manual", which starts next time It will not start the service automatically.
2. Delete two sub-keys in the registry
to the registry to find the primary key "HKEY_LOCAL_MACHINE / SOFTWARE / Microsoft / Windows / CurrentVersion / Explorer / RemoteComputer / NameSpace" Delete the following two Zijian {2227A280-3AEA-1069-A2DE-08002B30309D} {D6277990-4C6A-11CF-87 -00AA0060F5BF}
here, the first child decided whether the online neighbor is to search for online printers (even to the Internet to search), if there is no shared printer in the network, you can delete this button. The second child is decided to find the designated planned task, which is the judge of the online neighbor, and must be tenth.
three, solving other Windows computers unable to access WinXP computers
Some netizens have installed the network, but they found that the computer installed with Win9X or WinMe operating system cannot access WinXP computers, even in the online neighbor, do not see each other. If you also encounter this kind of trouble, you can check the following.
1. Check if guest users are enabled
By default, the Guest users in Win2000 and WinXP are disabled. To enable guest users to remove the "account has been deactivated" in the "Control Panel / Management Tools / Computer Management / Local User and Group / User". This user is best not to set a password, and select "Users cannot change the password" and "password never expiration", which can easily access and reduce the possibility of trouble. But the premise is that the authority of the guest user must set the guest and the group, otherwise the suffering is endless.
2. Check if you refuse guest users access the machine from the network
In WinXP, the deferion is rejected to access the native from the network. You can view the "Control Panel / Manager / Local Security Policy / Local Policy / User Rights Assignment / Refusal from Network Access this computer". If you include guest users, it will be deleted. If you are on the Win2000 Server or WinXP.NET server in the domain, you must also delete the guest user in the "Domain Security Policy" corresponding project, you need to pay attention to the delete to wait a few minutes to work. 3. Set password for guest users
If the guest user has a password, other Windows workstations will prompt the input password when accessing the WinXP computer. At this point, you can enter the WinXP computer. When you enter your password, you can select the following "Please save your password to the Password list", no longer prompt the password (unless the user password has changed). Of course, if it is already set to the login field on the Windows workstation, it is not affected by the GUEST user password in a domain user. Two: Especially XP exchanges If the setting is no problem, it is basically a strategy.
On the computer installed in Windows XP, even if the network connection and sharing settings are correct (such as the IP address belonging to the same subnet, the NetBIOS on TCP / IP is enabled, the firewall software does not prohibit file sharing 135, 137, 138, 139 and other ports), users who use other systems (including Windows 9x / ME / 2000 / XP, etc.) are still unable to access the computer. How should we solve this problem?
By default, Windows XP's local security settings require users to use users allocated. At the same time, the user rights assignment in the Windows XP Security Policy is prohibited from accessing the system through the network. Those two mutually contradictive security strategies have led to other users within the network to access the Windows XP's computer through the network. You can solve the following methods.
Method 1: Limit the guest account
Click "Start → Run", enter "GPEDIT.MSC" in the "Run" dialog, open the group policy editor, select Computer Configuration → Windows Settings → Security Settings → Local Policy → User Rights Assignment, Double click "Reject Access this computer from the network, delete the "Guest" account inside. This other users can use the guest account to access the computer using the Windows XP system over the network.
Method 2: Changing network access mode
Open Group Policy Editor, select Computer Configuration → Windows Settings → Security Settings → Local Policy → Security Options ", double-click" Network Access: Local Account Sharing and Security Mode "Policy, will set the default setting" Only guest - local users Guest authentication ", change to" Classic: Local users verify their own authentication ".
Now, when other users accesses the computer using Windows XP via the network, they can log in with their own "identity" (provided that this account in Windows XP is correct and the password is correct).
When the policy changes, the file sharing method has changed, and after enabling "Classic: Local User With your own authentication" mode, we can limit the number of users who simultaneously access the shared file and can set different users. Access permission.
However, we may also encounter another problem. When the user's password is empty, the access will still be rejected. It turns out that there is an "account: the local account using the blank password" policy is allowed to enable it by default, and the user who refuses the priority in the Windows XP security policy, the password is empty by network access It is disabled when using Windows XP. We will solve the problem as long as we stop this strategy. Summary
