CS 2560 Scanner Setup Issue

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Gym Teacher
    • May 2025

    #1

    CS 2560 Scanner Setup Issue

    I'm working with a 2560 where the scan to smb function will not properly set up. The parameters seem correct, including the path and user name/domain.

    The scan to smb has never been set on this machine. Might this be a driver issue? Doesn't the 2560 come out of the box with the required drivers installed? If not, can someone please point me to the proper download page for them?

    Thanks much.
  • blackcat4866
    Master Of The Obvious

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

    #2
    This document covers it all.
    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

    • aodtech
      Trusted Tech

      100+ Posts
      • Nov 2007
      • 194

      #3
      Eliminate any firewall as the problem. If you have something like McAfee, Norton, AVG, etc then disable it and try scanning. I had AVG disable the File & Printer Sharing Service in Windows. Also try Windows Firewall. You'll see File & Printer Sharing in the list of exception. Highlight it and click on edit. Highlight either port 139 or 445 and click Change Scope. Change the setting to Any Computer instead of My Network. This is what was hindering me from getting an 1820 from scanning. But before you even mess around with that try scanning with either or both Third Party and Windows Firewalls disabled. If all else fails, you can scan via Scanner File Utility. There should be a thread somewhere on here with instructions.

      Comment

      • Gym Teacher

        #4
        Thanks AOD and BlackCat for your replies. I followed the instructions and suggestions you sent. To no avail. However, I did find a solution.

        I simply used the IP address (fixed) for the host PC. I was so focused on using the computer name for the host name, that I did not think about using the IP address. It scanned on the first try after changing the computer name to the IP address.

        Thanks again for your help.

        Comment

        • blackcat4866
          Master Of The Obvious

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

          #5
          That's very common. Host names are desirable, but don't always work. I save the IP as a last resort just in case DHCP hands out a different IP at power up. =^..^=
          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

          • Gym Teacher

            #6
            Yes, CatMan, you are right. I read somewhere that the host name was required (probably because of the possibility of 'floating' IPs from the DHCP server), so I didn't think about using the IP. But, as you say, the last resort was to try the IP address.

            I restored all the firewalls and the unit is functioning properly.

            Thanks again.

            Comment

            Working...