02-09-2011 01:18 PM
We own a Xerox Phaser 6180MFP-N. We're having trouble setting up scanning to SMB share on Windows Server 2008 R2 Std. We are repeatedly recieving the error message: 016-782
The configuration is as follows:
Name: Information Technology
Server Type: SMB
Server Address: 192.168.X.X
Port Number: 139
Login Name: DOMAIN\USER
Login Password: ********
Share Name: Share
Server Path: "Folder\Sub Folder\Sub Folder"
I know that communication is hitting the server because I'm recieving the following message on the server:
An account failed to log on.
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: USER
Account Domain: DOMAIN
Failure Reason: Unknown user name or bad password.
Sub Status: 0xc000006a
Caller Process ID: 0x0
Caller Process Name: -
Workstation Name: 192.168.X.X
Source Network Address: 192.168.X.X
Source Port: 1298
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
I know that SMB is configured properly because I have a Ricoh 2851 with SMB scanning configured. The passwords an usernames are identical it I'm able to successfully scan to the shares on the server.... looking for some help.
02-10-2011 06:26 AM
I will assume you you have all "basic settings" covered, such as:
Apart from this some other settings I would try are: Those are at the DC level
Hope this helps
03-10-2011 06:12 PM
05-27-2011 12:13 PM
I did the following on a Windows 7 workstation when receiving the same error message...
Deleted and recreated Individual Directory Entry - No joy!
Checked properties of target directory called Scans in My Documents - security and Sharing info all looked OK.
Fixed by going to Start > right click Computer > Select Manage > System Tools > Shared Folders > Shares > My share was not there, so created a new share > Right click Shares > New Shares > Run through wizard, selecting my shared folder 'Scans' > once complete right click new share and select properties > Click on Share Permissions and add the required user and check the Allow Full Control checkbox > OK.
I ran the scan on printer and it worked.
02-21-2012 08:28 PM
I have a 2008 R2 cluster, and I am receiving the same 016-782 error message, but I have checked the reg and the verification settings are already set to 0. I think it is SMB related, we had no issues on the 2003 server. Two things seem to change on 2008, one is the SMB protocol which now uses version 2 and the 2008 cluster doesn't allow you to access the share with an IP only host name / DNS. I don't think it’s a DNS issue because all the DNS server information is correct. The error happens pretty fast and you can see on the Xerox LCD the it states logon error and the error code. Has anyone else has issues on 208 R2, and what have you done. I found another source that talked about adding a entry under Lanmanserver\Parameters for SMB and forcing it to use the older version, but that was for XP workstations and not the Xerox scanner.
06-21-2012 09:16 AM
Hey WestCoast, did you ever find a solution to this? We recently switched fom 2003 to 2008 cluster storage environment and are having the same problems on our 5 Xerox's that we use for scanning. Fortunately all of our Lexmark scanners are still working fine.
04-02-2013 07:46 PM - edited 04-02-2013 07:48 PM
Switched from Windows 2008 R2 Server to Windows 2008 R2 Cluster with 2 nodes. (Adding this is for 018-543 error as well)
For Scanning to the Windows 2008 R2 Cluster, I had a heck of a time getting all my Xerox items to scan like they used to. Success was made by a combination of items from a few obscure posts and non-related posts, but they worked for me:
1. Xerox WorkCentre 7775
These have the hidden Xerox Diagnostics link. so it would be http://IP_ADRESS/diagnostics/resolveHostname.php (case sensitive). Entery username, password. Uncheck Setting "Enabled"
In Properties, Services, Workflow Scanning, File Repository Setup: enter Default Repostory Server as
Servername.Domain.com , Port I kept as 139 and it worked, though 445 should work, too.
Scanning once again was able to work
2. For Older Scanner WorkCentre 7675, I had to use administrative share.
These did not have hidden Diagnostic link.
In Properties, Services, Workflow Scanning, File Repository Setup: enter Default Repository Server as
Servername.Domain.com, Port 445
Share: Admin Share i.e. f$ g$
Document Path: i.e. users\ or share\Scanning
Then if you are using the templates, you would continue the path JSmith\Scans to make (servername.domain.com:445\g$\users\username\Scans
3. For even older Scanner Xerox 7328, 7346, using Chrome or Firefox as IE9 did not go in for me for these older Xerox machines. But its the same thing. Just had to use Port 445, fully qualified name i.e Servername.Domain.com and admin share. So follow #2 above
Keys to remember on 2,3 the Share can only be one item like g$, not g$\users
If you are worried about administrative shares, there are programs to enable open for use and close for use like tenable.com, but I don't know much about that issue.
But behind good security, you may want to read that disabling Admin Shares anyways can hinder items here:
This is simply what worked for us for a cluster and may help you until Xerox does a patch...or doesn't. Many thanks to the various posts around the net that I had to piece together to make things work.
Forgot to mention that this was for error 018-543