Azure network error 1233, error 53 path not found

If you have an Azure VM that is suddenly getting errors including

  • Error 53: The network path was not found
  • Error 1233: The network location cannot be reached
  • Server can’t be pinged but can ping out

After ensuring that the firewall settings are ok (or if you know 100% this was working and now after a restart of the VM it is not…  then check Device Manager, from the View menu ensure that Show Hidden Device is ticked.  Expand Network Adapters and confirm that there are no hidden and unused Hyper-V network adapters

The module used was obtained from TechNet but for simplicity I have included it in the download below along with a wrapper script to call the required cmdlet.  Before running the script open a PowerShell session with Run As Administrator and call

Set-ExecutionPolicy RemoteSigned

to allow the script to be used.  The download can be unzipped on your server in any location and then you can right-click on the file Remove-AllHiddenHyperVNIC.ps1 and choose Run with PowerShell.  It will remove all hidden Hyper-V NICs from the server.

After that reboot the machine and access will be fully restored

*** As always the script is provided on an as is basis, please test it before you use it in a production environment. ***

Device Management

 

Twan van Beers

Twan is a senior consultant with over 20 years of experience. He has a wide range of skills including Messaging, Active Directory, SQL, Networking and Firewalls. Twan loves to write scripts and get deep and dirty into debugging code, in order to understand and resolve the most complex of problems.

Leave a Reply

Your email address will not be published. Required fields are marked *

Search