3 Replies Latest reply on Sep 1, 2017 8:19 AM by Andre Thompson

    dropped because peer didn’t respond

    cpo

      I've been getting this error quite frequently "dropped because peer didn’t respond". Most of the errors are associated with duplicate names for the logs themselves. The issue seems to stem from the server attempting to rename the file, which causes the whole process to come to a halt.  When the log is renamed by checking the (Rename existing files on conflict) box , the file gets hung up and never reaches the destination. When the log is overwritten by not checking the box, I’m losing data. Anyone else experiencing this issue?