The Samba-Bugzilla – Bug 871
renaming files from OS/2 client failures
Last modified: 2005-04-18 17:56:16 UTC
Running Samba server 3.0.0 and/or 3.0.1rc1 on Red Hat 8.0. Seems to work well
with Windows XP clients (haven't tested earlier Windows versions much yet), but
has lots of problems with OS/2 clients.
I can use "net use" to map a drive letter to a Samba share, but when trying to
rename files on the command line, it gives a SYS0072 error (service has been
paused???), but works correctly.
Using the OS/2 SMB Tracing Tool, we see things like this:
Understands long file names, Errors in NT status format,
Unknown secondary SMB flags: 0x18433
I have tried "nt status support = no" but it didn't change anything. The
protocol negotiation seems to come up with LM1.2X002, which I suppose is what
Samba calls LANMAN2.
Created attachment 311 [details]
Log file that shows the rename of "misc" directory to "m"
should be fixed in svn. please try the next release, which will be made
available (post 3.0.5pre1).
Problem still present in 3.0.5 RC1.
one more time. please retest 3.0.11 and reopen if necessary.
Error message is now "SYS0064: The specified network name is no longer available."
Seems to be fixed in 3.0.14pre1 from SVN 24.03.2005 (6031)
Sounds promising! Does NOT work in 3.0.13.
Working here with Samba 3.0.14a release built from SRPM.