Opened 12 years ago
Closed 12 years ago
#201 closed defect (wontfix)
evfs client Incomplete directory listing
Reported by: | Neil Waldhauer | Owned by: | Silvan Scherrer |
---|---|---|---|
Priority: | Feedback Pending | Milestone: | Netdrive plugin 2.1.x |
Component: | Samba Client Plugin | Version: | Client 2.1.x |
Keywords: | Cc: |
Description
Using SAMBA client to connect to OS/2 Warp Server eBusiness. Connection is successful, and directory and files are listed. But when I go to a larger directory with 410 files, only 186 files are shown by Samba client.
I updated to ndpsmb-2_1_2-GA-20120315, but it's still the same.
In another directory with 2653 files, all 8.3 names, I get 197 files displayed. Possibly a directory listing has a maximum size?
Attachments (1)
Change History (12)
comment:1 by , 12 years ago
Version: | 3.0.34 → NDP 2.1.x |
---|
comment:2 by , 12 years ago
Thanks for the note, Herwig. I see all the files through LAN requester.
I tried SAMBA server one the new server, and I can see any number of files in a directory correctly with SAMBA client. I so far cannot connect at all with IBM FILE and print. I cannot tell if SAMBA is a workgroup or a domain, which is a significant difference for the IBM client.
My plan is to go forward with my SAMBA installation and retire my WSEB server. This will be my first server with only SAMBA, no IBM File and Print client.
I will retain the WSEB server for a while if it helps debug this problem. Also I have to port my Business software from WebSphere and Java 1.1 to Jetty and Java 6, so there is not much hurry on this issue.
comment:3 by , 12 years ago
Priority: | major → Feedback Pending |
---|
please get a debug output of the samba client. how to do that is written in the help file. at least then i see if the directory listing gets written to the client.
comment:4 by , 12 years ago
I have attached a log file that was created when I attached an eCS machine and did a directory listing of a file with 1184 files. Only 197 files showed up on the listing.
Both client and server are eCS 2.1.
comment:5 by , 12 years ago
Priority: | Feedback Pending → trivial |
---|
according to the log the lan server only send 197 files. something is really wrong here. but as a remote samba server list all, it's not a urgent problem. because and i'm afraid lan server is not really supported anymore.
but there is one strange thing in the log. when i have time i might look at it, but no promise.
comment:6 by , 12 years ago
ah and the samba client log is missing. it could tell some more insight. please provide that also.
comment:7 by , 12 years ago
the log provided is enough. http://svn.netlabs.org/samba/browser/branches/client-2.1/src/smbwrp.c line 1490 send the error, and the the listing ends. why the LAN server sends the same file 2 times is another question.
could you see if the dir listing works with sbmclient? if this also fails it's a lan server problem. if this works it's a client problem.
comment:8 by , 12 years ago
How can I test this with smbclient?
Too bad this is not supported. Here is the migration scenario. I have a machine that has SAMBA client and server. I cannot use TCPBEUI on it because I have SAMBA. How can I reach a LAN server machine. Is it possible to load old NETBEUI and not interfere with SAMBA?
comment:9 by , 12 years ago
Milestone: | → Netdrive plugin 2.1.x |
---|---|
Priority: | trivial → Feedback Pending |
see here for smbclient syntax. in short: log in to the lan server and do a directory listing. if all files are shown we need to fix our client.
comment:11 by , 12 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
it seems reporter lost interest so closing it.
Neil, I see the very same problem on a single directory BUT only if the Server is running WSEB or IBM Peer. The directory is cut off no matter if I access it using LAN Requester or Samba Client.
However, if the very same is shared by Samba Server, Samba Client is seeing the complete directory.
So, what happens if you access the directory using LAN Requester?