Problems scanning on Server 2008 R2.

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • KalEl
    Technician
    • Jun 2011
    • 35
    #1

    Problems scanning on Server 2008 R2.

    Hi Guys,

    I've got a client with a number of MFPs on their network, different manufacturers. I got called in the other day as they have switched from a 2003 server to 2008R2. All the MFP's on the network had stopped Scanning SMB...

    When I arrived it turned out to be only one brand that had stopped working and they are rebadged Kyoceras. with all the new details in I was getting an "1103" fail report.

    Name: John Smith
    Hostname : JOHNSPC
    Port : 139
    Destination : Data\Share\Scans\test

    As soon as I put the same information in to a different departments machine (A Develop/Konica) it went through straight away.

    The things I've tried....

    Changed the port number to 445. Same problem.
    Given the user the network admins credentials so that have full rights. Same problem.
    Browsed the network direct from the copier and saved in the address book and it scanned to the root folder (DATA) and not the specific folder I chose it to scan to.

    Created a fresh brand new test account and it scanned successfully even though I got a failed connection when testing it through the machines browser page. File however did not turn up in the destination folder required. it turned up in the DATA folder after I searched the file name.

    No matter what I try it goes into that DATA file and not the required folder. I would put it down to the share name but it worked fine on the other brands machine using the same method! Has anyone ever had this problem?

    Kyocera models are... DCC2930, FS-C8525 and FS-3140+

    Any help is appreciated. Cheers.
    Tags: None
    • KalEl
      Technician
      • Jun 2011
      • 35
      #2
      Re: Problems scanning on Server 2008 R2.

      Sorry also forgot to mention that all three machines are on the latest firmware released. Cheers

        Comment

        • blackcat4866
          Master Of The Obvious

          Site Contributor
          10,000+ Posts
          • Jul 2007
          • 23010
          #3
          Re: Problems scanning on Server 2008 R2.

          Originally posted by KalEl
          Hi Guys,

          Name: John Smith
          Hostname : JOHNSPC
          Port : 139
          Destination : Data\Share\Scans\test
          A few things I'd check are:
          1) folder properties: based on your path "Data" should be the only folder in the path shared. Sub-folders "Share", "Scans", and "Test" should not have share properties. Is "Data" on the root of the drive?
          2) Are you using: \\domain\username\ ?
          3) I would expect that port 445 would be required, unless 139 is specifically opened up to SMB.

          =^..^=
          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

            • KalEl
              Technician
              • Jun 2011
              • 35
              #4
              Re: Problems scanning on Server 2008 R2.

              Hi BlackCat,

              Thanks for your response.

              Data is on the root of the drive. exact path is E:\data\share\scans\test

              I haven't put the domain in username. I've created this account under the network administrators login, so it has full rights.

              Thanks.

                Comment

                • Swift
                  Technician
                  • Apr 2011
                  • 29
                  #5
                  Re: Problems scanning on Server 2008 R2.

                  Hi,

                  Maybe you would like to verify if the Windows 2008 R2 SMB version 1.0 is it disable.
                  Up to date KYOCERA devices able to support SMB 1.0
                  Hope it help.

                  Cheers!

                    Comment

                    • RollingROARANDA
                      Technician
                      • Nov 2012
                      • 72
                      #6
                      Re: Problems scanning on Server 2008 R2.

                      Try this:

                      1. Create a New Folder in the root of the drive, name it "scans2" or whatever.

                      2. Cut and Paste or Move whatevers in the old folder to the new one.

                      3. SHARE out the new folder, and ensure that it is Shared and the Security and permissions are correct on the Folder's Properties. Typically, 1103 means "username password" and this is linked to folder permissions as well.

                      Test Settings.

                      Hope this helps

                        Comment

                        • KalEl
                          Technician
                          • Jun 2011
                          • 35
                          #7
                          Re: Problems scanning on Server 2008 R2.

                          Hi Guys,

                          Thanks for everyones help...

                          I did check all the permissions. Basically I can't touch the server as its a financial sector and they won't let a third party near it. They were adamant that it was the kit as another MFP would work. It did baffle me how the Kyocera/Utax would scan but then dump it in the root folder and not the specified path.

                          So I think it must be the way he has shared it. I sent him this info about 10 days ago and not heard a thing back so fingers crossed. I'll put it in here incase it helps anyone else. This is all info gethered by various replies to my threads so thank you everyone that posted!

                          Of course now that I have posted it here as fixed, I'll get a call saying "Same problem - Isn't Working". Fingers crossed.

                            Comment

                            Previous template Next
                            Working...