snip
I have already notified KDE of this as a bug:
http://bugs.kde.org/show_bug.cgi?id=57754
if you guys [and anyone else experiencing the problem] would follow the link and say "me too" or vote for fixing it, that might help.
In essence, it is related to the "[SLE] A [different] Telnet problem [SOLVED - but is there a bug?]" thread here earlier in April. For kprinter, what happens is a DNS call is made to resolve whatever is set in <ServerName> in . The DNS call arises because some system call outside of kde either does not provide a proper resolution or provides a resolution in a way which is not expected by KDE. Their man thinks he has a workaround in the kprinter code.
There is also a user workaround [untested] to have a DNS server on your network, but for networks like Marshall's and mine, that seems to be excessive. On the whole, I would like to run this issue to ground. It is either a direct library bug or a documentation bug, giving rise to the wrong expectations on the part of coders, I feel. Thus, even if kprinter has a workaround, we are going to see this in the next network thing, until it is fixed at source.
Thanks Vince. Man it looks like we might have to wait unit the KDE team can fix it. I will give you the "me too" vote later today. Oh well I hope that no one tries to use the phone while I try and print :) -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."