Windows Fax and Scan bug: Does not accept a valid UNC path in the Route Scan dialog
Windows Fax and Scan does not accept UNC paths or network paths with mapped to a drive letter when folder is located on a NAS (Network Attached Server)
Replication steps:
- Open network a folder (e.g. \\DNS323\Volume_1\Documents\Scans\) in Windows Explorer.
- Folder contents is displayed in the Explorer window
- Select and copy full network path in the address bar
- Open Windows Fax and Scan application (%windir%\system32\WFS.exe)
- In the main menu select Tools->Scan Routing...
- Select checkbox "Use a network folder"
- Paste selected network folder path (e.g. \\DNS323\Volume_1\Documents\Scans\)
- Click "Save"
Error is displayed: "\\DNS323\Volume_1\Documents\Scans\ is not a valid server share"
Expected result: Valid UNC path is accepted.
Similarly, the same error is received when a part of the UNC path is mapped to a drive letter.
January 21st, 2011 7:18am
Hi,
Thanks for posting in Microsoft TechNet forums.
What about Scan reroute to a local direction?
Best Regards
Magon Liu
TechNet Subscriber Support
in forum. If you have any feedback on our support, please contact
tngfb@microsoft.com
Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2011 1:21pm
What happens if you only put in a short UNC path
\\SERVERNAME\SHARENAME?
What about dropping the trailing slash (all of your examples above show a trailing slash)
=============
Update
I have tested this and you ARE required to only reference the first level share
You cannot append additional folders or a trailing slash
David J. This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your
question. This can be beneficial to other community members reading the thread.
March 3rd, 2011 2:08am
As David J mentioned above, using \\ServerName\ShareName syntax stops "Windows Fax and Scan" from complaining about invalid sharenames, however, in my tests it does not seem to be able to route to the share anyway.
I verified this by
1) Checking the access logs of my non-Windows (QNAP) NAS
2) Running procmon and checking for any "network activity" (none). I also looked at every "CreateFile" operation but did not see any attempt that involved network. BTW, it seemed that scanned file is first created as bmp and then converted to jpg.
Free Windows Admin Tool Kit Click here and download it now
August 18th, 2011 4:39pm