cups windows driver v6 and printer properties

Benoit SCHWINDEN benoit.schwinden at pharma.uhp-nancy.fr
Thu Jun 8 05:15:38 PDT 2006


Benoit SCHWINDEN a écrit :
> W. Engelhart a écrit :
> 
>> Unfortunately, the problem persists.
>>
>> I've double-checked the configuration on the Windows side. The driver 
>> has been copied and registered completely. Unfortunately, Windows does 
>> not give any hint how to analyse that problem.
>>
>> Could anybody give me a hint on how to analyse this? It must be a 
>> small, weird problem. But without any clue what goes wrong this is 
>> impossible to solve.
>>
>> Thanks & best, Wol.
>>
>>
>>
>>> Benoit SCHWINDEN a �crit :
>>>
>>>> Benoit SCHWINDEN a �crit :
>>>>
>>>>
>>>>> Hello,
>>>>>
>>>>> I am trying to set up a print server using cups 1.2.0 and samba 
>>>>> 3.0.22.
>>>>>
>>>>> I managed to have my printer drivers (cups v6) automatically installed
>>>>> on my clients (winXP sp2), but when I try to see the properties of my
>>>>> printer, Windows tells me that it cannot find any driver. I can print,
>>>>> but I can't edit the properties.
>>>>>
>>>>>
>>>>> Have you got an idea ?
>>>>
>>>>
>>>>
>>>>
>>>> I have a part of the solution :
>>>>
>>>> I've just used cupsaddsmb from cups 1.1.23, and I am now able to access
>>>> settings (recto/back, color, landscape...) of my printer.
>>>>
>>>> Best regards,
>>>>
>>>> BS.
>>>
>>>
>>> Hello,
>>>
>>> now, I can see options of my printer, but it doesn't want to do double
>>> side printing :( . I can set the double side option on my clients. If I
>>> print directly on the server, all works perfectly !
>>>
>>> What can be the problem : cups ? samba ? clients ? rights ?
>>>
>>> Greets,
>>>
>>> BS.
>>
>>
>>
> Hello,
> 
> on a old test server (debian 3.1, samba 3.0.22 and cups 1.1.23), 
> everything works fine ! color, landscape, double siding...
> 
> I will test today cups 1.1.23 on my other server (ubuntu 6.06).
> 
> best regards,
> 
> BS.

I've just tested a cups 1.1.23 on this machine : everything works 
perfectly !
So, I think that the problem is in cups 1.2.0, but where ? In 
configuration ? Are some acces rights not set ?

BS.




More information about the cups mailing list