No, not really... that just means that the remote file share was unavailable. This is typically due to a "burp" in the network or the server itself.
Most folks are currently thinking that this is a problem that Microsoft will need to fix... to make their application a bit more tolerant of minor network burps.
There already is a formal "bug fix" submission for this... so obviously they are aware of it.