Support Community
Showing results for 
Search instead for 
Do you mean 
Reply
New Member
Posts: 1
Registered: ‎03-21-2018

Intermittent failure to scan to PC

Hi folks, 

 

I'm in a bit of a pickle here. In the company i work for, we have a few FujiXerox MFP of different versions in each department. One particular issue that kept creeping up is scanning to PC failure. 

 

The error code: 027-516: Server Connection error in SMB

 

 

Action taken: 

1. I've created a folder called "scan" on the root of the drive ( C:\scan)

2. I created an account called "xerox" with full access rights to that PC

3. I force SMB using powershell.

   (Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 1 –Force)

 

Behavior post action taken:

1. The users were able to scan to PC throughout the first week after the steps taken above. Then the week after that it doesn't work again. The worse part, is that it hasn't come back since. 

 

A little backstory, the particular floor with that issue is congested and due to HW limitation (switches) , there are times where we had to reboot the switch to get some of the traffic moving. 

I'm have an inkling feeling that the root of the issue could be network congestion. I'm not sure. my network skill level is novice i would say.

 

Therefore, i acquire your help to assist me in finding a solution. The users are complaining and my boss made me make this my first priority. 

 

Cheers

Highlighted
Analyst Nation Moderator
Posts: 5,905
Registered: ‎11-25-2013

Re: Intermittent failure to scan to PC

When multiple clients all stop accessing a single server, it really isn't likely that the clients (printers) are the problem.

 

Typically 027-516 means an unsupported SMB type, typically caused by using port 445 on a device that uses Netbios over TCP/IP (uses port 139).

 

But since the server appears to be the issue, it would imply the smb change you made to re-enable SMBv1 (required since your devices likely can't do SMBv2-3) got over-ridden by another Windows patch (This is going to happen again and again so it probably isn't worth the hassle)

 

Short version and the best workaround is to simply enable FTP server side using the same exact folder, then  switch the printers to use the FTP path/user.

 

This way Microsoft won't change things on you, and the shares that exist can still be accessed by any client PC's (So if you have the folders mapped on client PC's, there won't be a workflow interruptions there)

Please be sure to select "Accept Solution" and or select the thumbs up icon to enter Kudos for posts that resolve your issues. Your feedback counts!

Joe.