Member Avatar for carlino

Ok, so here's my problem. From one of the workstations on our LAN it's not possible to print anymore to any of the network printers shared on the DC.
The DC runs 2000 Server and the workstation runs XP Pro.
The main printer is a sharp ar-275 but also the HP LJ4000 next to it has the same problem.
The drivers on the DC are for NT and 2000. But even though they're not for XP that shouldn't be the problem as it's worked just fine before.

And if I ping the DC, no problem. If I ping the printer, no problem.

What could be the problem here? I'm stuck! Anybody got an idea?

  • 4 Contributors
  • 4 Replies
  • 320 Views
  • 6 Days Discussion Span
  • Latest Post Latest Post by rasputinj

Dani AI

Generated

A single workstation that can still ping the server/printer but cannot print usually means a client-side block or misconfigured networking component rather than a cabling or IP problem. Good catches earlier from and point in the right directions — below is a compact, practical checklist that fixes the common causes while keeping the firewall enabled and the system secure.

  • Quick visibility test: from the XP machine open Explorer and enter \\<DomainControllerName> (or \\<IP>) to see shared printers. If shares are invisible, stop and check services/components; if visible, move on to printing-specific checks.
  • Windows Firewall (safe fix): Control Panel > Windows Firewall > Exceptions — enable “File and Printer Sharing” and click Change Scope to limit it to “My network (subnet) only” or add the DC’s IP. This opens the SMB/RPC traffic the spooler needs without disabling protection.
  • If you prefer port rules: allow TCP 139 and 445 (SMB) and UDP 137–138 (NetBIOS), or open printer-specific ports (9100 for raw/JetDirect, 515 for LPR) if the client talks directly to the device.
  • Services & NIC settings: ensure Print Spooler is running on both client and server, the Server service is running on the DC, and the client NIC has “Client for Microsoft Networks” and “File and Printer Sharing for Microsoft Networks” enabled.
  • Drivers: if the share connects but printing or driver installation fails, follow and install the correct XP/x86 drivers — add them on the print server using the shared-printer “Additional Drivers” option or install locally on the workstation.
  • Isolation test: add the printer as a Standard TCP/IP printer to the workstation (point at the printer’s IP). If that prints, the problem is the SMB share path, not the printer hardware.

Do not leave the firewall off. Use scoped exceptions or deploy the exception with Group Policy for domain machines, then verify by printing a test page from the affected workstation.

Recommended Answers

All 4 Replies

Member Avatar for Jonzsie

My printer stopped working after installing Windows SP2. When I disconnected the windows firewall (which was turned on by default when I downloaded SP2) it started working again.

Member Avatar for frrossk

Try reinstall the drivers on the workstation.

Member Avatar for carlino

It was the windows firewall that did it. The other users had disabled it on their own and that's why it worked for them.

Thanks for the help!!

Member Avatar for rasputinj

It was the windows firewall that did it. The other users had disabled it on their own and that's why it worked for them.

Thanks for the help!!

That is a quite common issue.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.