Kyocera 3500i SMB Scan troubles

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • copygal
    Technician
    • Feb 2012
    • 23

    #1

    Kyocera 3500i SMB Scan troubles

    Peer to peer network with copy, print, fax and scan to email working fine. Customer has been using SMB scan to pc for 6 months with no troubles, until recently.
    Customer is using Kaspersky antivirus and firewall...and we cannot get the host name of the receiving computer to reconcile with the copier. if the ip address is used, the scan to folder at the pc has not trouble at all. code for the connection error is 2203. IT refuses to believe it is within firewall and pc permissions and is insisting it is a firmware update that is required.

    I tested my laptop with a machine at my office with settings and it worked flawlessly, then tested laptop on customers network with failure. Kyocera tech support recommended a test with just laptop connected to copier(no customer network involved) to test smb scan. Can anyone help?? I was told the NetBIOS Primary directory was not reading right for some reason, that is why the host name isnot working, but the IP address will. AAARRGGG!!
  • Santander
    Senior Tech

    Site Contributor
    500+ Posts
    • May 2009
    • 768

    #2
    Re: Kyocera 3500i SMB Scan troubles

    We used to run Kaspersky in our office, by default it blocks port 445 which causes problems with the smb scanning. Try changing the port to 443 [Kaspersky doe not bother that port] under the scanner tab and in the address book. Since you say that they could scan six months before installing Kaspersky. If my memory serves me correctly Kaspersky as a default does allow Netbios for local addresses so this should not be a problem. Hope this helps.

    Comment

    • Iowatech
      Not a service manager

      2,500+ Posts
      • Dec 2009
      • 3930

      #3
      Re: Kyocera 3500i SMB Scan troubles

      I'm no expert on connected issues, but I'd guess the operating system that the customer's computer is running might be an important piece of information you may wish to share if possible. And maybe the operating system your laptop is running as well. At least that would be some things I'd like to know if I was able to help you. Win 7, 8 and 10 have a lot of similarities, but also there are some striking differences between them as well.
      Sorry if that was a waste of time.

      Comment

      • nmfaxman
        Service Manager

        Site Contributor
        1,000+ Posts
        • Feb 2008
        • 1702

        #4
        Re: Kyocera 3500i SMB Scan troubles

        Turn off the firewall and test it. If it works, it is not the machine, therefore not your problem.

        Firmware is never a magic fix if it is not listed in the list of repairs.

        Typically, if scan to email works, SMB is a Firewall, security or authentication problem.

        Scan works the same way. It is the direction it is pointed to that is different.
        I myself am tired of IT idiots always blaming the machine and making us do their job for them.

        Hook your laptop to it with a crossover cable and firewall turned off.
        Scan, then tell this lazy moron to open ports 137,138,139 and 445 on the firewall. If he asks you to do it, let his boss know he is worthless. He installed the software and doesn't even know how to operate it.

        It is called "HELP" in any program, he needs to learn how to do his own research.

        Just my rant for the week. In pain and feeling bitchy.
        Why do they call it common sense?

        If it were common, wouldn't everyone have it?

        Comment

        • slimslob
          Retired

          Site Contributor
          25,000+ Posts
          • May 2013
          • 37240

          #5
          Re: Kyocera 3500i SMB Scan troubles

          Things that I have encountered concerning name resolution on Ricoh equipment.
          1. If the customer has a Domain the domain name needs to be properly set and the first DNS must be the local DNS.
          2. If the customer's network is a workgroup, the workgroup name must be correctly.
          3. Have the IT people check that NETBios over TCP/IP is not disabled either by the DHCP, security policy, or at individual computers. SMB uses NETBios to do name resolution.


          The fact that using IP address works tells me that it is most like NETBios that is being blocked. If Kapersky were blocking it would also block scan to IP address.

          Comment

          Working...