Thank you gus for the knowledge.

Ok,Server A(Back-up Source)...OS Win Server 2008 R2,SQL Server R2

Server B (Back-up Destination)...OS Win Server 2008 R2,SQL Server R2

Machine C(My workstation)...OS Win XP SP3

1.log on remotely on A and back-up on...

I have not seen any documentation about this.

Apply the most recent transaction log to your mirror server and leave it.If you get the same error to reapply again.

If I perform the latest full back-up i will not need the previous log back-ups right.

What's wrong with running a maintenance plan thats does log back-ups for my databases and store in a folder on the same machine.If I were to burn the log back-ups...

Nice question.Hough difficult for me.Really learnt something thanks.

Thank you all,that's the first question i have contributed and like this.

It depends with how your application connects.If you are using SQ L Server native client,it will know that the server has changed.Otherwise you will have to manually change the connection...

Oh,I had missed the last part...Thanx.

Remove mirroring and reset again,that is how i do it.

You cant change anything on the mirrored databases.

Just out of interest,what is the impact of using different ports on different boxes?What difference does it make?

You can always increase the timeout.But what is probably more critical is to identify the cause for the time outs.

Thank you for the advice.