Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 651
  • Last Modified:

How to clear Windows Error 53?

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
FlyboyData
Asked:
FlyboyData
  • 4
1 Solution
 
ComputerTechieCommented:
try the following:

ipconfig /flushdns
ipconfig /registerdns

it will disrupt the server connection for a few seconds.

CT
0
 
FlyboyDataAuthor Commented:
Okay, will try that the next time it happens...it happened again last night :(  I cleared the error 53 by rebooting the system.
0
 
FlyboyDataAuthor Commented:
ipconfig /flushdns followed by ipconfig /registerdns does not solve the problem, unfortunately...
0
 
FlyboyDataAuthor Commented:
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
 
FlyboyDataAuthor Commented:
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
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now