Authorization mode enabled by default on the server system causes shared access failure

Recently, due to work reasons, the employees of the unit need to access a shared resource in the LAN file server. Originally, this was a simple operation, but many employees encountered the inability to access the shared access during the shared access process. A resource failure prompt. After the layer is checked, the network administrator finds that the authorization mode is enabled by default on the server system, preventing multiple employees from accessing the target shared resources in the file server at the same time. Now, this article summarizes the reasons for this shared access failure and the elimination process, and share it with netizens!

Introduction to sharing faults

In the recent period, some units in the unit are preparing to organize a large-scale scientific and technological negotiation activity. Since many activities need to be shared, the unit LAN administrator will temporarily A normal computer with Windows Server 2003 system is used as a file server, and all active resources are saved to one of the shared folders, allowing the employees to share access through the LAN. However, it is not long before the shared resources are released. Some employees report to the network administrator that the file server where the shared resources are located cannot be successfully logged in, and those who have successfully logged into the file server reflect that they can access them. Sharing resources, but only can not see.

In order to figure out the root cause of the specific fault, the network administrator immediately tried to log in to the LAN file server from the ordinary computer he used, and repeatedly logged in and connected several times. It was found that the file server could not log in normally, and the system screen was on the screen. At the same time, the number of remote connections has reached the maximum value, and the remote connection cannot be simultaneously performed. It seems that this failure phenomenon is likely that the shared resources in the LAN server limit the number of user accesses, thereby causing some employees. The ability to access shared resources, another part of the staff can not access the shared resources.

The first reason for troubleshooting

Since the fault indicates that the number of remote access connections exceeds the maximum access value, why not enter the file server system and modify the access attribute parameters of the shared resource to cancel the user access. What is the limit? With this in mind, the network administrator immediately logs into the Windows Server 2003 server system as a system administrator, opens the corresponding resource manager window, finds the target shared folder, right-clicks the shared folder, and pops up. Execute the "Properties" command in the shortcut menu, open the property setting window of the target shared folder, click the "Share" tab in the settings window, enter the label setting page as shown in Figure 1, in which the network administrator It turns out that in the default state, the server system only allows 5 employees to access the data content in this shared folder at the same time.

No wonder employees can access the file server, some employees can not access the file server, and the number of remote access connections is less than 5, the unit employees can successfully log into the file server system; In the case of 5 people logging in, if there are employees trying to log in to access the target shared resources in the file server, then the number of remote connections has reached the maximum value on the system screen, and remote connections cannot be made at the same time. The prompt message is up. After finding the cause of the failure, the network administrator immediately selected the "Maximum User" option in the "User Limit" section of the tab page of Figure 1, so there is no limit to the number of remote connections to the file server.

Considering those employees who have logged into the file server system can only see the target shared resources can not be changed, the network administrator thinks that this is likely to be caused by the inappropriate access rights settings of the target shared resources, so network management Immediately click the “Permissions” button in the tab page of Figure 1 to enter the permission setting dialog box as shown in Figure 2. In this dialog box, he finds that the default permission of the everyone account is “Read”, so he will account for everyone. The access rights are modified in order to "complete control" option. After the modification is completed, click the "Apply" button. Originally thought that it is here, the above-mentioned failure phenomenon that cannot be accessed at the same time and shared resources can only be seen and cannot be changed, will definitely disappear automatically. .

But it didn't take long, and some employees reported to the network administrator that the file server of the unit still could not log in successfully, but this time no employee reported that the target shared resources can only be seen. edited. For such fault response, the network administrator feels a bit puzzled. What other factors restrict the employee's access to the file server at the same time?

Resolve shared failures

The network administrator has been thinking for a long time, thinking that this is probably the network firewall installed in the file server, but he opened the parameter settings of the network firewall. When the window is used, it is always impossible to find which parameter is used to limit the number of remote connections. The network administrator has to temporarily shut down the network firewall program for a period of time and notify the employee to continue the shared access test, but the actual test indicates The failure to access the shared failure at the same time has nothing to do with the network firewall.

Under the helplessness, network administrators have to search the Internet to find all possible factors that prevent remote shared access connections; after careful analysis and screening, The network administrator found that in addition to the remote connection quantity limit option in the attribute setting window of the target shared resource, the Windows Server 2003 server system also provides the remote connection quantity modification option in the server authorization mode setting window, if the option parameter is not properly set here. It also causes sharing failures where the number of remote connections has reached the maximum value and remote connections cannot be made at the same time.

In order to verify that the authorization mode of the Windows Server 2003 server system is set correctly, the network administrator immediately returns to the Windows Server 2003 server system desktop, and in the desktop, click "Start" /"Settings" /" Control Panel command, in the pop-up system control panel window, double-click the "authorization" icon in the mouse to open the Select Authorization Mode dialog box as shown in Figure 3, in which the network administrator finds "per server" The option is selected, and the number of remote connections is also limited to "5" by default. It seems that the problem is in this place. In order to cancel the remote connection restriction here, the network administrator immediately selected the "per device or per user" option. When the pop-up violates the license prompt window on the screen, he clicked the "No" button on each device or In the Client Authorization Settings window, continue to select the "I agree" option, and finally restart the Windows Server 2003 server system. Sure enough, after the server system restarts, when the unit employee tries to access the shared resources in the file server again, the fault prompt that cannot access the shared resources at the same time will never appear again, which indicates that the fault phenomenon has been successfully solved.