I saw a lot of these recently (and status 25 as well).  It was because
our master had two NICs in our backup LAN IP range and the routing we'd
setup had gotten screwed up.   I was able to solve it temporarily by
adding the master server twice to /etc/hosts on the clients that were
failing using both the IPs from the NICs on the master.  That way
regardless of which IP the traffic came from the client would see it as
the master.

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of monalisa
Sent: Wednesday, January 07, 2009 1:32 AM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] socket read and write error


can anyone tell me what can be the reason of socket read and write error
with error code 23 and 24 in NBU.

+----------------------------------------------------------------------
|This was sent by monalisa.kundu AT wipro DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential 
information and is for the sole use of the intended recipient(s). If you are 
not the intended recipient, any disclosure, copying, distribution, or use of 
the contents of this information is prohibited and may be unlawful. If you have 
received this electronic transmission in error, please reply immediately to the 
sender that you have received the message in error, and delete it. Thank you.
----------------------------------

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu