S
slh2000
See below thread (bottom to top). Has anyone else had this problem? I appreciate any advise. Thank you.
Sent: Wednesday, May 17, 2017 12:49 PM
Last one : ( We are running Server 2012 R2:
https://social.technet.microsoft.co...to-become-unavailable?forum=w7itpronetworking
This ended up being the resolution in our case as well. Canon iR3225 - sending the scans to a DFS folder on a 2012 R2 Server. Had to update the DCs (2008 R2) with the registry key before this would work.
Sent: Wednesday, May 17, 2017 12:42 PM
Thanks.
I promise to try and not keep emailing you ….but that article I sent you does seem to be a similar problem:
https://community.spiceworks.com/topic/1669007-kb3161949-breaks-network-scanning
Yesterday was a slow day. Midday however started with a ticket indicating scans were't working at one of our 40 locations (90% of which are connected via MPLS). Our scans go into user shares on our file server in the "%username%\My Documents\Scans" folder.
https://social.technet.microsoft.co...to-become-unavailable?forum=w7itpronetworking
So if you are having problems with "modern" Windows hosted fileshares and Windows clients after applying this update, make sure that clients can access the server on TCP / UDP 445.
If you are having problems with non Windows / legacy clients (like Network scanners) accessing file shares, you need to either add the registry modification decsribed earlier to the hosting server:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NetBT\Parameters] "AllowNBToInternet"=dword:00000001
Or you can try to map the shared folder to the device using FQDN ( \\server.domain.com\share ), assuming the device is DNS capable (FQDN seemed to work on Windows client, but have not actually tested this on anything else)
Sent: Wednesday, May 17, 2017 12:39 PM
We are still looking at this issue. I have another tech taking another look at it to get a fresh pair of eyes to see if we can determine why the scan to folder isn't working. Thank you
Sent: Wednesday, May 17, 2017 12:37 PM
See below thread (bottom to top). Do you have any suggestions?
Last night all our servers got all Microsoft updates & SMBV1 was disabled (due to the Ransomware threat), Today no scans are coming through : (
Sent: Wednesday, May 17, 2017 12:24 PM
https://community.spiceworks.com/topic/1669007-kb3161949-breaks-network-scanning
Sent: Wednesday, May 17, 2017 12:18 PM
http://ug.oipsrv.net/USRMA-0320-zz-...2910536.html#4e77387369e2477d024ee8be96d5b010
Sent: Wednesday, May 17, 2017 11:59 AM
Still not working. I did 1 scan, then powered scanner off/on and did a 2nd scan. Neither worked.
I don’t know what this is because I never rec’d it when scanning before, but this printed out on the copier/scanner:
Sent: Wednesday, May 17, 2017 11:45 AM
Can you try one more time for me please.
Sent: Wednesday, May 17, 2017 11:23 AM
Something is not communicating?
Not going….Copier keeps displaying: SAN 01 SENDING
Sent: Wednesday, May 17, 2017 11:03 AM
Do you have the IP of the scanner. I want to go in and take a look at the settings. Thank you
Sent: Wednesday, May 17, 2017 10:56 AM
I logged into the scanner for the Basement B/W Copier and saw this:
RESULT: NG (MUST mean No Go?). I’m going to research the Error Code # 801.
Sent: Wednesday, May 17, 2017 10:52 AM
Shutdown/Powered up copier/scanner & still not scanning.
Sent: Wednesday, May 17, 2017 10:40 AM
Have you tried rebooting the scanner? I would try that first. Everything from the server and SAN side seems to be working correctly.
Sent: Wednesday, May 17, 2017 10:38 AM
When a user does a scan on the copier it’s not showing up (communicating) on our network. Last time this happened we had to reboot the servers & NetApp.
Sent: Wednesday, May 17, 2017 10:12 AM
Just an FYI –
This morning SCANS at copiers are NOT going into the respective scan folders (MY scan folder: i:\xxx\*.*).
We will try to figure this out ourselves, but just wanted to let you know.
Continue reading...
Sent: Wednesday, May 17, 2017 12:49 PM
Last one : ( We are running Server 2012 R2:
https://social.technet.microsoft.co...to-become-unavailable?forum=w7itpronetworking
This ended up being the resolution in our case as well. Canon iR3225 - sending the scans to a DFS folder on a 2012 R2 Server. Had to update the DCs (2008 R2) with the registry key before this would work.
Sent: Wednesday, May 17, 2017 12:42 PM
Thanks.
I promise to try and not keep emailing you ….but that article I sent you does seem to be a similar problem:
https://community.spiceworks.com/topic/1669007-kb3161949-breaks-network-scanning
Yesterday was a slow day. Midday however started with a ticket indicating scans were't working at one of our 40 locations (90% of which are connected via MPLS). Our scans go into user shares on our file server in the "%username%\My Documents\Scans" folder.
https://social.technet.microsoft.co...to-become-unavailable?forum=w7itpronetworking
So if you are having problems with "modern" Windows hosted fileshares and Windows clients after applying this update, make sure that clients can access the server on TCP / UDP 445.
If you are having problems with non Windows / legacy clients (like Network scanners) accessing file shares, you need to either add the registry modification decsribed earlier to the hosting server:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\NetBT\Parameters] "AllowNBToInternet"=dword:00000001
Or you can try to map the shared folder to the device using FQDN ( \\server.domain.com\share ), assuming the device is DNS capable (FQDN seemed to work on Windows client, but have not actually tested this on anything else)
Sent: Wednesday, May 17, 2017 12:39 PM
We are still looking at this issue. I have another tech taking another look at it to get a fresh pair of eyes to see if we can determine why the scan to folder isn't working. Thank you
Sent: Wednesday, May 17, 2017 12:37 PM
See below thread (bottom to top). Do you have any suggestions?
Last night all our servers got all Microsoft updates & SMBV1 was disabled (due to the Ransomware threat), Today no scans are coming through : (
Sent: Wednesday, May 17, 2017 12:24 PM
https://community.spiceworks.com/topic/1669007-kb3161949-breaks-network-scanning
Sent: Wednesday, May 17, 2017 12:18 PM
http://ug.oipsrv.net/USRMA-0320-zz-...2910536.html#4e77387369e2477d024ee8be96d5b010
Sent: Wednesday, May 17, 2017 11:59 AM
Still not working. I did 1 scan, then powered scanner off/on and did a 2nd scan. Neither worked.
I don’t know what this is because I never rec’d it when scanning before, but this printed out on the copier/scanner:
Sent: Wednesday, May 17, 2017 11:45 AM
Can you try one more time for me please.
Sent: Wednesday, May 17, 2017 11:23 AM
Something is not communicating?
Not going….Copier keeps displaying: SAN 01 SENDING
Sent: Wednesday, May 17, 2017 11:03 AM
Do you have the IP of the scanner. I want to go in and take a look at the settings. Thank you
Sent: Wednesday, May 17, 2017 10:56 AM
I logged into the scanner for the Basement B/W Copier and saw this:
RESULT: NG (MUST mean No Go?). I’m going to research the Error Code # 801.
Sent: Wednesday, May 17, 2017 10:52 AM
Shutdown/Powered up copier/scanner & still not scanning.
Sent: Wednesday, May 17, 2017 10:40 AM
Have you tried rebooting the scanner? I would try that first. Everything from the server and SAN side seems to be working correctly.
Sent: Wednesday, May 17, 2017 10:38 AM
When a user does a scan on the copier it’s not showing up (communicating) on our network. Last time this happened we had to reboot the servers & NetApp.
Sent: Wednesday, May 17, 2017 10:12 AM
Just an FYI –
This morning SCANS at copiers are NOT going into the respective scan folders (MY scan folder: i:\xxx\*.*).
We will try to figure this out ourselves, but just wanted to let you know.
Continue reading...