Do the following at a client:
- right click at a printer, choose "Pause Prining"
- the printer will be disabled at UNIX, but the context menu will be leaved
- there is now chance to enable the printer from client.
I did not found the place in the source code where samba looks for the printer
state to keep the client informed. When you give me a hint which function tries
to detect the printer status I can try to fix it.
The bug exists as long as I know Samba. In the past I had a own shell script
which disables a enabled printer and enables a disabled printer. Then I sent a
message by smbclient in this script. But on XP SP2 the messanger is disabled by
default and so I hav no chance to send a response.
I found a solution with a configuration change. With option
lpq command = lpstat -o%p -p%p
it seems to work in generally. Two minor problems:
- After the procedure descripted to reproduce the problem a new printer without
- The printer on windows is updated after hit <F5> button, not automatically.
My test system is very slow. it could be that I run in a time out. But I don't
believe it because the reaction on <F5> needs less then a second.
what client are you using for testing (OS and service pack) ?
The automatic notify works fine here.
I've been over this some. The change notify works fine locally.
It should probably be noted that WinXP SP2 completely broke
MS's print change notify functionality. EVen Windows to Windows.
Not much I've found that we can do about that currently.