D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: jgreiner on January 11, 2009, 07:16:16 PM
-
Through a DIR-655 using DHCP, I am unable to print to a networked (wired) HP LaserJet5. The LJ5 is receiving an IP which is verified by it's printed configuration page and also is listed on the DIR-655 status page. Additionally, am unable to ping the LJ5's IP address..no returns, just times out. Prior to implementing the DIR-655, had no issues printing when networked to another brand router. Help!
-
Check your HP manual for the right setup of the network printer. If I remember correctly the printing protocol should be LPR.
-
Through a DIR-655 using DHCP, I am unable to print to a networked (wired) HP LaserJet5.
What happens when you try?
-
Any firewall blocking the printerport...?
-
When attempting to print, the document just hangs in the queue attempting to establish a connection, then when unable, states 'unable to print'.
No firewall blocking the port unless it's something in the 655 config that I'm not seeing. What stumps me is the fact that I can 'see' the printer and it's IP on the 655 status page (also verified that the printer is picking up the 655 DHCP-assigned IP via it's printed self-test), but am unable to ping it through a cmd prompt or in the 655 'system-check' page. Also attempted to add the printer again (adding a TCP/IP port/IP) using the assigned IP, but it's unable to establish a connection.
-
If you:
1. Disable DNS Relay on Setup - Network Settings; plus
2. Set a Manual uplink speed on Advanced - QOS Engine (disable Automatic uplink detection); and
3. Restart the DIR-655, the printer, and the computer you are using to test; and
4. Wait 10 minutes
Does this resolve the problem?
If so, this is related to a reported DNS Relay bug in 1.2x firmware. Please advise, because D-Link is having trouble confirming this bug.
http://www.dslreports.com/forum/r21581163-Printing-and-LAN-problems-with-DIRfirmware-12X
-
When attempting to print, the document just hangs in the queue attempting to establish a connection, then when unable, states 'unable to print'.
No firewall blocking the port unless it's something in the 655 config that I'm not seeing. What stumps me is the fact that I can 'see' the printer and it's IP on the 655 status page (also verified that the printer is picking up the 655 DHCP-assigned IP via it's printed self-test), but am unable to ping it through a cmd prompt or in the 655 'system-check' page. Also attempted to add the printer again (adding a TCP/IP port/IP) using the assigned IP, but it's unable to establish a connection.
Check if you use the right protocol for network printing (PC printer driver setting). I have a strong feeling this is the cause.