• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 24221
  • Last Modified:

MFP's Suddenly Stopped Scanning to Network Share on Windows Server 2003

Most of our Multi Function Printers (about 8) have suddenly stopped scanning to our network share (on a Windows Server 2003 server).

I have troubleshot this for the past 5 days to no avail and EE is my last hope before having to implement something else instead of resolving the problem.

Sharp MX3501N states "selected server could not be found" (error 80-0000 in the logs which is no use anywhere).
Xerox MFP's say it's an authentication issue (error 016-782).
There are still some scanners that do work (ironically they are the newer scanners).

Things I've done:
Verified share permissions (they are completely correct, even testing with Everyone).
Pointed the scanner to a desktop with a shared folder (and it worked).
Verified Printer Settings are correct (gone up the tier with xerox, they recommended the group policy change mentioned below).
Checked Event Viewer for access logs on the server (there were none, but some from the printers that are still successfully scanning).
Ran Microsoft Network Monitor while attempting to scan (no connection attempt was logged).
Changed Group Policy for the server: "Send LM & NTLM - use NTLMv2 session security if negotiated" to "Send LM & NTLM Responses" then ran gpupdate.


I'm almost positive this is something with the server. It seems this happened after I rebooted the server. There were no Windows Updates installed (to my knowledge) which is very puzzling to me and the only thing I changed was the 'File and Printer Sharing for Microsoft Networks' properties on the network card to tell it to 'Maximize data throughput for network applications' instead of 'Minimize memory used' because it is a Application/File Server and has hanging issues due to the load it takes.

Please Help, I'm up to trying anything at this point.
0
sgcity
Asked:
sgcity
1 Solution
 
jorlando66Commented:
check that the servers are registering properly in dns.
from the remote site where the malfunctioning MFP is located try pinging the server by name.  Does it resolve?  from a desktop tru to get to the server share by UNC.  Does this work?
0
 
sgcitySystems EngineerAuthor Commented:
Checked DNS and it looks good. I did ping by name and it resolves properly with no drops. I also told the printer to scan to it's share using the IP address just in case and there was the same problem but the same error popped up. I used the built in ping tool on the printer and was 4 of 4 success on pinging the server by IP.
0
 
sgcitySystems EngineerAuthor Commented:
I did install the security update MS10-054 <http://support.microsoft.com/kb/982214> a week before and this reboot was the first since applying the update. Could it be SMB?
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
sgcitySystems EngineerAuthor Commented:
Sorry, repost of the link above since I can't find a way to edit my own comments... http://support.microsoft.com/kb/982214
0
 
jorlando66Commented:
Most likely the printers (most do) use smb to connect.on port 445.  check firewall settings?
0
 
sgcitySystems EngineerAuthor Commented:
I just verified the firewall is disabled on the server. Current SMB port is 139, though I'll try setting the scanner to use 445.
0
 
sgcitySystems EngineerAuthor Commented:
Did a proper hotfix uninstall of MS10-054 to no resolution.
0
 
sgcitySystems EngineerAuthor Commented:
Could it be SMB Signing? http://support.microsoft.com/kb/887429 ?? The server being scanned to is a domain controller. I'm curious if this was disabled and was recently enabled...
0
 
sgcitySystems EngineerAuthor Commented:
Apparently no-one has a solution to this. I simply redirected all MFP's to scan to ftp (and with junctions it puts them in the right places) and that was the solution I had to accept.
0
 
FSMC_ISDCommented:
If anyone else is having this issue, check the compression settings, and whether or not you are sending the files as TIFF or PDF. I found that the scanner is NOT COMPRESSING TIFF FILES even though compression is enabled. I tested this over my exchange server using both pdf and tiff- the tiff files were rejected every time (47MB), until i increased the message attachment size to something ungodly. However, if i used pdf, mmr G4, high compression the document was reduced to 9MB.
0
 
acronymsCommented:
I was having the same issue and it was due to the licensing on the server nearing the maximum number of per server licenses.
0
 
BBDITCommented:
I just had a similar issue: only two users on both our printers could not scan to a network share.

I was banging my head against the keyboard for a few hours.

The problem turned out to be a quota the shared folder  -for the respective users- was reached. Having the user delete unneeded files was the solution.

I had completely forgotten about the quota, and was reminded by a colleague, all the error messages I was getting suddenly made sense.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now