SMB Scan issue on Gestetner DSc332

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Toner Boy
    Trusted Tech

    Site Contributor
    250+ Posts
    • Aug 2007
    • 357

    #1

    SMB Scan issue on Gestetner DSc332

    Hello,

    We received a Gestetner DSc332 a few days ago and I am trying to set up Scan via SMB to our Windows 2003 Server. This server is setup on a domain network. File sharing is enabled and firewall is disabled; permissions are set to everyone and administrator (Anonymous Logon permitted as well just for troubleshooting purposes).

    Problem: Browsing to server and scanning to server fails (Indicates entered username or password is invalid). Another computer within the same network, but not the same domain succeeds all scan attempts.

    Also, Network scans with our Sharp MX-2700N works perfectly to same shared folder. I retyped the authentication info for the server access multiple times thinking I was mistyping something; but I am confident the login credentials are accurate.

    I checked the settings within the Gestetner Webpage and I am not sure what I am missing. I am trying to set this one machine up for scanning purposes in our office because of the "browse to folder" capabilities from the control pad. The purpose for this is to scan all documents and notes regarding our clients to their specific folder without having to go to a computer after the scan job.

    Has anyone had a similar experience (issue) with setting this machine up for SMB scan in a similar networking environment?

    Thanks in advance
  • fausto1981
    IT Technician

    100+ Posts
    • Dec 2007
    • 146

    #2
    Two questions for you:
    Is this a Domain server???? if yes, Miscrosoft does not support smb (cifs) scan to folder for win 2003 domain server (primary or backup)

    or does the machine have the latest firmware???? if not then that will fix your issue.

    if you don't want to do the firmware there are other work arounds that you can do but I dought that they will let you digital signing on their Server....

    Hope this helps

    Comment

    • Toner Boy
      Trusted Tech

      Site Contributor
      250+ Posts
      • Aug 2007
      • 357

      #3
      Wndows 2003 Domain Server

      Thank you for your response. Yes, this server is configured as a Domain Server. Would the 'digitally signing' idea work? If so, how would I configure this work-around on the server? FYI: Since this is our own server, I have full control to try this idea.

      I believe I want to try this work-around without updating the copier firmware.

      Please let me know how to go about configuring the work-around.

      Thanks again,

      Aaron

      Comment

      • Toner Boy
        Trusted Tech

        Site Contributor
        250+ Posts
        • Aug 2007
        • 357

        #4
        New alternative

        After a couple of minutes thnking this issue through, I decided to create a new alternative (until the first idea can be accomplished). For now, I am going to host the client folders on another computer running Windows XP, share the main directory, and assign this folder as a virtual network directory within IIS for web access.

        FYI: These folders are also being used for back-end website operations where we can manage and access client information (i.e. Previous service call information) via the internet when our techs require detailed info while on the field.

        I would still appreciate a response on this idea of a work-around for Windows 2003 SMB scan.

        Thanks again,

        Aaron

        Comment

        • Toner Boy
          Trusted Tech

          Site Contributor
          250+ Posts
          • Aug 2007
          • 357

          #5
          Work-around working, but...

          Hello again,

          My work-around is in working order. I setup a virtual directory within IIS so we can still access our documents via the website and be able to scan SMB to one of the other workstations where the new location of the customer folders are located.

          New problem: We have over 600 customers. I created a script to read each customer from our database and replicate a folder for each named after the customers' company name (this saved a lot of time). I proceeded to test the scan to a customers' folder. Through the Gestetner, I accessed the Workgroup; and then the workstation. I selected the shared folder of the customer directory and only 105 folders showed up.

          Is there a limit of folder to view with this machine?

          Thanks in advance,

          Aaron

          Comment

          • Tonerbomb
            AutoMajical Resolutionist

            Site Contributor
            2,500+ Posts
            • Feb 2005
            • 2589

            #6
            P.S some of the older ricoh made machines need a firmware upgrade for 2003 smb scanning. the firmware will fix the 2003 smb packet signing issue that 2003 server has.
            Mystic Crystal Revelations

            Comment

            • Froota
              Field service tech.

              100+ Posts
              • Apr 2008
              • 129

              #7
              Originally posted by toner boy
              Hello,


              Problem: Browsing to server and scanning to server fails (Indicates entered username or password is invalid). Another computer within the same network, but not the same domain succeeds all scan attempts.


              Has anyone had a similar experience (issue) with setting this machine up for SMB scan in a similar networking environment?

              Thanks in advance
              Hey,

              I often install scan to folder on Ricoh multifunctionals, so i think this is a bit the same, not?
              If you get the message to enter a username and password, this is more an issue about rights rather than problems with connections.
              Make a local user with administrator rights on the server, without password, and share your folder with this account, also with all the securityrights.

              Also look the bulletin about smb signing on a server 2003. (attachement)

              succes,
              Froota

              Comment

              • fras

                #8
                this has been a helpful thread for me, I've been struggling to get scan to SMB working on our domain with win2003 servers.

                In order to get it to work I needed to change the digital signing group policies as outlined in the document above, and I also needed to change the group policy:

                Network Security: LAN Manager Authentication level

                to allow NTLM authentication.

                NTLM is the authentication type used by SMB.

                Once I did this it started working.

                Thanks.

                Comment

                • Froota
                  Field service tech.

                  100+ Posts
                  • Apr 2008
                  • 129

                  #9
                  Originally posted by fras
                  this has been a helpful thread for me, I've been struggling to get scan to SMB working on our domain with win2003 servers.

                  In order to get it to work I needed to change the digital signing group policies as outlined in the document above, and I also needed to change the group policy:

                  Network Security: LAN Manager Authentication level

                  to allow NTLM authentication.

                  NTLM is the authentication type used by SMB.

                  Once I did this it started working.

                  Thanks.
                  Good to hear!
                  thx for the reply.

                  froota

                  Comment

                  • RSFarrer
                    Technician
                    • Sep 2008
                    • 20

                    #10
                    Group Policy approach to SMB scanning

                    see the attached doc. this is what I've been doing to enable SMB scanning to Windows Server 2003.

                    the new copiers/MFPs have this fixed thankfully so I'm not doing this lately.

                    Comment

                    Working...