|
|
Posted by Erland Sommarskog on 05/21/06 17:19
pb648174 (google@webpaul.net) writes:
> I used the same script and specified a bogus machine name and got
> "Specified SQL Server not found", so it isn't a network issue I
> guess... I'm at a loss as to what to do from here.
Yes, that's the message I would expect if the server is entierly
unavailable. But what if some packets make it, and others not?
I'm about as lost as you are, but what about running ping -n 200 in
conjunction with running the backup job, and then check for packet
loss?
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|