Sửa lỗi no more connect to this computer năm 2024
in My office, one of the computer is connected with domain environment, suddenly domain users are not able to login, it gives the error "The password is incorrect. Try again". but my password is correct, the same error for all users. Removed the computer name in AD but no use. When I try to login local administrator, its throughs same issue " The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator." This system has critical information, i do not want to reinstall the windows. Show I have searched solutions in internet; I could see registry edit options only. Tried to do that but without login to windows how can I edit that. I tried few steps such as Removing network cable/ tried to login – not working, created windows repair device in USB, repair option did not solve my issue, system not booting in safe mode to restore previous version, even image backup in Veeam also has the same problematic OS. suspected in two areas and tried to workout.
I have made a Bootable media using Hiran bootable, for windows 20 64 bit Moved all files stored in %WINDIR%\system32\drivers\etc\ to a different folder, no files here. Then Rebooted the windows system, it goes normally. I could see the critical application and its data. This is saved our company business downtime. Its the first day of school and we have more computers than ever on the network. In the computer lab, the first 10 computers were able to log on to the server 2008. After that I tried to join a computer to the domain and it gave me the following error: your computer could not joined to the domain because the following error has occurred: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. 36 Replies
I have not seen this command. Use it on the server or the workstation? A workstation in Run, assuming RDP of course. Was this post helpful? thumb_up thumb_down I also had exactly the same message. After some digging around I noticed the System Clock was 5 minutes out!!! N:\>w32tm /query /source Free-running System Clock N:\>w32tm /config /manualpeerlist:time-a.nist.gov,time.nist.gov The command completed successfully. N:\>net stop w32time The Windows Time service is stopping. The Windows Time service was stopped successfully. N:\>net start w32time The Windows Time service is starting. The Windows Time service was started successfully. N:\>w32tm /query /source Local CMOS Clock N:\>w32tm /query /source time-a.nist.gov,time.nist.gov Was this post helpful? thumb_up thumb_down No More Connection to a Remote Computer Problem 1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click to select the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters 3. On the Edit menu, point to New, and then click DWORD Value. 4. Type MaxMpxCt, and then press ENTER. 5. Right-click MaxMpxCt, and then click Modify. 6. In the Value data box, type the desired value, and then click OK. Note You can set the number of concurrent SMB commands to a value that is between 10 and 255. The default value is 10. In Microsoft Windows Server 2003, you can set the number of concurrent SMB commands to a maximum value of 65,535. 7. Close Registry Edit Was this post helpful? thumb_up thumb_down Make sure the time on the client computer/server are the same as the domain controller. Also check to make sure the time zone on the client appropriately offsets the time. This can happen if the time is more then 4 minutes different. Was this post helpful? thumb_up thumb_down thanxs ldavis wrote: Its the first day of school and we have more computers than ever on the network. In the computer lab, the first 10 computers were able to log on to the server 2008. After that I tried to join a computer to the domain and it gave me the following error: your computer could not joined to the domain because the following error has occurred: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. Was this post helpful? thumb_up thumb_down This error is caused by the limitation of Windows XP Professional to 10 connection only. To solve this problem, you have to edit your registry. Follow this steps; 1. Click START -> RUN 2. Type regedit 3. Go to \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon 4. Look for cachedlogonscount 5. Replace its value to your desired number of connection, for example 15. That’s it! Was this post helpful? thumb_up thumb_down To solve this problem, you can reduce the timeout time of 15 minutes to 1 minutes so that the idle connections are terminated soon and other connection can be established. Follow the below steps to change the default timeout time to 1 minute instead of 15 minutes: 1. Go to Start > Run net config server /autodisconnect:1 and press Ok. You can also do this in CMD. Open CMD and write the following net config server /autodisconnect:1 hit enter. Hope your problem will be solved. Thanks :-) Was this post helpful? thumb_up thumb_down thanks worked well Was this post helpful? thumb_up thumb_down Please, I tried all the options on window 7 (64 bit), yet the problem is still the same. Can anyone tell me of other alternatives that worked? Was this post helpful? thumb_up thumb_downRead these next...
Hard Lessons From Romance ScamsSecurity Seeing as this is Valentine’s Day, I should have written something about rom coms, true love, and trusting your heart more. But this is not one of those posts. This post is about romance scams and how hard they are ... |