Here’s an odd one.
My organization has two accounts for users like me. My normal account, and an “admin_” prefixed account.
When I connect to network shares on most servers, I connect with the “admin_username” account (from here on called the admin_ account) rather than my normal “username” account.
This has been the pattern for literal years, since sublime 2.
This issue popped up with sublime 3, and I just dealt with it. Every 90 days, when I change my password, it would happen. From then on, when I reboot, usually monthly, it happens again.
Now with sublime 4, it’s happening like 6x a day, which is too much to deal with.
I’ve edited my Session.sublime_session to remove all history of network files, all instances of ANY network path, yet it still persists.
Where on earth is it caching the network credentials, and… why is it doing it? My admin_ account won’t be locked out for hours, and hours, even a day! (I used VS code, rather than sublime for a day. It wasn’t ideal)
The INSTANT I open sublime, which pauses for roughly the amount of time it takes to fail connecting to a file share, if I try to use that account, it’s locked out, and I have to unlock it.
What am I missing? Any help? I searched 3x and couldn’t find anyone with a similar issue.