Bug 6242 - Can't browse a printers server
Summary: Can't browse a printers server
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 3.3
Classification: Unclassified
Component: Client tools (show other bugs)
Version: 3.3.2
Hardware: All Linux
: P3 normal
Target Milestone: ---
Assignee: Guenther Deschner
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-02 07:52 UTC by Patrice Vetsel (dead mail address)
Modified: 2020-12-22 00:23 UTC (History)
0 users

See Also:

Attachments
wireshark log (8.28 KB, text/plain)
2009-04-03 06:37 UTC, Patrice Vetsel (dead mail address) 		no flags Details
wireshark log (8.28 KB, application/octet-stream)
2009-04-03 06:39 UTC, Patrice Vetsel (dead mail address) 		no flags Details
wireshark log under XP (22.37 KB, application/octet-stream)
2009-04-03 07:30 UTC, Patrice Vetsel (dead mail address) 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Patrice Vetsel (dead mail address) 2009-04-02 07:52:24 UTC 
My first bug was reported on system-config-printer, all informations are here :
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/330883

I use a printers server : Trendnet TE100-P21
http://www.trendnet.com/products/proddetail.asp?prod=145_TE100-P21&cat=46

All is ok under Windows XP clients, but I can not list shares on it under Ubuntu 9.04 using smbclient 3.3.2



kagou@kagou-laptop:~$ smbclient -L Ps-70f869
Enter kagou's password:

 Sharename Type Comment
 --------- ---- -------

 Server Comment
 --------- -------

 Workgroup Master
 --------- -------
kagou@kagou-laptop:~$


Or there are 2 printers shared, and shown under Windows XP
http://launchpadlibrarian.net/24662403/winbro.jpg
Comment 1 Guenther Deschner 2009-04-02 16:02:29 UTC 
Can you please upload a network trace with the (failed) attempt to see the printers using smbclient -L Ps-70f869 ?
Comment 2 Patrice Vetsel (dead mail address) 2009-04-02 21:10:05 UTC 
You mean using a sniffer ?
Comment 3 Patrice Vetsel (dead mail address) 2009-04-03 06:37:19 UTC 
Created attachment 4050 [details]
wireshark log

launch of wireshark
capture
launch : smbclien -L PS-70F869
end capture
save as (no change to type : tcpdump/...libpcap)
Comment 4 Patrice Vetsel (dead mail address) 2009-04-03 06:39:01 UTC 
Created attachment 4051 [details]
wireshark log

launch of wireshark
capture
launch : smbclien -L PS-70F869
end capture
save as (no change to type : tcpdump/...libpcap)

PS : repost attachment 'cause I'm not sure for Content type, set it to auto-detect
Comment 5 Guenther Deschner 2009-04-03 07:12:51 UTC 
Ok, thanks, can you also upload a trace of the working printbox browsing using a windows client ? That would allow to identify the issue quite fast.
Comment 6 Patrice Vetsel (dead mail address) 2009-04-03 07:29:20 UTC 
For informations : samba is installed ! (not by default)
If I remove samba I have this :
smbclient -L PS-70F869
Connection to PS-70F869 failed (Error NT_STATUS_BAD_NETWORK-NAME)
Comment 7 Patrice Vetsel (dead mail address) 2009-04-03 07:30:13 UTC 
Created attachment 4052 [details]
wireshark log under XP

Here is wireshark log from windows xp
Comment 8 Guenther Deschner 2009-04-03 07:54:12 UTC 
ok, thanks for the traces.

samba's clirap2.c LANMAN NetShareEnum is doing something wrong here. I can look for a fix later today.
Comment 9 Patrice Vetsel (dead mail address) 2009-04-05 08:45:35 UTC 
Great :) Thanks Guenther Deschner
Comment 10 Patrice Vetsel (dead mail address) 2009-04-27 08:10:07 UTC 
Confirmed under final Ubuntu 9.04
Comment 11 Derrell Lipman 2009-04-27 08:12:48 UTC 
corrected component
Comment 12 Patrice Vetsel (dead mail address) 2009-06-18 09:39:22 UTC 
@Derrell Lipman : which one ? where ? which version of samba correct this bug ?
Comment 13 Patrice Vetsel (dead mail address) 2009-06-18 09:43:25 UTC 
Oups, sorry Derrell forget this noise.
Comment 14 Björn Jacke 2020-12-22 00:23:22 UTC 
I expect this is fixed by now, If it still happens with 4.12 or later, please file a new bug for that.