Remote shutdown 53 error

remote shutdown 53 error

Verify that the network path is correct and the target computer is turned on. System Error: 53, Cannot connect to the remote computer. Ensure that File &. › faq › faq-ideal-administration-system-error-53-error-. Error 64 - "The network name has been deleted". This builds on the premise of error 53 in a good way. It means that the target machine did shutdown properly and.

Commit error: Remote shutdown 53 error

Remote shutdown 53 error
Remote shutdown 53 error
Error code 150
Error in command line daemon tools
Restart-Service -force -Verbose

Check RDP Port and Windows Firewall Settings

In some cases, the administrator can change the RDP port number remote shutdown 53 error default 3389 to something else (although Microsoft does not recommend this). To check the current port on which the Remote Desktop service is listening on the computer, remote shutdown 53 error, open the registry editor (regedit.exe), and go to the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

Note the value of the PortNumber REG_DWORD parameter. Remote shutdown 53 error indicates the current TCP port assigned to the RDP service. In our example, remote shutdown 53 error, this is 3389 (d3d hexadecimal value). If you have a different port, you can change it to 3389 (in decimal), and restart the computer.

this computer can't connect to the remote computer server 2016

You can check the current Remote Desktop listening port number using PowerShell:

Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -name "PortNumber"

In order to check the RDP port on a remote computer, use the Invoke-Command command:

Invoke-Command -ComputerName computername1 {Get-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp -Name PortNumber

Windows remote shutdown: access denied

One thing to keep in mind is that, the computers you want to shutdown must be on the same network as the "controlling" computer.

There are many solutions to this, I simply chose this one.
This is a simple com port error_access_denied access issue. You will have access to certain computer some times, but that is not this case. To gain access of another computer for you to remote shutdown, you must execute the follow command in command prompt:

Replace with the computer ip/name you want to shutdown remotely, with the password to any administrator account of the remote computer and with the Administrator user account name. To list all the computers in your current Wi-Fi network, do. It'll give you the names of the computers. Unless you prefer an easier way: Click Start, then Right-Click Computer. Click properties, it should be named in there. IPC$ is supposed to be sbt internal consistency error. Sometimes it will not work. I do not know why.

Work cited here.

For example, we'll have a computer named CHOCOLATE, and an Administrator account on the current machine is Bob and the password is Joe:

Exporting Execution Results

"Run","Group","Machine","Container","Title","Severity","Description","Time","Error Code"

"'Shut Down' - 1/17/2018 6:34:46 PM - Processed: 1 Machine (Successful: 0, Warnings: 0, Errors: 1, Canceled: 0) - Duration: less than 1 sec","Dreamlight","W2003-x86-sp1","Floor 2\Office 203","Prepare Remote Agent","Error","The remote agent cannot be installed to the 'W2003-x86-sp1.Dreamlight.local (' Machine as the client operating system is no longer supported by the agent.","2018-01-17 18:34:46",

"'Retrieve MAC Address Task' - 1/17/2018 7:01:53 PM - Processed: 2 Machines (Successful: 2, Warnings: 0, Errors: 0, Canceled: 0) - Duration: less than 1 sec","Dreamlight","WXP-X86-SP1","Floor 2\Office 204","NetBIOS","Warning","The Blender game runtime error address could not be retrieved using the NetBIOS method. Command timed out.","2018-01-17 19:01:53",

"'Retrieve MAC Address Task' - 1/17/2018 7:01:53 PM - Processed: 2 Machines (Successful: 2, remote shutdown 53 error, Warnings: 0, Errors: 0, Canceled: 0) - Duration: less than 1 sec","Dreamlight","WXP-X86-SP1","Floor 2\Office 204","DHCP (","Warning","The MAC address could not be retrieved using the DHCP method, remote shutdown 53 error. Failed to read the MAC address from the '' DHCP server, remote shutdown 53 error. Could not connect to the DHCP server using the credentials specified within the Credentials view. Access is denied (Error code: 5).","2018-01-17 19:01:53","5"

"'Wake on LAN Task' - 1/17/2018 6:58:36 PM - Processed: 2 Machines (Successful: 2, Warnings: 0, Errors: 0, remote shutdown 53 error, Canceled: 0) - Duration: 10 sec","Dreamlight","W2003-x86-sp1","Floor 2\Office 203","WOL","Information","The 'W2003-x86-sp1.Dreamlight.local (' Machine is responding, thus it has been turned on successfully.","2018-01-17 18:58:46",

"'Wake on LAN Task' - 1/17/2018 6:58:36 PM - Processed: 2 Machines (Successful: 2, Warnings: 0, Errors: 0, Canceled: 0) - Duration: 10 sec","Dreamlight","W2003-x86-sp1","Floor 2\Office 203","IPv6 Link-Local Multicast","Warning","The WOL packet could not be sent using the IPv6 Link-Local Multicast method. A socket operation was attempted to an unreachable network (Error code: 10051).","2018-01-17 18:58:36","10051"

How to Fix the "Network Path Was Not Found" Error on Windows

Microsoft allows devices that are connected to the same network to access each other's data and share files remotely. When you need to use two devices simultaneously, this process of data and resource sharing can be quite useful. However, there are times when users encounter errors, which can make the process quite a hassle and unpleasant.

One such common issue is the "network path name was nvram checksum error nvram cleared found" error, which occurs when users attempt to connect to a remote device. If you are facing a similar problem, we have discussed six troubleshooting methods below that will help you fix the error in no time.

1. Double-Check the Path Names

If you encounter the "network path name was not found" error, then the first thing that you should do is double-check the path name you entered. A small mistake within the path name will prevent the system from finding the path to the connected network.

While you are at it, we also recommend checking if the device you want to share files with has the sharing feature enabled. If not, enable it and then try performing the action that was previously causing the error.

Here is how you can make the targeted drive on the remote computer shareable:

  1. Right-click on the targeted drive and choose Properties from the context menu.
  2. In the following dialog, head over to the Sharing tab and check the status of Network Path.
  3. If it says Not Shared, then click on the Advanced Sharing button.
  4. Checkmark the box associated with Share this folder and note the Share name of the drive.
  5. Once done, click on Apply > OK to save the changes.

You can now check if the drive is accessible after following the steps above.

2. Temporarily Disable Your Antivirus

Another common culprit that often prevents users from connecting to networks, sharing remote shutdown 53 error, and downloading applications from third-party sources is an overly-protective antivirus.

Antivirus’s job is to identify malicious activities and block them, but there are times when these security programs start labeling legitimate processes as threats as well, blocking them completely.

If you are using a third-party security program on your operating system, we recommend that you disable it temporarily and then try connecting to the remote computer and sharing files. If the antivirus was causing the problem, disabling it should fix the issue for you.

You can also try disabling Windows Defender if you are using it and see if that helps. However, once you are done sharing the files, make sure you enable the antivirus back immediately since keeping it disabled for a long period can expose your PC to threats.

3. Try to Connect Using an IP Address

You can also connect to the remote computer using the IP address. In this method, we will be using Command Prompt to make this work.

Here is what you need to do:

  1. Press Win + R to open Run.
  2. Type cmd in the text field of Run and hit Ctrl + Shift + Enter to open Command Prompt as an administrator.
  3. In the Command Prompt window, type the command mentioned below and hit Enter to execute it:
  4. Scroll down and bit and note down the address for IPv4 Address.
  5. Now, open a Run dialog again and paste the IPv4 Address you noted in the text field here.
  6. Click Enter and see if you can connect to the remote computer successfully.

4. Restart the TCP/IP NetBIOS Helper Service

To connect to a remote device and share files with it, certain services on Windows should be ssl citrix error 61 properly. One of the most important services, remote shutdown 53 error this case, is the TCP/IP NetBIOS Helper service. As such, we recommend that you restart it to ensure that it is working.

Here is what you need to do:

  1. Open Run by pressing Win + R.
  2. Type services.msc in Run and hit Enter.
  3. In the Services window, look for TCP/IP NetBIOS Helper and right-click on it.
  4. Choose Properties from the context menu.
  5. In the following dialog, click on the Stop button.
  6. Wait for a few seconds and then click Start.
  7. Now, expand the dropdown for Startup type and choose Automatic.
  8. Click Apply > OK to save the changes.

Once done, check if that fixes the issue for you.

5. Enable SMB 1.0

SMB is a network protocol that allows users access to shared files and printers on Windows. This is disabled by default in Windows, but enabling it can help you connect to a remote device and share files across the network.

In this method, we will enable it to share the files. However, remote shutdown 53 error, we strongly suggest that you disable it after usage since it is known to have some security vulnerabilities that can mess up your system.

Here is what you need to do:

  1. Type Control Panel in Windows search and click Open.
  2. In the following window, head over to Programs > Programs and Features.
  3. Choose Turn Windows features on or off from the left pane.
  4. Now, look for SMB 1.0/CIFS File sharing support and checkmark the box associated with it.
  5. Click OK to save the changes and check if the error is now fixed, remote shutdown 53 error.

6. Reset TCP/IP

Finally, if the methods above have not worked for you, then you can consider resetting TCP/IP, which will revert all the IP protocols and Remote shutdown 53 error entries to their default state.

This fix is known to fix almost all the network-related issues that pop up in Windows now and then, and will hopefully fix the error at hand for you as well.

Network Path Error, Resolved

Connecting to another device over the network and sharing files should be a seamless process. Hopefully, the troubleshooting methods mentioned above will help you get the network functionality up and running in no time. However, if the error persists, you can consider using another file-sharing service like Google Drive till Microsoft launches an official fix for this issue.

find "LIST"

As you can see, in our example, port 3389 is listening.


try connecting again if the problem continues contact the owner of the remote computer

Try to restart the Remote Desktop Services service. You can perform this action using the services.msc console or with the following command in the elevated PowerShell prompt:

get-service TermService

Remote shutdown 53 error - Let's talk

select PortNumber}

If a non-standard port is configured for Remote Desktop on a remote computer, you must specify the port number separated by a colon when connecting to the computer through the Remote Desktop Connection client. For example, rdp_server_name1:3320.

this computer can't connect to the remote computer server 2012

Also, check that the rule which allows incoming RDP connections is enabled in the Windows Defender Firewall settings.

  1. To do this, go to the Control Panel > System and Security > Windows Defender Firewall;
  2. Press the “Allow an app or feature through Windows Defender Firewall” > Change Settings;
  3. Find the Remote Desktop rule, and make sure it is enabled for Private and Public networks.the remote resource can't be reached

Hint. You can enable the built-in firewall rule for the Remote Desktop Service running on port TCP/3389 using PowerShell:

Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

If this built-in firewall rule is missing, you can create a new one:

New-NetFirewallRule -DisplayName "AllowRDP_connection" -Direction Inbound -Protocol TCP –LocalPort 3389 -Action Allow

Check your network connection profile. You may encounter various RDP connection errors if a Public profile is configured for your network location. Try changing it to Private.

You can change the network location using the Control Panel (Network and Internet > Status > Connection Properties), or with PowerShell.

Get current network profile:


Change network connection profile to Private:

Set-NetConnectionProfile -InterfaceIndex 14 -NetworkCategory Private

remoteapp disconnected there was a problem connecting to the remote resource

If you use a third-party firewall or antivirus, make sure it does not block incoming RDP connections. You can temporarily disable your antivirus software.

Next, check your network connection properties. Verify if the network connection status is set to Public. Change it from Private to Public if needed (Settings > Network & Internet > Status > Network status > Change connection properties).

your computer can't connect to the remote desktop gateway server

In some cases, you need to try resetting the winsock and IP stack settings for the network adapter on the remote computer. Open a command prompt with administrator rights and run the commands:

netsh winsock reset netsh int ip reset ipconfig /release ipconfig /renew ipconfig /flushdns

In Windows 10, there is a special option to reset network settings in Settings > Network and Internet > Status > Network reset.

After resetting the network settings, you need to reboot Windows.


RDP This computer can’t connect to the remote computer: a possible cause

Another possible cause of the RDP error may be a high level of security, which is not supported by older versions of the RDP client.

In this case, open the General tab on the RDP-Tcp properties window, and change the Security layer from default Negotiate to less secure RDP Security Layer.

the two computers couldn't connect in the amount of time allotted

Tip. Snap-in tsadmin.msc and RDP-Tcp Properties dialog boxes are missing in Windows Server 2019/2016 and 2012 R2. But you can configure the Remote Desktop setting using the local Group Policy Editor (gpedit.msc). The necessary policies are located in the following GPO section: Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.

RDP security level can be specified using the policy named Require user of specific security layer for remote (RDP) connections. Enable this policy, and in the dropdown menu select the RDPSecurity level. This will change the Remote Desktop security layer from the default Negotiate to the less secure RDP.

remote desktop connection this computer can't connect to the remote computer

Save the changes, update local GPO settings using the “gpupdate /force” command, and restart the Remote Desktop Service:

net stop TermService && net start TermService

RemoteApp Disconnected: Can’t Connect to the Remote Computer

In some cases, when connecting with Windows 10 to a remote desktop on Remote Desktop Gateway on Windows 2012 R2, an error occurs:

RemoteApp Disconnected

Your computer can’t connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance.

this computer cant connect to the remote computer

To fix this problem, you need to perform the following steps on the RDP client:

  1. Open the Registry Editor (regedit.exe);
  2. Go to the registry key HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client;
  3. Create a DWORD parameter with the name RDGClientTransport and the value 1;
  4. Restart the computer.

there was a problem connecting to the remote resource ask your network administrator

The RDGClientTransport parameter forces the clients to use the RPC/HTTP connections instead of HTTP/UDP to connect to the server.

If the above solution didn’t fix the RDP connection error, try to change the collection settings on the RDSH server side. Open properties of your problematic application collection, go to the Security tab, and uncheck the option “Allow connections only from computers running Remote Desktop with Network Level Authentication”.

your computer can't connect to the remote computer

If the RemoteApp Disconnected error occurs on only a single not-domain joined computer, it is possible, that the different LAN Manager/NTLM policy settings are used on the RDSH host and the desktop computer. Often, this can cause authentication problems.

Check current Network Security: LAN Manager authentication level policy settings on RSDH using the command gpresult /r c:\tmp\gpreport.html (inspect html file) or using rsop.msc (this policy is located in the section Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options). If LM and NTLMv1 protocols are disabled on your RDSH server (SendNTLMv2 Response only policy value), you must change the appropriate policy settings on the client side.

  1. To do this, open the local GPO editor (gpedit.msc);
  2. Go to the GPO section above;
  3. Enable the policy “Network Security: LAN Manager authentication level”, and set its value to SendNTLMv2 Response only;this computer can't connect to the remote computer the two computers couldn't connect in the amount
  4. Update the policies on the client with the command gpupdate;
  5. Check your RemoteApp connection.

Fix: Can’t Connect to the Remote Desktop Gateway Server

There is another error related to Remote Desktop Gateway which is used to deliver RemoteApps to users:

RemoteApp Disconnected.

Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address.

remote desktop can't connect to the remote computer

This error looks like this:

Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance.

If you are facing one of the errors above, then, most likely, the problem is that your computer can’t resolve the public FQDN name of your Remote Desktop Gateway server. In some cases, the public RDGW name can’t match the hostname.

To fix this problem:

  1. Open the Internet Information Services (IIS) Manager on the Remote Desktop Gateway server;
  2. Go to the IIS section Sites > Default Website > RDWeb > Pages > Application Settings;
  3. For the DefaultTSGateway value, enter the server’s FQDN public name of your RD Gateway server, and then restart the web services with the command:iisreset

Also, check your RDGW certificate. Your certificate must not be expired.

You can find your SSL certificate info by going to Server Manager > Remote Desktop Services > Collections > Your_Collection > Tasks > Edit Deployment Properties > Certificates > RD Gateway > View Details. Check the certificate expiration date.

remote desktop this computer can't connect to the remote computer

Go back to your client’s PC, and try to start a new RDP session. The connection should be established successfully.

Remote Desktop Connection: Error Code 0x904, Extended Error Code: 0x7

In modern versions of Windows 10/11 and Windows Server 2016/2019/2022, you may encounter another common RDP connection error:

Remote Desktop Connection

This computer can’t connect to the remote computer.

Try connecting again.

Error Code: 0x904

Extended Error Code: 0x7

rdp there was a problem connecting to the remote resource

Most often, when connecting to RDP, an error 0x904 appears on an unstable network connection (not enough bandwidth, packages lost, mismatch encryption cyphers, etc.), or when your VPN connection to a corporate network is too slow. Try to reconnect to your VPN workspace or change your ISP.

Cyril Kardashevsky

Cyril Kardashevsky

I enjoy technology and developing websites. Since 2012 I'm running a few of my own websites, and share useful content on gadgets, PC administration and website promotion.

Cyril Kardashevsky

Latest posts by Cyril Kardashevsky (see all)