This is an issue because VSS was never written with distribution in mind. The VSS client connects directly to the database file which needs to be on an accessible network share. Doing this over a less than 100% reliable network eventually results in database corruption. Bad news, and doubly bad news when you’re talking about the database that contains all your source code!
Turns out there’s a fix…
SourceOffSite (SOS) is the tool you’re looking for. It provides a new client that looks just like the VSS client you know and love but connects to a server that handles all the interaction with your VSS database. For locally connected clients you can still use the original VSS client and tools but remote users connect with SOS.
I used this extensively when I worked for a company that had developers in Syracuse, Seattle, Austin and London. Prior to adoption SOS we had significant VSS database corruption issues. With SOS these were a thing of the past.