1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Network Error HP LaserJet P2015dn

Discussion in 'Networking (Hardware & Software)' started by Kile, 2007/09/25.

  1. 2007/09/25
    Kile

    Kile Inactive Thread Starter

    Joined:
    2007/09/25
    Messages:
    4
    Likes Received:
    0
    [FONT= "Arial"]Hello,
    We have a Simple network in the office with 10 computers connected through a Switch (Power Switch CNET CNSH 1600) and a Patch panel.
    The problem is We can access the Internet and all other shared resources (Files, Folders and Printers) except the newly purchased printer HP LaserJet P2015dn which we have installed through the network detected having IP Address 169.254.151.38 and Mac address 001A4B13E51F. The printer is successfully installed but when you print any document it gives a print error message. Can you please help me to sort out this problem.

    Your help is greatly appreciated.

    Nb: All computers acquire IP addresses dynamically.
    [/FONT]
     
    Kile,
    #1
  2. 2007/09/26
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    From what? Do you have a server or router on the network giving out IP addresses? That address (169.254.151.38) is what I'd expect to see if there wasn't dynamic addressing on the network.

    Can you give an example of the IP address of another computer on the network?
     

  3. to hide this advert.

  4. 2007/09/26
    Kile

    Kile Inactive Thread Starter

    Joined:
    2007/09/25
    Messages:
    4
    Likes Received:
    0
    Network Printer error HP LaserJet P2015dn

    Hello,
    Computer's Ip address as 192.168.2.4 etc., and default gateway as 192.168.2.1

    While installing the Network printer just after the printer was detected and the assigned ip address 169.254.151.38 there was an option whether the ip address should be assigned automatically or set a static address. Could this be the solution.

    Hope to hear soon from you.

    Thanks,

    Kile.
     
    Kile,
    #3
  5. 2007/09/26
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    IP addresses in the 169.254.0.0 subnet are automatically generated by a system set to dynamic when it can't find a DHCP server to give it an IP address (most modern routers have DHCP built in). Therefore, it is a classic symptom of a system not being able to communicate correctly on the network.

    The most likely cause is a basic connection problem:
    • Faulty cable - try a different cable
    • Wrong type of cable. With routers you often need to use a standard straight-through cable. If you connect using a cross-over cable, you can get the error you are seeing.
    • Faulty port - try connecting to a different port on the router
    • Cable not connected correctly - check that your cables haven't become disconnected.
    If none of the above works, try setting the IP address of the printer manually. 192.168.2.200 should be OK.

    If none of that works, there is a possibility that it is the network NIC in the printer that is faulty.
     
  6. 2007/09/26
    Dennis L Lifetime Subscription

    Dennis L Inactive Alumni

    Joined:
    2002/06/07
    Messages:
    2,557
    Likes Received:
    2
    For my curiosity ....
    Reggie, if network printer was configured as static address and nothing was inputed to static IP field when originally configured, could this cause / force a 169.154.x.x subnet IP assignment??
    Technically, I would be disappointed in user interface software if it allowed this action to occur (no IP address inputed into static request IP field).
     
  7. 2007/09/27
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    I think that depends on the software. Most systems won't let you leave the fields blank.

    Automatic should always try to find an IP via DHCP or BOOTP first. 169.154.x.x should be what the system falls back on after it has failed to get a response to the BOOTP packets.

    Use of the address space 169.154.0.0/16 (IPv4 Link-Local addresses) is set out in RFC 3927. Within this, section 1.9.2 states:
    I think not using a DHCP address when one was present would go against this directive. However, I also think RFC are advisory - a bad designer may not follow this.
     
  8. 2007/09/27
    Dennis L Lifetime Subscription

    Dennis L Inactive Alumni

    Joined:
    2002/06/07
    Messages:
    2,557
    Likes Received:
    2
    Thank you Reggie.
    Sorry, did not mean to high-jack thread.
     
  9. 2007/09/27
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    No problem - I think the extra background may make it easier for the original poster to understand what is going on. And then there is the fact that I enjoy getting my geek hat on :)
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.