Skip to main content
Answer

can't browser for Windows printers

  • March 27, 2012
  • 5 replies
  • 22 views

Forum|alt.badge.img+9

* Can't BROWSE for Windows Printers *

Good day to all.

Our Macs are joined to our AD domain. Our Windows Server printers are shared out through AD. Our Macs used to be able to browse for the shared Windows printers in the Add Printer dialog within System Prefs. Now, all of the sudden, our Macs cannot browse the Windows printers. Only a few printers show up. This happens on both 10.6 and 10.7.

I didn't change anything on the Macs so I'm not sure what the problem could be. Apparently the Windows clients can still browse for printers.

Do you have any ideas?

Best answer by catfeetstop

We figured it out! It was an issue on the Windows print server. Apparently they had to reset the spooler or something. Thanks for the help!

5 replies

Forum|alt.badge.img+10
  • Contributor
  • March 27, 2012

Is your windows print server on the same domain/forest than your mac binder to AD... ?

we have the same situation that has been going forever because of that situation...

we manage to push printers through terminal with LPD printer queue...


Forum|alt.badge.img+9
  • Author
  • Contributor
  • March 27, 2012

I just asked our Network Manager, he says the Windows server is on the same domain. It's strange that a few of the Windows print server printers show up. I wonder what's different about those printers?

It's gotta be something on the Windows server! WINDOWS!!!!!!!!


Forum|alt.badge.img+4
  • Contributor
  • March 27, 2012

I have the same situation on my network as well, even with the print server in the same domain.

I found a very un-proper workaround, that works for me.
Just unbind the client to AD and rebind it again. All your printers will show up.
Hopefully.

regards


Forum|alt.badge.img+9
  • Author
  • Contributor
  • March 28, 2012

Thanks for the suggestions. I tried unbinding and rebinding, that didn't work for me.


Forum|alt.badge.img+9
  • Author
  • Contributor
  • Answer
  • March 28, 2012

We figured it out! It was an issue on the Windows print server. Apparently they had to reset the spooler or something. Thanks for the help!