We just had a customer with an EM-C800 (and a 579R) who had 4 laptops all turn on the default for password age in "Local Security Policy", all on the same day; all 4 stopped scanning 42 days after that, which is exactly the default number of days.
The annoying part, is you'd expect an authentication error, but instead, we were met with a "Check Connection" error, and the occasional DNS error. Immediately I had no issues scanning to my own laptop - hardwired, or wireless - and then tried setting up scanning from the 579 to one of those laptops, and received the same error, only it failed a little faster than the 800. After numerous attempts to see if scanning was getting blocked, Windows Updates, any security policy, all of the things you could think of, we probably tried. Even tried dropping a file from my laptop to theirs and that worked, so SMB couldn't have been getting blocked. We set up one of them as an FTP server and that worked.
The tech assisting me at some point was trying to map the drive to another laptop, and it finally gave him a password expired problem for the account we were using - it was a local account that we create for scanning with a pretty long password. Once he changed it and updated it on the machine, it worked fine. We then went into the other 3 laptops and set the password expire day to "0" so it doesn't expire.
It's very strange that it didn't give us an authentication error. Perhaps the machine wasn't understanding the error that laptops were sending back when it tried.
You would think it goes Search for PC(IP or hostname), then it checks on the rest of the path, and then it asks for permission, and at THAT point it should have given us an authentication error because it technically wasn't correct - but BOTH machines didn't know what to do with that error.
Ended up finding a resolution to our issue, but the machine was leading us in the entire wrong direction.
The annoying part, is you'd expect an authentication error, but instead, we were met with a "Check Connection" error, and the occasional DNS error. Immediately I had no issues scanning to my own laptop - hardwired, or wireless - and then tried setting up scanning from the 579 to one of those laptops, and received the same error, only it failed a little faster than the 800. After numerous attempts to see if scanning was getting blocked, Windows Updates, any security policy, all of the things you could think of, we probably tried. Even tried dropping a file from my laptop to theirs and that worked, so SMB couldn't have been getting blocked. We set up one of them as an FTP server and that worked.
The tech assisting me at some point was trying to map the drive to another laptop, and it finally gave him a password expired problem for the account we were using - it was a local account that we create for scanning with a pretty long password. Once he changed it and updated it on the machine, it worked fine. We then went into the other 3 laptops and set the password expire day to "0" so it doesn't expire.
It's very strange that it didn't give us an authentication error. Perhaps the machine wasn't understanding the error that laptops were sending back when it tried.
You would think it goes Search for PC(IP or hostname), then it checks on the rest of the path, and then it asks for permission, and at THAT point it should have given us an authentication error because it technically wasn't correct - but BOTH machines didn't know what to do with that error.
Ended up finding a resolution to our issue, but the machine was leading us in the entire wrong direction.