CompTIA A+ Core 1 (220-1201)Hardware and Network TroubleshootingHard
A technician is troubleshooting a network printer that is reachable via its IP address (ping works) from all workstations on the network, but no workstation can print to it. When users attempt to print, the print jobs get stuck in the print queue or disappear without an error message. What is the MOST likely cause?
- AFirewall blocking print services ports on the printer or workstations.
- BThe printer is offline or out of paper/toner.
- CIncorrect printer driver installed on workstations.
- DDHCP server misconfiguration.
Show answer & explanationAnswer & explanation
Correct answer: A. Firewall blocking print services ports on the printer or workstations.
If the printer is reachable by IP (ping works) but print jobs don't go through, it strongly suggests a higher-layer issue, typically a firewall blocking the necessary print service ports (e.g., TCP 9100 for Raw, UDP 161/162 for SNMP, TCP 515 for LPR). The firewall could be on the printer, a server managing print queues, or the workstations themselves.
Why the other options are wrong
- B. If the printer was offline or out of supplies, ping would still work, but print jobs would typically show an error message like 'offline' or 'out of paper'.
- C. Incorrect printer drivers might cause garbled print or specific formatting issues, but usually wouldn't prevent print jobs from reaching the printer or cause them to disappear silently if the connection is established.
- D. DHCP misconfiguration would prevent the printer from getting an IP address or workstations from reaching it, which contradicts the fact that ping works.
Network Printer Firewall Block
A firewall (on the printer, a server, or client) that is preventing communication over the specific ports used for network printing services.
- Printer is reachable by ping, but print jobs fail.
- Common ports: TCP 9100 (Raw), TCP 515 (LPR), UDP 161/162 (SNMP).
- Requires checking firewall rules on all involved devices.
Memory trick: If the printer 'pings' but 'pages' don't flow, check the 'firewall' to see why they don't go.