Bug 65800 - kio_smb can't access share
Summary: kio_smb can't access share
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Unmaintained
Component: smb (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-10 11:48 UTC by Gianfranco Liporace
Modified: 2004-07-27 10:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
tcpdump file (28.59 KB, application/octet-stream)
2003-10-10 16:07 UTC, Gianfranco Liporace 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Gianfranco Liporace 2003-10-10 11:48:00 UTC 
Version:            (using KDE KDE 3.1.4)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc 3.2.3 
OS:          Linux

When I type "smb:/", I get the list of all computer on the network.
Trying to access shares on computers located in subnets other than mine, using the NETBIOS name, I get this error:"Share could not be found on given server". I have no problem using the computer's ip address (e.g.: smb:/10.1.1.20/).
Comment 1 Stephan Kulow 2003-10-10 11:56:42 UTC 
what samba do you use?  
 
The NETBIOS name relies on broadcast, maybe your firewall filters them out?
Comment 2 Stephan Kulow 2003-10-10 11:58:30 UTC 
Can you provide a "tcpdump -w file" attachment? Perhaps your DNS is configured  
for different host names than NETBIOS? Or you use win95?
Comment 3 Gianfranco Liporace 2003-10-10 16:07:11 UTC 
Created attachment 2731 [details]
tcpdump file
Comment 4 Gianfranco Liporace 2003-10-10 16:10:04 UTC 
Hi,  
I've attached the file you requested. I've also tried to browse those computer 
with smbclient and Nautilus from Gnome using NETBIOS name with success.
Comment 5 Stephan Kulow 2004-02-22 20:19:37 UTC 
can you please try with KDE 3.2.0 and samba >= 3.0.1? There were quite some fixes since october. I can't find any 10.1.1.20 in your tcpdump, so I'm a bit puzzled