eStudio Scan to Domain Issues

[Guest]

My company sells and installs Toshiba eStudio copiers and I set up the network printing and scanning. The larger copiers have a scan location in the copier that is easily accessed as a "network place". The smaller copiers have to scan to a shared folder on a network computer. I have never had any problem setting up this type of scanning in a workgroup environment but when dealing with a domain, the results have been very hit and miss. I have had some success scanning to a shared folder on a domain server using the destination \\ip-address\sharename and the administrator name and password.
I am currently trying to set up an eStudio 182 to scan to a shared folder on a Small Business Server 2000 domain server. Following Toshiba support's instructions, I had the administrator set up an account, username "Toshiba", password "eStudio182" and create a folder in the server's Public share. When I try to scan I just get the message "TO FILE ERROR".
Part of my problem is that I am not the administrator for these domains and so it is difficult for me to play around with the security settings. I need to make some specific requests of the administrator.
The copier has the latest firmware and Toshiba support says it should "just work".
Any suggestions?

[Mr Spock]

Have the IT guys check and make sure the Toshiba account has full rights to the folder and also if it is a domain controller there are smb signing issues you may run into.

[Paper_path]

Check the scan logs in the web interface for it. It should have more information on the error you are getting such as "failed authentication." When working in a domain structure, make sure the DNS is set, and WINS is NOT (unless they have some legacy machines the copier needs to connect to) also turn off DDNS. Occassionally, depending on how their server is configured (it may also be a windows 2000 thing - I've run accross it before) you may need to put the domain prefix before the user name, so the authentication info looks like "domain/username" (I forget if its a forward slash or a back slash) - the server might have been thinking that the MFP was trying to log on using a local account and not a domain account.

Also, as Mr Spock suggested, have the IT guy check the permissions. Make sure that they have set the user with full share permissions, not just security permissions. Microsoft says that the security permissions over-ride the share permissions but practical experience has taught me otherwise.

[coveytech]

Thanks for your input. It was indeed a rights issue. A new share had been created as a destination for scans and the share rights were not set correctly. The network administrator suggested that it might be easier in the future to simply create a folder in the public area and use a longer path to access it. That way the folder would inherit the required rights from the public area folder and the administrator would not have to be involved.

[bnicolas]

I'm having a similar issue in windows 7 workgroup environment, error I'm getting is "Logon to file server failed. Check username and password" for topaccess scan log, any ideas? I know the share is available because I can access it from other pcs on network with the same l/p I entered into setup=>save as file

what user account will the mfp be entering the shared network folder with?

[bnicolas]

accessing shared location on copiet

I also can't access the shared location on the copier through \\name-of-copier-on-network

ie. \\mfp-05007509\FILE_SHARE

although it is available via estudio file downloader, I want to be able scan straight to the network folder though

[softballfreak28]

not finding the local scan

one thing we have seen is that the estudio"s have to be unplugged and rebooted then the local scan appears and you can access it the other has been the digital signing settings under the smb settings you want it set to digital signing isn't done for the server and the client also if the firmware is not on the newest version

[rthonpm]

If possible, I always ask the server admin to create a profile for the machine with admin rights. This way, even if new shares are created down the line, the rights assigned to the copier's profile don't need to be tweaked.