BizHub 223, no data lights?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • copyman
    Owner / Technician

    Site Contributor
    2,500+ Posts
    • Sep 2005
    • 4624

    #1

    BizHub 223, no data lights?

    Prints config page with correct IP. No data lights
    when ethernet cable plugged in. Cable is tested and
    live. Does printing config page confirm controller
    is good?
    Any type of reset, firmware or something else I
    could try?

    Thanks for the help
  • fuzzyg
    Junior Member
    • Oct 2011
    • 6

    #2
    Re: BizHub 223, no data lights?

    Originally posted by copyman
    Prints config page with correct IP. No data lights
    when ethernet cable plugged in. Cable is tested and
    live. Does printing config page confirm controller
    is good?
    Any type of reset, firmware or something else I
    could try?

    Thanks for the help
    We had a similar issue and it was the main brd that was faulty.

    We also tried firmware and all sorts but no getting around it unfortunately.

    Comment

    • copyman
      Owner / Technician

      Site Contributor
      2,500+ Posts
      • Sep 2005
      • 4624

      #3
      Re: BizHub 223, no data lights?

      Turns out the router was bad. Now have lights at port on copier but still won't ping. I tried a few different IP's didn't help. Any ideas ?

      Thanks again

      Comment

      • wseyller
        Service Manager

        1,000+ Posts
        • Sep 2012
        • 1129

        #4
        Are the network settings configured properly for the new router? I would recommend going to the network settings on the copier and set to auto obtain. Let it pull a new IP address, gateway, dns, from the new router. Most routers will have its own dhcp server and the copier can obtain all the network settings automatically. This copier it will make you turn off main power off then back on. Give it time to pull a new IP. Look and see what the new IP address of the copier is and try to ping it. If good then set the copier to manual in the TCP/IP settings and change the IP to what you want (change to unused IP in the same subnet range) and ping again to confirm it is still OK.

        Could be the new router is on a different subnet range which happens a lot when changing router as the default config differs between routers.

        Comment

        Working...