5050 smb scaning 2203 code

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • shep
    Trusted Tech

    100+ Posts
    • Sep 2010
    • 108

    #1

    5050 smb scaning 2203 code

    connection timed out. it takes forever for it to do it. about 5 min per scan and then it codes, it happening on some computers and not on others, some windows 7 some xp. i have not seen this error and dont know what would cause it. i have disabled firewalls, i have used 445 port on the windows 7 machines and that has worked for some of them..... any other ideas???? thanks for the help.
  • blackcat4866
    Master Of The Obvious

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

    #2
    Are you sure it was SMB scanning? 2203 is specific to Email/FTP only:

    Send Email/FTP Error: Response Wait With Timeout. Response is not returned from the server, above specified time.
    Check the network connection (cable, network condition within LAN, etc.). =^..^=
    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

    • shep
      Trusted Tech

      100+ Posts
      • Sep 2010
      • 108

      #3
      yeah it is smb scanning, they are not set up for ftp or email scanning. my scan to email error code for smb scanning has it on there, it has the same explaination for all three smb, email, and ftp. i can pull the web browser from the machines, can not ping the machine though. it really makes not sense to me why its not working. ill try tech support today but past experience with scanning and tech support has not helped much. thanks

      Comment

      • jmaister
        certified scrub

        Site Contributor
        500+ Posts
        • Aug 2010
        • 755

        #4
        You need a packet sniffer and a person that can diagnose with the tool, above paygrade not worth our time. Check dns setting before calling it a day.
        Idling colour developers are not healthy developers.

        Comment

        • aragul
          Trusted Tech

          100+ Posts
          • Dec 2007
          • 128

          #5
          Originally posted by shep
          can not ping the machine
          That seems strange. Have you tried hooking up your laptop directly to the copier and pinging it and scanning SMB?

          Comment

          • jmaister
            certified scrub

            Site Contributor
            500+ Posts
            • Aug 2010
            • 755

            #6
            A mixture of XP and 7 OS in the office means its not properly thought out when its upgrading. Therefore the network was the last thing on the "to do" list and likely they dont have the know how to set it up properly. If you have any decent IT in the office, 7 is just not the way to go, yet.

            Its either ICMP that has been turned off or you have multiple routers in the place. I've only been to one place that ping was purposely disabled. Other than for air tight security purpose "ping" wouldnt be disabled.

            Its more than likely that the packet was lost.

            edit: As aragul advised, plug the laptop in prove that it works on your lappy, have their IT person look after it.
            Idling colour developers are not healthy developers.

            Comment

            • shep
              Trusted Tech

              100+ Posts
              • Sep 2010
              • 108

              #7
              Thanks for the replies its a head scratcher cause half of the people work fine so they know its not our machine, all the xp machines and about half of the 7 machines work, to make things worse they fired there old IT company and just got a new IT company that is working on it. so they don't know what all the old company did......

              Comment

              Working...