Bug 80833 - Cannot access files on NetApp Filer CIFS/SMB share
Summary: Cannot access files on NetApp Filer CIFS/SMB share
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kio
Classification: Unmaintained
Component: smb (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-03 12:19 UTC by Sven Hergenhahn
Modified: 2013-08-18 23:20 UTC (History)
0 users

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


Attachments
tcpdump (317 bytes, application/octet-stream)
2004-05-17 17:23 UTC, Sven Hergenhahn
Details
full dump this time :-) (3.19 KB, application/octet-stream)
2004-05-18 09:41 UTC, Sven Hergenhahn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Hergenhahn 2004-05-03 12:19:13 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    RedHat RPMs
OS:          Linux

- Browsing NetApp Filer shares works fine, I can also see the files there, but opening, copying, downloading files does not work.

Error message in Konqueror (e.g. when trying to copy the file to my desktop) is:
"Could not read smb://server/share/folder/test.txt"

- I can easily access the file via smbclient

- I have no problem to open this same file on a Windows share

- The NetApp Filer's OS is: Ontap 6.3.2
Comment 1 Stephan Kulow 2004-05-08 18:45:59 UTC
what's your samba version?
Comment 2 Sven Hergenhahn 2004-05-10 09:12:49 UTC
samba-3.0.2-7.FC1
Comment 3 Stephan Kulow 2004-05-13 08:40:17 UTC
3.0.2 got some very weired regressions. Any chance you can update to 3.0.4?
Otherwise I would need some tcpdump

Comment 4 Sven Hergenhahn 2004-05-17 17:23:43 UTC
Created attachment 6041 [details]
tcpdump

It's samba-[common|client]-3.0.4-2 now. Same problem.
smbdump is attached.

Thanks,
Sven
Comment 5 Stephan Kulow 2004-05-17 20:56:08 UTC
the tcpdump is only the end and the server says indeed "directory not found"
Comment 6 Sven Hergenhahn 2004-05-18 09:41:08 UTC
Created attachment 6045 [details]
full dump this time :-)

Yes, although I can see the directory and browse into it. Only when trying to
get files, it doesn't work.

Full dump is attached.

Thanks,
Sven
Comment 7 Stephan Kulow 2004-05-18 13:41:55 UTC
I'm not sure I understand the dump ;(

You request folder\ic_counter.zip and there it says Directory not found.
Is the file named that way? Or is in a directory folder?
Comment 8 Sven Hergenhahn 2004-05-18 15:31:02 UTC
the directory is called folder, the file is called ic_counter.zip
Comment 9 Sven Hergenhahn 2004-07-07 16:38:06 UTC
Hi Stephan - any news on this?

Thanks,
Sven
Comment 10 Sven Hergenhahn 2005-05-18 08:47:06 UTC
Hi Stephan,

this is similar to the bug #103212 AFAIR, this did not happen with 3.3, but is now again a problem.

I can browse into open shares ((Everybody), but the can't get any files there(i.e. I can see them but neither open nor copy them)

On shares that require authentication, I have the exact same problem as reported in #103212

Cheers,
Sven
Comment 11 Christoph Biardzki 2005-05-23 12:48:21 UTC
Hi,

I had a case opened with Netapp regarding this issue. Netapp says Konqueror does not use "leading slashes" in filenames - something that works (erroneously) on Windows but not on filers which stick to CIFS. Filers do not accept these packets. Netapp has bug #77896 opened on this issue - but the problem is in KDE. Their suggestion was to change Konquerors behaviour to include these  "leading slashes".

Cheers,
  Christoph


Comment 12 Christoph Biardzki 2005-05-23 13:43:59 UTC
Some additional info from Netapp's bug description:

During the handling of path-based CIFS requests, Data ONTAP currently
 expects and checks for a leading backlash in the file/pathname. It will
 return the error 'Directory not found' if the leading backlash is missing.
 This behavior is not consistent with Windows.

 All Microsoft clients send the initial "\", but certain non-Microsoft
 CIFS clients sometimes send paths without it.
Comment 13 Dawit Alemayehu 2013-08-18 23:20:00 UTC
KDE 3 is no longer maintained. Feel free to reopen the ticket if the problem is still applicable in the current stable KDE 4 version. Thank you for your report.