Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ARCserve E3392 TCP timeout

Status
Not open for further replies.

Mohnkern

MIS
Joined
Feb 22, 2007
Messages
2
Location
US
I have already read through the CA Support article: Threads related to this issue do not indicate successful solutions.
RE: "E3392 Backup server TCP reconnection timeout. (AGENT=<IP> (Server Name), Network Error=0x274c"

I currently have E3392 TCP timout errors with 3 different codes (0x2746, 0x274c & 0x9).

These errors are sometimes inconsistent and sometimes occurring on the same session (I have both scenarios).
* AntiVirus does not scan at the specific time.
* Client versions are all 11.1 SP2.
* Specifying IP address, nor priority in client does not fix.

We are in process of swapping NIC cards, but there are org. hurdles to do this. In the mean time, has anyone successfully fixed these errors?

Also see: thread861-1267522 & thread861-1129499

Thanks All!
Rick
 
Consider this: those TCP errors are about as generic as you can get and a problem at any place from one end to the other and everything in between can result in the errors.

So CA puts together a bunch of settings to slow down the client agent backup which often will let the backup wait out the problem and let the backup complete.

So whats to be done?
Well start at one end and go down to the other and check everything in between. Sounds like fun huh. Anyways here are something to work with.
1)try it without the client agent. this will basically backup just data, but the idea is to see if it will consistently work. If it does then ck target end for anything that might be conflicting with the agent.
2) set the agent for low priority. yes low, in the hope it will play nice with other apps and complete the job.
3) set up logging on the switch. goal is to track errors and see if that are on the ARCserve server side or target system side. This will at least give you a direction to look.
4) ck Event Viewer for messages from the NIC or IP stack.
5) setup Network Monitor at both ends to see if one or the other traps errors. This will at least narrow it down.

my mind has already gone on to other things but this at least gives you something to try.
 
Thanks! I have tried most of those, except I set priority to 'high' of course.

Thanks again - I was really hoping for the cure-all!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top