XYplorer startup appears to cause corporate account lockout
Posted: 31 Aug 2017 22:31
Thanks for the excellent software. Please bear with me while I describe a situation that I'm not liking.
I use XYplorer in a variety of work contexts. In particular, I store network-drive-based locations as items in Catalogs to make it easy to quickly navigate back to those locations. I have quite a lot of these per each work environment.
In one example work environment, the item links are in a format similar to: \\file-dal.xyp.com\T-Drive\PROJECT FILES\TELCO
If I'm using basic Windows Explorer to navigate to the locations, I (1) open a VPN connection for the company, (2) navigate to the link, and (3) if prompted, enter my work credentials.
About every six months, I have to change my password for this work environment, which of course causes changes to a variety of federated access points (email, network drives, online services, etc.). This all works fine: I change passwords in email clients, use different passwords on company websites, enter the new password when prompted as navigating the network drives, etc. and authentication is no problem. I can work without issues for as long as I like after changing my password...
Until I launch XYplorer. As soon as I launch XYplorer the first time after changing my company password, I suddenly get locked out of my company account. I believe the company's rule is something like 5 login attempts with wrong credentials before being locked out.
So it appears that XYplorer by itself, or in conjunction with some underlying Windows process, is somehow caching my old credentials and probably trying repeatedly to login to the numerous location items I've got stored in that company's Catalog. Then I get locked out and I have to go work with the company's IT department to get the account unlocked - which is not good when dealing with this particular company.
After account unlock (and sometimes having to unlock a handful of times), XYplorer will eventually cause a prompt to occur for new credentials, at which point I can finally authenticate and no longer encounter account lockouts. But then the next time my password expires, I have to go through this all over again. I've had this occur every password change over the last couple years, ever since I've been using XYplorer with this company.
What can I do to prevent XYplorer from firing off multiple connection attempts with the wrong credentials in the future? I'd like to (a) prevent XYplorer from firing off any connection attempts without my explicit input; and (b) be able to change the credentials prior to XYplorer causing this problem.
I use XYplorer in a variety of work contexts. In particular, I store network-drive-based locations as items in Catalogs to make it easy to quickly navigate back to those locations. I have quite a lot of these per each work environment.
In one example work environment, the item links are in a format similar to: \\file-dal.xyp.com\T-Drive\PROJECT FILES\TELCO
If I'm using basic Windows Explorer to navigate to the locations, I (1) open a VPN connection for the company, (2) navigate to the link, and (3) if prompted, enter my work credentials.
About every six months, I have to change my password for this work environment, which of course causes changes to a variety of federated access points (email, network drives, online services, etc.). This all works fine: I change passwords in email clients, use different passwords on company websites, enter the new password when prompted as navigating the network drives, etc. and authentication is no problem. I can work without issues for as long as I like after changing my password...
Until I launch XYplorer. As soon as I launch XYplorer the first time after changing my company password, I suddenly get locked out of my company account. I believe the company's rule is something like 5 login attempts with wrong credentials before being locked out.
So it appears that XYplorer by itself, or in conjunction with some underlying Windows process, is somehow caching my old credentials and probably trying repeatedly to login to the numerous location items I've got stored in that company's Catalog. Then I get locked out and I have to go work with the company's IT department to get the account unlocked - which is not good when dealing with this particular company.
After account unlock (and sometimes having to unlock a handful of times), XYplorer will eventually cause a prompt to occur for new credentials, at which point I can finally authenticate and no longer encounter account lockouts. But then the next time my password expires, I have to go through this all over again. I've had this occur every password change over the last couple years, ever since I've been using XYplorer with this company.
What can I do to prevent XYplorer from firing off multiple connection attempts with the wrong credentials in the future? I'd like to (a) prevent XYplorer from firing off any connection attempts without my explicit input; and (b) be able to change the credentials prior to XYplorer causing this problem.