KM-1820 scanning

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • LNorris
    Senior Tech

    500+ Posts
    • Sep 2008
    • 645

    #1

    KM-1820 scanning

    ok, this is a new one for me.

    i have a 1820 on a domain network (instead of peer-to-peer). we tried setting up scan to local computer and local server (that runs the domain). the scans are being rejected (error 1102). we set up a user just for the scans, error. we entered domain/username and password on the 1820, error.

    we called in the company's IT tech and they cant figure this out either.

    setting up scan from an 1820 has to be the simplest to set up (normally).
    has anyone encountered this? if so, what am i missing?

    thanks
  • netjustin

    #2
    Norris,

    Not sure what the error 1102 is but a couple places to look are the NTFS folder permissions on the server and, if those are fine, revisit how you entered your domain credentials. Different systems expect different syntaxes (sp?), but at times I've been forced to abandon the username & password syntax and go straight for domain\username & password, or even more obscure the username@domain.local & password convention.

    That should give you something to try. It'd be interesting see whether the server is firing logon failure audits in the event viewer.

    Hope that helps.

    Comment

    • LNorris
      Senior Tech

      500+ Posts
      • Sep 2008
      • 645

      #3
      Thanks, i'll check into that and let you know

      Comment

      • jneezy2008
        Software/IT

        50+ Posts
        • Mar 2009
        • 72

        #4
        Typically, with scan to SMB, you want to set Full Control to Allow for All Users, under permissions.

        One way to test the folder permissions is to go to a workstation, click Start => Run. Type \\hostname (hostname is the name of the computer you're scanning to) then click OK. This will open a window showing all shares on the remote computer. Navigate to the destination folder. If you're prompted for a username and password, enter the username and password that the copier is configured with. After you get in to the folder, try to create a new text document(this tests writing privelages). If that all works then the permissions are set correctly are your problem may be the syntax on the copier.

        Also, you can test the copier by connecting your laptop to the NIC using a crossover cable.

        And make sure SMB is enabled on the copier.
        The snozberries taste like snozberries!!

        Comment

        • golanie

          #5
          take a look

          I think this might help:

          Comment

          Working...