Scanning Problem in KM-4050 Printer with SMB Protocol

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • aborad
    Technician
    • Aug 2011
    • 61

    #1

    [Error Code] Scanning Problem in KM-4050 Printer with SMB Protocol

    hi,

    I have KM-4050 Printer.. i am using SMB for Scanning.. its working fine with Windows XP. And its giving error "2101" in Windows 2008 Server.

    can anybody tell me what is to be done to work with Windows 2008.. i am using administrator user for configuration.

    any patches need to be run in win2008 Server?
  • taskalfa
    Technician

    50+ Posts
    • Jun 2011
    • 97

    #2
    Re: Scanning Problem in KM-4050 Printer with SMB Protocol

    I dont know if this will help but have you tried disable smb signing on 2008 server.
    When SMB signing is enabled on both the client and server, SMB sessions are authenticated between the machines on a packet by packet basis.
    To disable SMB signing on the Windows Server 2008 and 2008 R2 perform the following:

    Changes need to be applied in the Group Policy management console.

    Start --> Administrative Tools --> Group Policy Management

    Configure the Default Domain and Default Domain Controller Policies. The settings you are looking for are under:

    Computer Configuration --> Policies --> Windows Settings --> Security
    Settings --> LocalPolicies --> Security

    Comment

    • blackcat4866
      Master Of The Obvious

      Site Contributor
      10,000+ Posts
      • Jul 2007
      • 22927

      #3
      Re: Scanning Problem in KM-4050 Printer with SMB Protocol

      Good to know. Thanks for the education. =^..^=
      If you'd like a serious answer to your request:
      1) demonstrate that you've read the manual
      2) demonstrate that you made some attempt to fix it.
      3) if you're going to ask about jams include the jam code.
      4) if you're going to ask about an error code include the error code.
      5) You are the person onsite. Only you can make observations.

      blackcat: Master Of The Obvious =^..^=

      Comment

      • Kelvinator

        #4
        Re: Scanning Problem in KM-4050 Printer with SMB Protocol

        Another thing to try is swithching to port 445 on the web page

        Comment

        • RCR
          Technician
          • Dec 2009
          • 11

          #5
          Re: Scanning Problem in KM-4050 Printer with SMB Protocol

          Originally posted by aborad
          hi,

          I have KM-4050 Printer.. i am using SMB for Scanning.. its working fine with Windows XP. And its giving error "2101" in Windows 2008 Server.

          can anybody tell me what is to be done to work with Windows 2008.. i am using administrator user for configuration.

          any patches need to be run in win2008 Server?

          Tray the port 445 instead of the standard port 139

          Comment

          • blackcat4866
            Master Of The Obvious

            Site Contributor
            10,000+ Posts
            • Jul 2007
            • 22927

            #6
            Re: Scanning Problem in KM-4050 Printer with SMB Protocol

            Originally posted by Kelvinator
            Another thing to try is switching to port 445 on the web page
            I just used this today on our new server. =^..^=
            If you'd like a serious answer to your request:
            1) demonstrate that you've read the manual
            2) demonstrate that you made some attempt to fix it.
            3) if you're going to ask about jams include the jam code.
            4) if you're going to ask about an error code include the error code.
            5) You are the person onsite. Only you can make observations.

            blackcat: Master Of The Obvious =^..^=

            Comment

            • aborad
              Technician
              • Aug 2011
              • 61

              #7
              Re: Scanning Problem in KM-4050 Printer with SMB Protocol

              My problem got solved by changing Port 139 to 445.

              Thanks a lot Kelvinator and also who had replied to this post.

              Comment

              Working...