Comment # 14 on bug 1040951 from Johannes Meixner

Samuel Cabrero,
I think in the past such a symbolic link hack was o.k.
but for the future it would be nice if things could
work right even somehow automatically.

Ideally there is only one CUPS backend 'smb' that internally
could find out automatically what the right way is so that
the user would not need to specify how printing via SMB
works on that system.

Perhaps something like "try it one way and if that is impossible
try it the other way"?

As far as I understand it with the current symbolic link hack
one cannot have some print queues on one same system that print
via SMB in the traditional way while some other print queues
can print in a Windows AD environment (e.g. think about a user
with a laptop who moves between traditional SMB environments
and Windows AD environments).

I don't know if that "either via traditional SMB or via Kerberos/AD"
is a restriction in practice and I am not a Samba user so that
I cannot make a founded comment here.