SMB connection to Windows 2008R2 File Server Problem RRS feed

  • Question

  • Hello, I recently migrated a file server from Windows 2003 to Windows 2008R2.  Since the migration, I can no longer use our Canon multi-function printer to scan documents to a network share on the new file server.  The share has Everyone, System and Authenticated Users set to Full control and the NTFS Security is setup for Everyone to modify.  The connection from the Canon uses SMB using a domain account called jdoe.  

    I wondering if the problem is related the the LAN Manger authentication level settings.  On the new file server and domain controllers it's set to Network security: LAN Manager authentication level is set to Send NTLMv2 response only\refuse LM & NTLM.  I have setup a network capture and hope somebody can help me out with determinging the problem. 

    Here is the detals of the Error

    Wednesday, September 12, 2012 2:28 PM

All replies

  • I am very interested in any replies as I am presently working with somone that is having a similar problem with a Xerox scanner.  In their case, however, the file server (clustered 2008R2) is responsing with the cluster node name as the server instead of the file server name in the SMB negotiate protocol response. This would wirk with 2003R2 but not 2008R2.  The scanner is basically trying to save the scan to the wrong location.

    Robert Thompson

    Wednesday, September 12, 2012 9:14 PM
  • It does seem possible that the NTLMv2 authentication level might be affecting things.  So I would give it a try.  It's difficult to troubleshoot from the image, but I beleive there is a flag in the negotiate response that might give you a clue.  In either case, I think your question would be better served by our networking group, rather than the group that makes the tool.  While we have some general protocol knowledge, we don't have the depth that the experts for each component would have.

    If changing that setting doesn't work we can move this thread over to the right place.



    Thursday, September 13, 2012 1:45 PM
  • Robert, I think your problem is slightly different, though you might still run into the same root problem described originally in this thread.  A trace of your problem would also help determine what is happening.  But again, like above, posting this question in the approrpiate network related technet forum would be a better fit for this type of question.



    Thursday, September 13, 2012 1:48 PM
  • Sorry, for the poor image quality.  I'm told this may be a problem with the fiery on the Canon.  I have a Canon rep coming out tomorrow, so I will update this post tomorrow.

    Thursday, September 13, 2012 8:52 PM
  • Was this resolved ?

    If yes, I would request you to share the solution.



    Thursday, June 6, 2013 4:24 PM
  • I'm having the same issue with our 5 Canon Scanners. Any suggestions?

    Faisal Nahian

    Monday, July 21, 2014 8:17 PM