Bug 119280

Summary:	Unable to browse network using kword
Product:	[Unmaintained] kdeprint	Reporter:	Gerard Seibert <gerard.seibert>
Component:	general	Assignee:	KDEPrint Devel Mailinglist <kde-print-devel>
Status:	CLOSED NOT A BUG
Severity:	normal	CC:	jlayt
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	FreeBSD Ports
OS:	FreeBSD
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	This is the tcpdump file output I created

Description Gerard Seibert 2005-12-31 00:38:09 UTC

Version:            (using KDE KDE 3.4.3)
Installed from:    FreeBSD Ports
OS:                FreeBSD

I have three computers networked together. Two are WinXP machines and one is a FreeBSD 5.4 computer. Using Samba, I can browse both Windows machines, as well as print to the printer attached to the one Windows machine.

Inside KDE, I can print to, but not browse the Windows computers. I receive an error message when I attempt to do so.

Comment 1 Gerard Seibert 2005-12-31 00:44:04 UTC

Created attachment 14084 [details]
This is the tcpdump file output I created

Comment 2 Thiago Macieira 2005-12-31 00:56:26 UTC

What error message do you receive? And how is this a kword bug?

Comment 3 David Faure 2006-03-03 12:05:59 UTC

Must be a kdeprint (or underlying) issue. Details on the error message would be good though.

Comment 4 Kurt Pfeifle 2007-01-13 00:55:06 UTC

KDEPrint does not "browse" Windows shares or Windows shared printers.

If the Linux underlying print system (that is, most likely, CUPS) is configured to use and show these printers, KDEPrint works just fine for them. And likely this even works for the reporter....

He probably had problems to use the smb:// kio slave?

Closing bug now as INVALID.

Gerard,
feel free to re-open it -- but only with a very precise description what you expect to work, and how it doesn't work for you. If you do so, please name also the version of Samba you are using (or rather: libsmbclient). Have you tried it with KDE 3.5.5?

Cheers,
Kurt

Comment 5 John Layt 2008-12-31 19:26:57 UTC

Closing old Resolved status bug.