The customer can scan to everyone's desktop scan folder except one individual. This has worked in the past for a year now and something changed, but the customer is not aware of any change that would cause them to loose there connection. Any ideas on this?? Thank you in advance. Jerry

Host name change, IP address changed, the Share permissions got changed, the user login changed. Lotsa reasons could have happened that the end user is not aware of but their IT department might be and I have found that the IT people don't realize all that needs changed if they switch a PC out. They will say they set it up exactly the same as the one that got swapped out, but the Host name changed slightly or it's on DHCP and is now getting a different IP address, or the password changed slightly. It could be that the PC is now in an entirely different Workgroup. Keep asking questions, I just had one like that today with Scanning to Email. Worked one day and quit the next. Turned out that the Login User account I had stored in the copier for SMTP authentication was no longer a valid user account. The end user had no clue. Inform you end users that if changes get made on the network, that changes to the copier may need made also.

"Error type Setting" is what that worthless error print out says. Check the panel when the error occurs and look for a four digit number (1102, 2101...). That will narrow it down, the errors are in the book and all over here on D-net

Is this with SFU or SMB?

Is it possible Windows Firewall (or another software firewall) is blocking it?

It's possible they had Windows firewall off on this workstation and that there are exceptions (either for SFU (37100) or SMB (there's more than one SMB port) and Domain Group Policy has since turned Windows Firewall on.

Other security packages can block ports too.

Just have a customer today that can't scan SMB to one workstation in particular from a CS-5050. A KM-2530 using SFU in the same office can scan to the PC. I checked and the workstation is not showing in the Network Neighborhood, so the SMB sharing cannot work to it. May be something to look at. I did not try to resolve it, just told the customer that the scanning will work again when they can make the workstation appear in the workgroup.

When dealing with a friendly business I always ask if it's OK to add some users to a working PC and just pull those folders on the appropriate desktop.

SMB can really cross the line between copy guy and IT guy. I like to learn the solutions but it can be time consuming and dangerous.