MPC2050 not connected to network

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Ltd
    Technician

    50+ Posts
    • Feb 2009
    • 90

    #1

    MPC2050 not connected to network

    Customer had Novell server had a bridge between server and printers, 2 HP printers worked w/o problem. 1 Canon MFP cannot connected to server due to IP problem, my new Mpc2050 just delivered today had same problem as Canon, cannot ping from local network to Ricoh
    Customer using IP started with first numbers 169.xxx.xxx.xxx for Ricoh copier, It didnot connect to network.
    Is there any settings at Ricoh to make it accept Ip starting 169.
  • unisys12
    Trusted Tech

    250+ Posts
    • Jul 2007
    • 490

    #2
    No. If the address is good/available, it should work.

    - Are the HP's connected to the network through the same bridge?

    - Have you checked their IP settings? You might find the missing info on their config sheets.

    - Be careful with 169 addresses. If the second octet is 254 (169.254.0.0) then that is your problem. This class is reserved for local link communication. Here is a paste from an article I found on the subject...
    169.254.0.0/16 - This is the "link local" block. It is allocated for
    communication between hosts on a single link. Hosts obtain these
    addresses by auto-configuration, such as when a DHCP server may not
    be found.

    sigpic
    The first law states that energy is conserved: The change in the internal energy is equal to the amount added by heating minus the amount lost by doing work on the environment.

    Comment

    • Ltd
      Technician

      50+ Posts
      • Feb 2009
      • 90

      #3
      Originally posted by unisys12
      No. If the address is good/available, it should work.

      - Are the HP's connected to the network through the same bridge?

      - Have you checked their IP settings? You might find the missing info on their config sheets.

      - Be careful with 169 addresses. If the second octet is 254 (169.254.0.0) then that is your problem. This class is reserved for local link communication. Here is a paste from an article I found on the subject...
      169.254.0.0/16 - This is the "link local" block. It is allocated for
      communication between hosts on a single link. Hosts obtain these
      addresses by auto-configuration, such as when a DHCP server may not
      be found.

      Yes, the HP's connected to the same bridge, 2nd octet is not 254.

      Comment

      • Patish
        Technician

        50+ Posts
        • Aug 2008
        • 66

        #4
        Try switch coper's "network speed" to 10.
        It would be reasonable connect laptop instead coper. Turn on DHCP and check your IP. You could print HP's configuration page and look at net parameters.

        Comment

        • Ltd
          Technician

          50+ Posts
          • Feb 2009
          • 90

          #5
          Originally posted by Patish
          Try switch coper's "network speed" to 10.
          It would be reasonable connect laptop instead coper. Turn on DHCP and check your IP. You could print HP's configuration page and look at net parameters.
          We did slow down speed to 10, did subnet, gateway like The HP's but somehow Ricoh not talking to network.

          Comment

          • unisys12
            Trusted Tech

            250+ Posts
            • Jul 2007
            • 490

            #6
            Originally posted by Ltd
            We did slow down speed to 10, did subnet, gateway like The HP's but somehow Ricoh not talking to network.
            Sounds like you need to do a packet capture. That's possible the only way your going to find out what really going on. Here's a thread I started awhile back that will get you started, if you've never performed one before.

            http://www.copytechnet.com/forums/co...reference.html
            sigpic
            The first law states that energy is conserved: The change in the internal energy is equal to the amount added by heating minus the amount lost by doing work on the environment.

            Comment

            Working...