Win2003 remote method beyond the maximum number of connections failure

There was a problem that the remote win2003 exceeded the maximum number of connections in the work. The traditional method is to restart the server to log off the user, but the server is in the IDC room, so it is very inconvenient, and the server will be restarted at some time. Bring your own losses! Here are some ways to deal with the work summary for many years. 1. Method 1 (my favorite method) Enter tsmmc.msc in the run below, which is installed by default in the 2003 system, but not in the XP system. You can download it online, put it in the system32 directory and then register it. This tool is connected to the server console number 0, which is the local operation start->run->cmd-> tsmmc .msc -> New Remote Host -> Enter Server Account Password Login Server 2. Method 2 Step: Start -> Run -> cmd-> mstsc /console /v: Server IP: Remote Port -> Input Server account password login server 3. Method 3: Configure group policy to limit connection time start->Run->gpedit.msc->Computer configuration->Administrative template->Windows component->Terminal service -> The right window of the session selects the time limit for the disconnected session -> Select is enabled, select a time to avoid the failure of the remote maximum number of connections! 4. Method 4 Windows
Server 2003 allows the number of remote terminal connections to be 2 users by default. We can increase the number of simultaneous remote connections at the same time as needed. Click “Start →Run”, enter “gpedit.msc”Open the Group Policy Editor window, and then navigate to “Computer Configuration & Rarr;Administrative Templates & Rarr;Windows Components & Rarr;Terminal Services”, double click right On the side of the "restricted number of connections", in the end, if you can't, use the most cattle method: restart the server.