Kyocera ci problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • BillyCarpenter
    Field Supervisor

    Site Contributor
    VIP Subscriber
    10,000+ Posts
    • Aug 2020
    • 14752

    Kyocera ci problem

    I have a 4551ci. The customer said the power went out over the weekend and now it won't print. I can ping the copier but can't access the Command Center and it won't print.

    I just got off the phone with their IP guy and he said that an HyPass app grabbed the IP address of the copier and that's the reason for the problem. I'm abou to head back over there.

    Any advice? Thanks.
    Adversity temporarily visits a strong man but stays with the weak for a lifetime.
  • tsbservice
    Field tech

    Site Contributor
    5,000+ Posts
    • May 2007
    • 7635

    #2
    Re: Kyocera ci problem

    Originally posted by BillyCarpenter
    I have a 4551ci. The customer said the power went out over the weekend and now it won't print. I can ping the copier but can't access the Command Center and it won't print.

    I just got off the phone with their IP guy and he said that an HyPass app grabbed the IP address of the copier and that's the reason for the problem. I'm abou to head back over there.

    Any advice? Thanks.
    Billy another thought - may be an IP conflict. Another device on network can get MFP IP after power outage. Change MFP IP for the time being, ping new IP and try Command Center if it works then You know.
    A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
    Blessed are they who can laugh at themselves, for they shall never cease to be amused.

    Comment

    • bsm2
      IT Manager

      25,000+ Posts
      • Feb 2008
      • 27442

      #3
      Re: Kyocera ci problem

      Have customer unplug the copier and ping it

      Change the IPaddress or have there IT make a reservation for the copier

      Comment

      • allan
        RTFM!!

        5,000+ Posts
        • Apr 2010
        • 5445

        #4
        Re: Kyocera ci problem

        Originally posted by BillyCarpenter
        I have a 4551ci. The customer said the power went out over the weekend and now it won't print. I can ping the copier but can't access the Command Center and it won't print.

        I just got off the phone with their IP guy and he said that an HyPass app grabbed the IP address of the copier and that's the reason for the problem. I'm abou to head back over there.

        Any advice? Thanks.

        Agreed. Ask the guy to do a MAC reservation on the printers IP.

        When installing a machine if you can help it don't use the first IP address that DHCP dishes out. Like to keep the address out of the DHCP pool. If the router is setup well it should only include form xxx.xxx.xxx.11 to xxx.xxx.xxx.249.The IP's out of that range would be used for things that require a static address.
        The IP I try to use if open is 192.168.0.252.
        Whatever

        Comment

        • BillyCarpenter
          Field Supervisor

          Site Contributor
          VIP Subscriber
          10,000+ Posts
          • Aug 2020
          • 14752

          #5
          Re: Kyocera ci problem

          I apologize for not providing much information. I was on my way out the door when I made the post.


          Here's the situation. The printer is set to a static IP address that was outside of the DHCP range. The customer had a new router installed after that and he said the printer was working fine after the new router was installed.

          Over the weekend he said the power went out and now it's not printing. No settings in the copier have changed.

          Their IT guy logged in remotely and said after the router went down due to power outage that it re-assigned the IP address to a Hypass app. I go back and delete the Hypass app.

          I can ping the copier but still can't access the web interface and it won't print. There is no duplicate IP address. I checked. Twice.
          Adversity temporarily visits a strong man but stays with the weak for a lifetime.

          Comment

          • bsm2
            IT Manager

            25,000+ Posts
            • Feb 2008
            • 27442

            #6
            Re: Kyocera ci problem

            Originally posted by BillyCarpenter
            I apologize for not providing much information. I was on my way out the door when I made the post.


            Here's the situation. The printer is set to a static IP address that was outside of the DHCP range. The customer had a new router installed after that and he said the printer was working fine after the new router was installed.

            Over the weekend he said the power went out and now it's not printing. No settings in the copier have changed.

            Their IT guy logged in remotely and said after the router went down due to power outage that it re-assigned the IP address to a Hypass app. I go back and delete the Hypass app.

            I can ping the copier but still can't access the web interface and it won't print. There is no duplicate IP address. I checked. Twice.
            Something changed
            Set copier to DHCP and see what address it pulls
            Than re enter the static and test again or setup the mini network your laptop switch and cables and test print and web access

            Comment

            • tsbservice
              Field tech

              Site Contributor
              5,000+ Posts
              • May 2007
              • 7635

              #7
              Re: Kyocera ci problem

              I'm sure You've checked it but but make sure they power cycled MFP.
              A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
              Blessed are they who can laugh at themselves, for they shall never cease to be amused.

              Comment

              • bsm2
                IT Manager

                25,000+ Posts
                • Feb 2008
                • 27442

                #8
                Re: Kyocera ci problem

                Some devices don't reply to a ping request pretty rare but possible. Assign it a different ipaddress if necessary.

                See now your in goat territory. Ha

                Comment

                • BillyCarpenter
                  Field Supervisor

                  Site Contributor
                  VIP Subscriber
                  10,000+ Posts
                  • Aug 2020
                  • 14752

                  #9
                  Re: Kyocera ci problem

                  Luckily this account is only a few blocks down the road. I just made a 3rd trip and here's the deal.

                  Before I left I searched the forum for any old threads that pertained to the same issues. Blackcat offered a couple of suggestions. I'll just repost what he said:



                  It's destructive ... but a U021 will wipe out any network settings, and a lot of machine settings. I think first, I might try the following PreScribe commands:
                  !R! ACNT "EGRE";EXIT;

                  or
                  !R! ACNT "REST";EXIT;

                  That should just reset the printer NIC. =^..^=


                  The prescribe commands were over my head so I ran U021 and that fixed the problem. I don't really understand why other than the network settings changed on the copier when the power went out.

                  PS - I've got to get blackcat to explain the prescribe commands to me.

                  Adversity temporarily visits a strong man but stays with the weak for a lifetime.

                  Comment

                  • BillyCarpenter
                    Field Supervisor

                    Site Contributor
                    VIP Subscriber
                    10,000+ Posts
                    • Aug 2020
                    • 14752

                    #10
                    Re: Kyocera ci problem

                    PS - Before I ran U021 i changed to DHCP and it pulled the same IP address - 10.157.1.113. It wouldn't pull a different IP address. I don't know if their IT guy accessed the router remotely and reserved the IP address. The guy never called me back. Nothing worked unit I ran U021. But it did wipe out the address book.
                    Adversity temporarily visits a strong man but stays with the weak for a lifetime.

                    Comment

                    • bsm2
                      IT Manager

                      25,000+ Posts
                      • Feb 2008
                      • 27442

                      #11
                      Re: Kyocera ci problem

                      Kyocera Nic cards freeze sometimes
                      If you had followed the advice of setting the card back to DHCP and then checked You would Not had to run a U21.

                      Prescribe commands send data to make setting and parameters changes. Almost NEVER Ever had to do unless You know what your doing or Hotline or tech rep tells you to do it.

                      Comment

                      • BillyCarpenter
                        Field Supervisor

                        Site Contributor
                        VIP Subscriber
                        10,000+ Posts
                        • Aug 2020
                        • 14752

                        #12
                        Re: Kyocera ci problem

                        Originally posted by bsm2
                        Kyocera Nic cards freeze sometimes
                        If you had followed the advice of setting the card back to DHCP and then checked You would Not had to run a U21.

                        Prescribe commands send data to make setting and parameters changes. Almost NEVER Ever had to do unless You know what your doing or Hotline or tech rep tells you to do it.

                        Read the post above yours. I did change to DHCP. Didn't work.
                        Adversity temporarily visits a strong man but stays with the weak for a lifetime.

                        Comment

                        • bsm2
                          IT Manager

                          25,000+ Posts
                          • Feb 2008
                          • 27442

                          #13
                          Re: Kyocera ci problem

                          Originally posted by BillyCarpenter
                          Read the post above yours. I did change to DHCP. Didn't work.
                          Did you power cycle the machine after the change?
                          no

                          You must power cycle almost all changes for them to take affect.

                          Comment

                          • BillyCarpenter
                            Field Supervisor

                            Site Contributor
                            VIP Subscriber
                            10,000+ Posts
                            • Aug 2020
                            • 14752

                            #14
                            Re: Kyocera ci problem

                            Originally posted by bsm2
                            Did you power cycle the machine after the change?
                            no
                            Certainly.
                            Adversity temporarily visits a strong man but stays with the weak for a lifetime.

                            Comment

                            • Santander
                              Senior Tech

                              Site Contributor
                              500+ Posts
                              • May 2009
                              • 768

                              #15
                              Re: Kyocera ci problem

                              Originally posted by BillyCarpenter
                              Read the post above yours. I did change to DHCP. Didn't work.
                              After you changed the unit to DHCP did you power cycle the machine? Changes to the network only take effect after a reboot.

                              Comment

                              Working...