Just a quick update for anybody else who has this issue.
We submitted network packet captures to the Xerox Engineering team, one set from a Phaser 3300 that sneds SMB scans fine and the second set from the 3325 that does not.
Here's what they found (email from tech support):
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
[We] did a scan from our WC3325 to a 2003 x32 server running as a Domain Controller. It failed the initial connection using NTLMv2, but then switched to NTLMv1 (as it should) and connected fine. Looking at the trace that was submitted, the customer’s WC3325 does the same, however it fails on both NTLM and NTLMv2.
. . . . . . . . .
Since the server is set to NTLMv2 only and the printer is failing the login attempts, there appears to be an issue with the implementation of NTLMv2 on the WC3325. I have already submitted this matter to the engineering to see if they can develop a patch for the printer to address this matter. The SPAR# for this matter in Engineering is Xerox00187319. You should be receiving an email from the SPAR Administrator shortly.
. . . . . . . . . .
I wanted to inform you that SPAR/XSEED for Xerox00187319 for your WC3325 has been submitted to 3rd level engineering per your request for NTLMv2 Authentication Failure.
Going forward, our Escalation Administrator will be your point of contact for this escalation. If the escalation administrator needs my assistance, they will work with my manager to request my help.
We will provide an update for the escalation (above) every (2) weeks via e-mail.
- - - - - - - - - - - - - eom - - - - - - - - - - - - -
FYI in our domain environment we set the authentication method to NTLMv2 ONLY via network-wide group policy.
Seems there will be a firmware fix coming from engineering soon.
So if you are having this issue of SMB failing to send because of authentication issues, Please Stand By!