log shipping problem

In our enviornment we have many databases that participate
in log shipping to a standby server. I find that every
once in a while the restore of the log will fail with the
following error (Example)

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 4305:
[Microsoft][ODBC SQL Server Driver][SQL Server]The log in
this backup set begins at LSN 11797000000035000001, which
is too late to apply to the database. An earlier log
backup that includes LSN 11715000000012500001 can be
restored.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
is terminating abnormally.

What I find is that there is no missing log file. My
first thought was that a log file didn't copy over
correctly. Basically its the next log that was backed up
and copied over and now trying to be restored. So where
did these missing transactiong go? To log heaven maybe?
What I do notice is now that also where my trn files are
there is a new file with a TUF extension. Is this where
my missing transactions are? Can I restore this file?

So do i have any other options here rather than deleting
log shipping and reinitalize the destination database once
again. Thanks

rcronin@.apcc.com

.The error 4305 indicates that the restore operation found a gap between
the last restore and the transaction log that you attempted to apply.
So, to resolve this error you should restore transaction logs in the
same order in which they were backed up.

Make sure to refer SQL error log on both the machines and take network admin help to find out any network bottlenecks.

By any reason if this occurs, just restore the full database on secondary server and restart LS.sql