For a few days, I noticed that I can no longer connect to my NAS. It is odd because, before that, I could easily click on a share and see what is in that share and read and write the files there. My backup software was able to transfer data to the NAS. However, now I have problems. The problem is mainly that the NAS security is blocking the IP address of my laptop. When in 30 minutes 5 times the wrong password is entered, the IP address will be blocked for 24 hours.
When I use an app and delete my IP address, I can log into the administration console of the NAS and do whatever I want. However, when I click on the share using Directory Opus in seconds, the IP address of my laptop is added to the block list.
What I tried is as follows:
Turn off the firewall
Change the settings in the NAS to block attempts with incorrect passwords
Turn off my VPN
Check if my laptop is discoverable in the private network
Update to the latest version of Directory Opus
Al these things do not seem to have any effect.
It is no problem to access the NAS from another laptop, and the IP address of that laptop is not added to the block list. On that laptop, there is no Directory Opus installed.
I did not change the password in the last few weeks. I use Windows 10 Home Version 21H2 build 19044.1766.
Does anyone of you know what I could do to fix this? Thanks in advance for the help!
That’s a question for your NAS’s support team. Opus isn’t adding your laptop to the NAS block list; the NAS is doing that itself for some reason, which only they can explain.
Thanks for the reply, and I understand. The only thing is that the security settings are triggered explicitly by Directory Opus and apparently nothing else. So, I wondered if I somehow can check the credentials Directory Opus is using to access the shares on the NAS.
Opus doesn’t deal with credentials for network drives; it’s something Windows does.
First connection attempt usually uses the account you’re logged in with (or an admin account if using OTS elevation, but that’s rare). If that fails, and is recognised as a credentials failure, then Opus will ask Windows to prompt for alternative credentials and connect to the drive. Opus isn’t involved in the connection or password prompt, and never sees the credentials; it only requests that they happen.
Some NAS return non-standard errors for the first failure, which can mean the credentials prompt isn’t triggered. There’s a setting you can change to solve that in most cases (and we can also change the code to look for the unexpected error). But that would only help if Explorer on the same machine is able to connect to the drive. If Explorer can’t either then the problem is somewhere else.