System error 53 has occurred the network path was not found

С ошибкой 53 «не найден сетевой путь» можно столкнуться при попытке получить доступ к общим папкам и файлам по локальной сети. Узнаем подробнее, как ее исправить?

Чем вызвана ошибка?

Сбой при подключении по указанному сетевому пути может произойти по следующим причинам:

1. Установка соединения по сети блокируется брандмауэром или антивирусной программой.
2. Подключение ограничено фоновым процессом, который вмешивается в работу компонентов сети.
3. Отключен общий доступ к содержимому на удаленном компьютере.

Подключение с помощью командной строки

Если пытаетесь получить доступ через командную строку, проверьте правильность написания команды. Она должна отображать адрес сервера и папки, удаленного компьютера.

Откройте командную строку от имени администратора с помощью системного поиска.

В консоли введите команду, придерживаясь следующего формата:

net use F: «\servershare»

Где server – имя компьютера, share – наименование общей папки.

Проверка ping

Чтобы узнать, правильно ли работает сетевой сервер, запустите ping тест и проверьте, есть ли ответ. Кроме того, с помощью этого теста можно проверить, есть ли потери пакетов, что также приводит к ошибке 53. Для его запуска выполните указанные шаги.

В строке системного поиска наберите cmd, при отображении искомого результата щелкните на запуск от имени администратора.

В консоли запустите команду для проверки связи с сервером или компьютером:

ping (IP-адрес сервера)

Если команда возвращает все пакеты без их потери, это значит, что сеть настроена правильно. В противном случае проверьте настройки сети.

Отключение антивирусной программы

Если ping возвращает все пакеты, попробуйте отключить антивирусную программу, чтобы узнать, причастна ли она к этой ошибке 53. Есть много случаев, когда антивирус препятствует подключению к папке по сети. Поэтому временно отключите его и посмотрите, установлено ли соединение между устройствами.

Включение общего доступа

Иногда совместное использование файлов может быть отключено с Панели управления. Для включения, выполните следующие шаги.

Откройте Панель управления командой control из окна «Выполнить» (Win + R).

Переключите режим просмотра в правом верхнем углу на крупные значки и перейдите в раздел «Центра управления сетями и общим доступом».

На левой панели щелкните на вкладку «Изменить дополнительные параметры общего доступа».

Разверните профили «Домашний и рабочий» и «Общий». Отметьте флажками опции «Включить сетевое обнаружение» и «Включить общий доступ к файлам и принтерам» обоих профилей.

Сохраните изменения на «Применить», закройте окно. Попробуйте подключиться к общему ресурсу, к которому ранее не удавалось из-за ошибки 53.

Если по-прежнему не удается подключиться по сети, попробуйте это сделать из режима чистой загрузки. Если в этом режиме ошибка не препятствует получению доступа, то причина в стороннем фоновом процессе. Для его поиска включайте одно за другим приложения, пока не обнаружите то, которое вызывает ошибку 53.

Many users have recently faced the error “System 53 Error has Occurred” on their network computers. This annoying error has mainly plagued older operating systems.

In this post we will talk about some of the reasons for this error and offer practical solutions to fix it completely. To avoid conflicts, perform the actions in exactly the same order as they are presented.

Here’s the complete error message:

System error 53 has occurred.
The network path was not found.

What is the Cause of the “System 53 Error has Occurred”?

• Connection Problem – Perhaps two computers were not properly connected or the network to which they are connected has problems. In this case, the problem with the Ethernet cable, router or configuration can occur between the computers. These problems need to be checked and corrected by troubleshooting using various options.
• Security Software – In some cases, security software installed on one of the two computers may prevent the connection between the two computers. Security software can detect a connection as malicious and completely block it, causing this error.
• Background Applications – Some background applications/tasks may also prevent proper connection. These background processes can affect important system functions, one of which can be a network function.
• Sharing is Disabled – In some cases, access to files and folders on your computer or network card may be disabled. This option can be configured on the control panel and must be enabled for the connection to work properly.
• Wrong Sharing Folder Command – Most users have experienced problems because of an incorrect command that was executed during sharing. It is recommended that you use the correct command with the appropriate format to share the folder.

How to Fix the “System Error 53 has Occurred”?

Solutions 1: Disable the Firewall via Group Policy

To solve this problem, you can create a firewall locally, through Group Policy, or create remote management exceptions locally, or through Group Policy.

1. To manage the firewall through Group Policy (or Local Policy), go to the Computer page at ConfigurationAdministrative TemplatesNetworkNetwork ConnectionsWindows Firewall[Domain,Standard] Profile.
2. For computers that are part of a domain, use the domain key.
3. For standalone systems, use the local key.
4. For notebooks that are on the network, not the network, change both.
5. To disable the firewall, set the Protect All Network Connections Policy setting to Disabled.

Solutions 2: Check if File and Printer Sharing for Microsoft Networks is Enabled

1. Click Start, then click Computer.
2. In the Computer window, open the folder that contains the folder that you want to share.
3. Right-click the folder that you want to share, and then click Share. The File Sharing window opens.
4. If you are allowed to share using a password, in the File Sharing window, select the users who can access the shared folder and the level of their permissions. To allow all users, select All from the list of users. The default authorization level for the selected user is Reader. Users cannot edit files in the share or create new files. To allow a user to edit files or folders or create new files or folders, select Shareholder as the access level. Figure 5 shows an example of user configuration and authorization levels in the File Sharing window.
5. If password sharing is disabled, select Guest or All Accounts in the File Sharing window. This is the equivalent of just sharing files under Windows XP.
6. When you are finished, click Sharing, and then click Done.

To access a shared folder from a computer running Windows Vista:

1. Click Start, then Network. The Network window displays a list of workgroup computers on the computer. An example is shown in Figure 10.
2. Double-click the name of the computer that hosts the shared folder you want to access.
3. Double-click the shared folder that you want to access.

Solution 3: Check if NetBIOS Protocol is Enabled

To enable NetBIOS over TCP/IP in Windows:

1. Click Start, then Network. (Or, enter ncpa.cpl in the search box and press ENTER).
2. Click Network and Sharing Center, and then click Manage Network Connections.
3. Right-click on the Local Area Connection or connection you are using and select Properties.
4. Select Internet Protocol Version 4 (TCP/IPv4).
5. Click the Advanced button on the General tab.
6. Click the WINS tab.

Solution 4: Check if Ping can be Performed using CMD Prompt

Verify that you can ping the command with a CMD request (by IP address or NetBIOS physical name) and that the remote host responds without significant packet loss. If the remote machine does not respond when its hostname is jammed, but when it is jammed by its IP address, please check the DNS properties of the remote machine. This point should be taken into account because many of the features of our products use name resolution when trying to access remote hosts.

Solution 5: Check Networking in Safe Mode

If all of the above methods do not work, the network must be tested in Safe Mode. At this point, the computer will go into Safe Mode to determine if the application is the cause of the problem.

1. From the Start menu, click Shift and simultaneously click Restart to open WinRE.
2. In the Troubleshooting section, select the appropriate option and then Advanced Settings.
3. Select Enable Safe Mode with Networking in the advanced settings and wait for the computer to start.
4. In this mode, check whether there is a “System Error 53 has Occurred” error.

Conclusion

Errors like this are sometimes hard to troubleshoot and fix. Hopefully you found help through this guide. If you have any questions, ideas or suggestions, feel free to leave comments.

— 1 — Check that you can ping with the CMD prompt the remote host (by its IP address or by its physical NetBIOS name), and that the host answers without significant packet loss. If the remote host does not answer when it is pingued by its hostname but answer when pingued with its IP address, please check on the remote host the DNS properties. This point should be considered because a good many functionalities of our products use the name resolution when trying to to access remot hosts.

— 2- If your station is in a Windows Active Directory domain, in this case check if you «ping» the remote machine by using its full name: ping remotecomputer.pointdev.local (or remotecomputer is the name of the remote computer and pointdev.local the name of your Active Directory domain). If the ping responds correctly, check if the option Append parent suffixes of the primary DNS suffix is activated on your network card: Properties of your network card, Advanced button …, DNS tab. You can also add suffixes manually if needed (option Add these DNS suffixes (in order)).

— 3 — Check on the local computer and on the remote host that there is no security hardware or software blocking or filtering the communication between the local and remote machines (firewall / antivirus / router …). If necessary rules have to be instaured (port opening, port translation …) in order to allow the communication between the two machines.

Windows is a popular operating system with more than one billion active users. Its popularity is credited to its user-friendly features, including the ability to link computers through a network.

While it’s such a handy feature, a lot of Windows users reportedly encountered the “System 53 Error Has Occurred” error. So, what’s this issue all about and can it be resolved?

In this article, we will share the most common reasons that trigger this error. We will also provide you with viable fixes. As long as you follow the solutions properly, you can surely get rid of the problem.

What Is “System 53 Error Has Occurred” Error on Windows 10/11?

When a Windows user tries to establish a connection to a network using the net use command or through the Map Network Drive, the error code 53 may show. This means that the network path was not found by the system. This error occurs because no DNS name resolution was performed. It can also show if a machine is not properly registered with the server.

What Causes “System 53 Error Has Occurred” Error on Windows 10/11?

Below are some possible factors that can trigger the error:

• Connection problem – It is possible that two computers are not properly connected or the network they are connected to is having problems. It could be in the router, ethernet cable, or in the network configuration.
• Background apps and processes – Some background processes and applications can keep the connection from being properly established. As a result, important system functions are disturbed, and this could include the networking function.
• Security software issues – Sometimes, the security software program installed on either of the computers is preventing the connection from being successfully established.
• Disabled sharing – The sharing of folders and files between a computer might be disabled by the network card or the computer itself. However, this can be easily configured and enabled in the Control Panel.
• Incorrect execution of shared folder command – Like many users, the issue can be triggered by an incorrect execution of the shared folder command.

What to Do About “System 53 Error Has Occurred” Error on Windows 10/11?

Now that you have fully understood what causes the error message to appear, we will share with you some ways to resolve it. We suggest implementing the solutions in the recommended order to avoid having problems.

Here are several ways on how to fix “System 53 Error Has Occurred” error on Windows 10/11:

Solution #1: Use the correct command

As mentioned above, the error may surface when you execute the wrong command. Make sure that the command displays the address of the folder and the server to be shared. They need to be separated in commas.

For a clearer guide on what to do, follow these steps:

1. Press the Windows + R keys to launch the Run utility.
2. Input cmd and hit Enter to open the Command Prompt.
3. Type the net use F: “\servershare name” command.
4. Hit Enter.
5. Check if the issue persists after entering the command.

Solution #2: Run a Ping Test

The best way to confirm that you are experiencing a network server problem is to perform a ping test. Make sure the server responds to the ping.

To perform a ping test, do the following:

1. Press the Windows + R keys to launch the Run tool.
2. Input cmd into the text field and hit Enter.
3. Type the ping (IP address of the server) command and hit Enter.
4. If you get a reply, then it means that your network is properly set up. Otherwise, your connection is not set up correctly. Troubleshoot the problem according to the result of the test.

Solution #3: Disable your security software

If the ping test returns a good response and the server is detected, try to disable your security software first. It is possible that it is causing the problem.

There are instances when the installed antivirus on your computer will keep you from accessing a folder saved on a network. In this case, disable your antivirus and check if the folder can be accessed on the network.

To disable your antivirus software, do the following:

1. Go to Start and select Settings.
2. Navigate to Update and Security and choose Windows Security.
3. Next, go to Virus and Threat Protection and click Manage Settings.
4. Now, switch off real-tome protection. Take note though, scheduled scans will still continue to run.

In addition to disabling the security software, you may also try disabling the firewall. To do so, refer to the guide below:

1. Navigate to your computer’s configuration folder and select Administrative.
2. Choose Templates and click Network.
3. Select Network Connections and then choose Windows Firewall Profile.
4. In this section, disable the Protect All Network Connections Policy setting.

Solution #4: Enable file sharing

The sharing of files between computers might also be temporarily disabled, hence the error message. To fix this, change the settings and enable file sharing between devices. Here’s how:

1. Press the Windows + R keys to launch the Run utility.
2. Input control panel and hit Enter to launch it.
3. Select Network and Internet Settings and hit the Network and Sharing Center button.
4. Click Change Advanced Sharing Settings.
5. Tap on the All Dropdowns section and tick the Turn On Network Discovery and the Turn On Printer and File Sharing options. Make sure to enable these options for the Guest and Private Networks as well.
6. Hit the Apply button to save the changes.
7. Close the window and check if the issue persists.

Solution #5: Boot in Safe Mode

In this solution, you will have to launch your computer in Safe Mode. And from here, you may check if an application is causing the problem. Here’s how to do that:

1. Restart your computer and hit F8 successively.
2. Wait for the boot options screen to show and choose Advanced Boot Options.
3. Choose Safe Mode with Networking and wait for your computer to boot up.
4. Check if the problem exists in this mode. If it doesn’t, this means that a background application is causing the issue. So, disable all your applications one at a time and check if the issue goes away. If you have found the faulty application, you have the option to uninstall it or have it disabled.

Solution #6: Check if the NetBIOS protocol is active

A disabled NetBIOS protocol can also trigger the error message to show. To enable this protocol on your Windows device, follow these steps:

1. Go to the Start menu.
2. Navigate to Network.
3. Click Network and Sharing Center and select Manage Network Connections.
4. Right-click on the Local Area Connection option or the connection you are currently using.
5. Select Properties and click Internet Protocol Version4 (TCP/IPv4).
6. Hit the Advanced button and navigate to the General tab.
7. Click WINS and exit the window.

Solution #7: Run a malware scan

Malicious components are notorious for causing system errors like system error 5016. So, we cannot rule out the possibility that the system error that you’re seeing is caused by a malware entity or a virus.

To get rid of viruses and malware entities, you may run a malware scan automatically or manually. If you choose to run an automatic malware scan, you need to install a reliable antivirus software program. And then, run a complete scan and follow the suggested fixes. Most of the time, you will be given the option to quarantine the malicious entity or get rid of it completely.

Should you prefer to run a manual scan, you will need the help of Windows Defender. And just like performing an automatic virus scan, you will be asked whether you wish to remove the problematic entity or quarantine it. The decision is up to you.

For a guide on how to use Windows Defender, follow these steps:

1. Click the Start menu.
2. Into the search field, type windows defender. Click on the most relevant search result.
3. At this point, you will be asked to check for updates. If you wish to do so, click the Check for Updates Now button.
4. Now, you may proceed with the performing a complete scan by clicking the Scan button.
5. Windows Defender will now scan your computer and notify you if any malicious entity or process is found.
6. Once done, restart your PC and check if the error message persists.

Wrapping Up

Yes, a lot of users may be facing the “System Error 53 Has Occurred” error when using a computer connected to a network. This error may surface due to a connection issue or a problematic background application. It can also appear because of incorrect share folder settings or limitations set by the security software. But the good news is that it can be easily resolved.

By using the correct command or by running a ping test, you can identify what’s causing the problem. From there, you can troubleshoot. If it doesn’t work, you can also try disabling your security software like what other Windows users did.

Now, if you know other solutions that can resolve the “System Error 53 Has Occurred” error on Windows 10/11, please do share them below!