I had the same problem.
My solution was to go into the printer properties on the client machine and
under ports, I had to uncheck the Enable bidirectional support box in order
for them to work.
Then this allowed me to print just fine but it added a new problem.
Being as the printer was seen from Active Directory, disabling the
bidirectional support on the client also disabled it on the server where the
printer is physically attached. When this happened, the printers status
monitor would pop up saying I had lost comms with the printer.
Normally I'd get rid off the status monitor but this is a color laser and
the status is nice for toner level checks!
What I ended up doing was telling 2k3 to NOT list the printer in the
directory but still keep it shared and then on each client I installed a
local copy of the driver and pointed it to \\servername\sharename and I also
had to still turn off bi-directional support on each client.
Has worked perfect for me ever since!
"Joe Williams" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> THe printer is being shared on a client computer, not the server. But no,
> when clients browse the client, they do not see anything.
>
> The printer DOES show up in AD, but when you try to connect to it you get
> an error message "Cannot conenct to printer, the printer may have lost
> connection with the server"
>
> Joe
>
>
> "Todd J Heron" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> When clients browse the server (\\servername) do they see the printer
>> shares? Also when they search in AD, do these printer shares show up?
>>
>> --
>> Todd J Heron, MCSE
>> Windows Server 2003/2000/NT; CCA
>> ----------------------------------------------------------------------------
>> This posting is provided "as is" with no warranties and confers no
>> rights.
>>
>
>
|