I'm not too familiar with domains. compared to a workgroup structure, Is there a difference in information that needs to be entered (Besides the domain name) to get this to work? Or possibly some differences in sharing the folder to be scanned to? Could I get an example of what to enter as the hostname/path/username and password if there is a difference? For some reason I just could not get it to work at a customer's office and I think I might be missing some information. Thank you for any input.
-
Last edited by JVergin; 03-14-2011, 02:47 PM. -
The most important piece of information to find is what the domain controller is (Windows 2003, 2008 server, Linux, etc). From there, several variables can come into play. If it's a Windows 2008 server, the SMB protocol has changed so their may be newer firmware needed for the machine. Check your bulletins &c for any issues with the current firmware levels.
Overall, in a domain environment, you're going to need a valid user ID and password to access anything. From there, the rights assigned to that user name are going to be paramount. Even if the name gets you authenticated to the domain, if the user doesn't have rights to access shares, you won't be able to scan to them.
Try having the customer's IT create a new user just for the machine with full rights to any and all shares users will be scanning to, as well as a password that will not expire (otherwise once the password goes scanning stops until it's re-set). Sometimes, the only way to get everything right is to make the account a member of the domain admins group (that way any odd group or location not configured correctly on the network will still be able to access it, so long as the domain information is correct).
Here's hoping that helps.
Comment