A good way to deal with the win 2003 server management problem

  

When the website develops to a certain scale, the webmaster will begin to consider hosting the server for the website. Usually, the server will be placed in the telecom or Netcom's computer room. The webmaster manages the server remotely. For a more professional webmaster, managing the server may be a relatively simple matter! However, the fact may not be As easily as we imagined, in different server system environments, we may encounter many unique management challenges that seriously affect the efficiency of our management servers. To this end, today I will summarize some of the server problems that often occur, and propose solutions to each management problem. I hope that these contents can be useful to everyone!

1. Speed ​​up server login

When we installed Active Directory on the Windows 2003 server system, set up all the workstations in a specific domain, and created the account of the user accessing the server, the workstation user always complained about the current login when trying to log in to the server. The speed is much slower than before. So why after the above settings, we will feel that the server login speed is slower than before, how can we improve the speed of workstation users logging into the Windows 2003 server?

In fact, once installed in the server system In the Active Directory, if the "Domain Name System" in the Active Directory is not configured correctly, it will naturally lead to an extended server login time. When the workstation attempts to log in to the server, the locating domain controller component used by Active Directory is actually the domain controller locator, and the domain controller locator accesses the connection in the format ldld._tcp.DnsDomainName. DNS server, in order to get the service resources required by the workstation user; if the DNS server server is not working properly during this access connection, or the local server's DC registration operation is not correct, then the workstation cannot be found when logging in to the server. DC, the speed at which you log in to the server will be severely affected. In fact, in order to solve this kind of failure, we only need to run the Netdiag diagnostic program in the LAN workstation and DC respectively. Through this program, we can quickly find the specific cause of the failure, for example, whether the Dns server is not working properly, or The DC registration operation is not correct. Once the cause of the failure is identified, it is not difficult to easily troubleshoot the slow login of the server.

2, simplify the password for the server

When I try to upgrade the unit's windows 2003 server system update to a domain controller, I would like to set a simple access password for the unit leader, after all, There are many things to do, and you can't remember complicated passwords with both uppercase letters and lowercase letters and numbers. However, when setting up simple passwords, the domain controller system prohibits the author from creating too simple passwords in the system. This kind of fault prompt, how should we face it?

In fact, the password that cannot be set too simple is caused by the default security settings of Windows 2003 server. We only need to modify the system according to the following steps. The default security settings policy can simplify the password for the server:

First log in to the domain controller system as a super administrator, and click the "Start" button in the system desktop, in the pop-up system “Start” in the menu, execute the “Set”/“Control Panel” command in the pop-up control In the panel window, double-click the “Administrative Tools” icon to open the management system list window of the server system;

Secondly, double-click the “Domain Security Policy” icon in the mouse, and then pop up In the default domain security settings window, double-click "“Windows Settings”/“Security Settings”/“Password Policy", in the right side of the corresponding password policy" project, find “password You must meet the complexity requirements & rdquo; this option, and right-click the option, execute the "Properties" command from the pop-up shortcut menu to open the property settings window,

Check the settings window "Don't be disabled", if the project is still selected, you must re-select it in time, click the "OK" button in the dialog box, and then restart the server system, in the future We can freely set a simple password in the domain controller.

3, for server access troubleshooting

When accessing a specific shared folder in the Windows 2003 server system from a workstation in the unit LAN, there is a failure to find the network path. Prompt, but when a workstation continues to access the target shared folder on the server, it is found that the access operation is normal. Even more strange is that when the workstation system that cannot access the server is restarted once and the shared folder of the target server is accessed again from the workstation, the server does not have a fault prompt, and sometimes it sometimes appears Can access the phenomenon that sometimes can not be accessed; when accessing the server we use the IP address access method, when a failure prompt can not find the network path, we also found that the PING通 server can be normal at this time? Face this kind of time Continued unstable access failure, where should we start?

When we accidentally encounter the above strange phenomenon, we can first check whether the network connection line between the corresponding workstation and the server is It is in a stable state, and once the network cable connection interface is loose, it is easy to occur the above-mentioned intermittent and unstable failure phenomenon. After eliminating the instability of the connection line, if the above fault phenomenon still cannot be eliminated, it is mostly a problem with the workstation itself. This is because other workstations in the LAN can normally access the target shared folder in the server. This basically makes it possible to conclude that the server system does not have any problems. Considering that the target workstation can sometimes access the server, we suspect that it is very likely that the master browser in the target workstation has encountered an accident. At this point, we may wish to perform the following operations on the target workstation to detect whether there is a problem with the master browser:

First click on the target workstation and click “Start” to start ”/“Run&rdquo ; command, enter the string command "ldd; cmd" in the pop-up system run dialog box, click the Enter key, switch the system state to the MS-DOS window;

Secondly at the DOS command line prompt Next, enter the string command “nBTstat –a xxx.xxx.xxx.xxx” (where “xxx.xxx.xxx.xxx” is the IP address of the server), click the Enter key, check it later The result information contains the words "_msbrower", if it is not found, it means that the master browser of the workstation is mostly problematic. At this time, you may want to restart the workstation system to see if it is intermittent. Whether the stable access failure phenomenon still exists, if it still exists, then we must uninstall the workstation's network card, then re-install the driver of the network card, and then set the parameters of the network card to The argument before the Internet, I believe that way we can eliminate the workstation can not access the server stable strange phenomenon. Previous12Next page Total 2 pages

Copyright © Windows knowledge All Rights Reserved