I am not aware of any reported problem with 7225 and DFS scanning. But depending on the erros, this can cover mode device models. Can you please describe a bit more your situation.
Please, also test normal SMB scanning. Set a shared folder and attempt to scan to that share.
Avoid spaces on file repository and path names.
Let us know of the error messages you are having. As a reminder, if a jobs fails to scan, it will be displayed on the completed job queue, as completed with an error. Please select the job details to provide further information.
Which models have problems scanning to DFS path 2nd / 3rd levels?
Do you know of any problems with scanning to a DFS path using a 7225?
Do you know of a link to an Application Note or similar document discussing scanning to a DFS path in more detail?
the UNC below is correct. Make sure that all DFS level and the target will support authentication credentials you are inserting.
i.e If you use the domain credentials, this will allow you to access anything on your windows domain, but if the final target (no matter on what level of the DFS) uses its own credential set (some NAS products without AD integration) you will find problems.
Make sure you can access the folder using smb and you can create and delete files within it. as well as make sure the target is live on the DFS.
also make sure your devices are on the latest firmware. I am aware of scanning problems to 2/3rd level DFS targets with some models.
What kind of settings should I use if we are using DFS (Microsoft's distributed file system)?
hotname = <DOMAIN.NAME> ?
port = ?
share = <dfsroot> ?
Document Path = <path>.
Standard share (ie: hostname,port, share, path .....) is working fine .