STATUS_OBJECT_NAME_NOT_FOUND

Hi Everyone,

I've been having issues with backing up servers in my LAN with backup exec;
I constantly get connection drops and end of data unexpectedly set errors -
so I decided to just do a simple file copy from the local server to a shared
folder on the backup server's SAN.

I ran a packet capture on the local server to see what's going on - and when
I started the file copy (about 250 MBs in size), it went half way through
the progress bar and paused, then gave me an error: "The specified network
name is no longer available", and closed the copy dialog box when I clicked
OK. Oddly enough, when I checked the backup server's shared folder, the file
was copied.

I opened the packet capture and scrolled down to see where I can find an
error, and I saw dozens of packets with STATUS_OBJECT_NAME_NOT_FOUND - and
at the end "Close Response"...

Has anyone seen this kind of behavior - or have a suggestion on where I
should put my focus onto to further isolate the issue?

Thanks,

Ali

Updates:



In the packet capture, I see a lot of checksum errors ("maybe caused by
checksum offloading").



I've disabled offloading on the local server, not the backup server, and
still persists.



Thanks,



Ali





"Ali" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> Hi Everyone,
>
> I've been having issues with backing up servers in my LAN with backup
> exec; I constantly get connection drops and end of data unexpectedly set
> errors - so I decided to just do a simple file copy from the local server
> to a shared folder on the backup server's SAN.
>
> I ran a packet capture on the local server to see what's going on - and
> when I started the file copy (about 250 MBs in size), it went half way
> through the progress bar and paused, then gave me an error: "The specified
> network name is no longer available", and closed the copy dialog box when
> I clicked OK. Oddly enough, when I checked the backup server's shared
> folder, the file was copied.
>
> I opened the packet capture and scrolled down to see where I can find an
> error, and I saw dozens of packets with STATUS_OBJECT_NAME_NOT_FOUND - and
> at the end "Close Response"...
>
> Has anyone seen this kind of behavior - or have a suggestion on where I
> should put my focus onto to further isolate the issue?
>
> Thanks,
>
> Ali
>