Visual SourceSafe uses normal Windows File APIs to do its work. If you can browse to \\host-name\vss-share-name through a windows explorer from your remote, then forwarding is set up correctly. Merely set up your VSS explorer or other VSS connectivity to connect to \\host-name\vss-share-name\srcsafe.ini (or whatever UNC path you use to get to srcsafe.ini)
Another alternative you may want to look at is something like
SourceOffSite (SOS). Due to its design, VSS databases running over a network share is not the most efficient, and you may encounter performance problems and sometimes VSS database corruptions. SourceOffSite mitigates those problems. SOS will sit as a server connected to your VSS database running on any port you like. An SOS client communicates to the SOS Server allowing you full access of your VSS database.
Good Luck,
Jeff Clausius
SourceGear