Solved

How to clear Windows Error 53?

Posted on 2012-03-13
5
644 Views
Last Modified: 2012-08-20
Hi everyone,

During a backup to NAS device last night, one of our servers quit talking to the NAS box.  A MUP event 139 was logged on that server.  The server was running Symantec Backup Exec 2010 R3.

I backtraced the reason for the failure: the domain controller the NAS uses for authentication of SMB clients ran out of disk space, and quit being a domain controller.  I fixed that probem and rebooted the domain controller.

On the server which had the connectivity hiccup, I can ping the NAS device by IP address, netbios name, or by FQDN.  However, if I try a net use \\<device name>\share (which uses NETBIOS), I get a windows event 53.  This works correctly against an identical twin NAS.

Further, I can connect to the NAS that the server can't using netbios and other domain members.

I did reset Symantec Backup exec by restarting the Backup exec services (since the backup job wouldn't quit nicely).  The server in question is a physical machine (not a VM).  

It is not a firewall issue (as Microsoft seems to imply)-I disabled Symantec Endpoint Protection 11.06a (which the server is running).

I rebooted the NAS box, also.  How can I clear up the Error 53 condition without rebooting the server?
0
Comment
Question by:FlyboyData
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
5 Comments
 
LVL 23

Expert Comment

by:ComputerTechie
ID: 37719709
try the following:

ipconfig /flushdns
ipconfig /registerdns

it will disrupt the server connection for a few seconds.

CT
0
 

Author Comment

by:FlyboyData
ID: 37722558
Okay, will try that the next time it happens...it happened again last night :(  I cleared the error 53 by rebooting the system.
0
 

Author Comment

by:FlyboyData
ID: 37744734
ipconfig /flushdns followed by ipconfig /registerdns does not solve the problem, unfortunately...
0
 

Accepted Solution

by:
FlyboyData earned 0 total points
ID: 38298471
The problem is due to a poor CIFS stack implementation by the NAS vendor, which is not robust under heavy SMB traffic.  We solved the problem by using a different NAS to back up to.
0
 

Author Closing Comment

by:FlyboyData
ID: 38311012
Months of debugging (including tech support from the NAS vendor) has lead me to the conclusion that I reached.  The only thing which solved the problem was switching to a different NAS vendor, whose devices had full Symantec Backup Exec certification.
0

Featured Post

Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is an update and follow-up of my previous article:   Storage 101: common concepts in the IT enterprise storage This time, I expand on more frequently used storage concepts.
Is your phone running out of space to hold pictures?  This article will show you quick tips on how to solve this problem.
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting. This w…

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question