After working on this problem for days, I happened to stumble upon the answer (in my case anyway). The workstations that were not working did not have name resolution...
A DBCC Check does report it as corrupt (although cannot repair it with any repair options), I am more interested in trying to figure out how this happened.
Just wanted to report back that I have actually solved this problem. In my case someone had added an invalid Named Pipes alias in the client network utility on...
Backing up to a local hard drive, no tape drive even installed and there is plenty of disk space (all 4 databases total less than a gig and there is...