|Maybe one of you have encountered this and fixed it or perhaps some sage advice is out there.
My laptop is Windows 10 Pro, and I have full admin rights. I travel between my home office and my customer location. At the customer location, I have a networked drive mapped to our development server file storage area:
N drive mapped to \\SwServer\Development
This server also hosts our SVN repositories, which will come into this story in a bit.
My laptop is mine, and as a consultant, I am not allowed to be a member of the domain (nor do I want to be). My credentials are entered, saved, and I can access this drive as you would expect.
Now I go home to my corporate office and I'm attempting to access the network drive using the customer supplied VPN software (global protect if it matters). Once connected (no error messages in the log), I cannot see the network drives. If I ping the server, I get timeouts. Okay, the network is screwed up somehow.
But here comes the weird part - our svn server is hosted on SwServer behind an Apache web server (standard SVN setup). I can access my svn repositories just fine. So, somehow the path from my laptop to the SwServer exists somewhere.
Something is screwed up. Any suggestions as to what to look for?
The odd thing is that I can go a week and things will work flawlessly, then it all comes off the rails....
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759