SMTP Trouble after replacing NIC

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tmaged
    Owner/Service Manager

    Site Contributor
    1,000+ Posts
    • Oct 2008
    • 1868

    #1

    SMTP Trouble after replacing NIC

    I have a customers ES230 that had the NIC go bad. I pulled the NIC off our 200L in the service area & installed it on the customers machine. I put their IP address in & thought all was good. They called the other day saying they are unable to email. I went there & all of my SMTP settings were in the web page. Evidently this is on the NIC pwb ??? I changed all the settings to theirs & haven't been able to get it to work. Tried 08-947. Still no SMTP. Everthing else seems to work. I don't want to do 08-693 right? It should have worked on theirs since all my SMTP settings were right. Any way to re-initialize SMTP? Not sure where to go next.
    Thanks for any help.
    Hope that helps !
    -Tony
    www.dtios.com
    Become a fan on Facebook
  • atudorica
    Technician

    50+ Posts
    • Oct 2007
    • 79

    #2
    take the easy way
    save your network setings
    do 08-693 up to 20 times
    when you wil see "initialize" button on screen is done
    you will be amaized

    Comment

    • tmaged
      Owner/Service Manager

      Site Contributor
      1,000+ Posts
      • Oct 2008
      • 1868

      #3
      Does 08-693 affect the Firmware on the NIC or just restores all settings. I was concerned it would revert the firmware to an older version or something.
      Thanks,
      Hope that helps !
      -Tony
      www.dtios.com
      Become a fan on Facebook

      Comment

      • Baphomet
        Copier Technician

        250+ Posts
        • Aug 2008
        • 293

        #4
        I'd say do yourself a favor before you just go wild guessing about it. Go into the job log and see what code is given for the scan jobs that did not go through then look up the code in the handbook. It will tell you, for instance, if it was a communication error, authentication error, couldn't find the server, etc ... Most likely the error code will lead you in the right direction. If you don't have the service handboook, post the code I and will let you know what it means.

        Comment

        • ivovb
          Senior Tech

          500+ Posts
          • Apr 2008
          • 695

          #5
          In addition to Baphomet's post I would check firmware versions of both copy machines. All firmwares must be bundle in order system to work.
          BR
          I'll never ask if I didn't check user manual, service manual, parts list, BSI/TNI/TAD... web, existing threads.

          Comment

          • Baphomet
            Copier Technician

            250+ Posts
            • Aug 2008
            • 293

            #6
            Originally posted by ivovb
            In addition to Baphomet's post I would check firmware versions of both copy machines. All firmwares must be bundle in order system to work.
            BR
            It is true the if you revert the firmware and the NIC is at a more recent version it will ruin the NIC. But in that instance you would not be able to connect to the network at all.

            I might just throw this into the discussion just for thought. I went to an account where the customer complained that the scan to email quit working. I get there and the job log indicated "OK" where the jobs were sent. The problem was that the customers mail server was down and not delivering the mail that day. A few hours later she received everything she had scanned. It is important to use the job log when troubleshooting scanning issues, otherwise you are just beating yourself to death.

            Comment

            • mckinley
              Chief Twiddler

              100+ Posts
              • Dec 2006
              • 150

              #7
              two things...
              1. you do realise that if you have changed the NIC, the machine will have a different MAC address & therefore could be seen as an intruder on the network.
              2. If the network is using anything such as SMB & it requires specific settings ( username / pwd or admin login / pwd, smb path ), smtp will fail.
              I would speak to their network admin if they have one, or try to speak to who set the machine up on the network.
              Happiness Is The Road.

              Comment

              • atudorica
                Technician

                50+ Posts
                • Oct 2007
                • 79

                #8
                my reset worked every single time
                if you print but can't scan to email
                you need to reset the NIC
                do 08-693 until you'll see "initialize" button
                this is your fix

                Comment

                • tmaged
                  Owner/Service Manager

                  Site Contributor
                  1,000+ Posts
                  • Oct 2008
                  • 1868

                  #9
                  Originally posted by Baphomet
                  I'd say do yourself a favor before you just go wild guessing about it. Go into the job log and see what code is given for the scan jobs that did not go through then look up the code in the handbook. It will tell you, for instance, if it was a communication error, authentication error, couldn't find the server, etc ... Most likely the error code will lead you in the right direction. If you don't have the service handboook, post the code I and will let you know what it means.
                  I found all the error codes for scanning in the SH. I can't find where it lists the code. I've attached the Job log screen shot. I also tried clear/8 when I get the failed to send email error thinking it would display the error code. I also printed the error history list. Sadly, all were failures.
                  Am I missing something obvious ?
                  PS I did try 08-693 & reset all the SMTP settings.
                  Hope that helps !
                  -Tony
                  www.dtios.com
                  Become a fan on Facebook

                  Comment

                  • Sbarro
                    Trusted Tech

                    100+ Posts
                    • Feb 2008
                    • 176

                    #10
                    Your authentication is set to PLAIN. It usually is LOGIN. Try another too.
                    "A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it"

                    "
                    What do you despise? By this you are truly known"

                    Guess who

                    Comment

                    • atudorica
                      Technician

                      50+ Posts
                      • Oct 2007
                      • 79

                      #11
                      when you did 08-693 did you see "initialize" button on screen?
                      if not, repeat until you see that and press it
                      this is the last time I tell you to do that

                      Comment

                      • tmaged
                        Owner/Service Manager

                        Site Contributor
                        1,000+ Posts
                        • Oct 2008
                        • 1868

                        #12
                        Originally posted by atudorica
                        when you did 08-693 did you see "initialize" button on screen?
                        if not, repeat until you see that and press it
                        this is the last time I tell you to do that
                        Yep, I didn't see it until the 4th time. It would just say initializing after I hit the start key. I finally got the Initialize button though. I did swing back by & changed the authentication from Plain to Login. Didn't help though.
                        Hope that helps !
                        -Tony
                        www.dtios.com
                        Become a fan on Facebook

                        Comment

                        Working...