I'm running Windows 10 Pro on a home network. No domain.
Background: As a developer, I use source control for my projects. I have many projects. They all reference the source control location like this: \sol\Data\SourceSafe. Now, SOL was my terastation (NAS). It died. All the data is now on my local PC called VAL. So my source control location is now \\VAL\Data\SourceSafe. However, I really really want to avoid changing that in all my projects.
Goal: I want to use some kind of trickery in order to have VAL respond as SOL, and thereby have \\SOL\Data\SourceSafe work again as if it has not changed physical location.
What I've tried so far
I've added an entry in my hosts file using the IP address of my computer, VAL:
I can now ping sol successfully.
However, inspite of having the 'alias' in place for the host name, I cannot use the Data share.
dir \\val\data\SourceSafe --> works dir \\sol\data\SourceSafe --> The user name or password is incorrect dir \\sol\data --> same
Mapping a drive letter and explicitly specifying my username and password (when prompted)
C:\WINDOWS\system32>net use * \\sol\data /user:swatt Enter the password for 'swatt' to connect to 'sol': System error 86 has occurred. The specified network password is not correct.
I have also tried adding the DisableStrictNameChecking registry entry and rebooting, but no change.
So, how can I make the \\sol\data\SourceSafe path work again?
Thanks much! Sandra