File Mangling Issues for Samba 2.2.1a-4

File Mangling Issues for Samba 2.2.1a-4

Post by Ding-Hou Le » Sat, 17 Nov 2001 03:21:51



    Hi,

    I'm running Samba 2.2.1a-4 on Redhat 7.2 (Kernel 2.4.7-10).  The version
of Samba is the package that comes with Redhat 7.2.

    Here is an example of the problems I'm seeing:

    I have a file called "Copy of template.txt" on the samba server and the
directory where it's located is mapped to my client computer as the W drive.
If I go to a Command Prompt under my Windows machines, including Windows
95/98, NT, and 2000, the truncated name of that file with long filename
(located in W:\) is displayed as COPYO~S7.TXT.  Howerver, if I copy that
same file to a location on my client computer (e.g. C:\), then the trucated
name becomes COPYOF~1.TXT, which is different.  If I change the filename to
"copy of template.txt", then it's displayed as "COPYO~RI.TXT" under W:\
while it's still displayed as "COPYOF~1.TXT" under C:\.

    For applications including Minitab and LView Pro 1.c/32 bit version
running under Windows 95 (and sometimes on Windows 98), the files would not
open if being double-clicked from Windows Explorer, even though  the
applications would launch.  Interestingly, same versions of the applications
running under Windows NT and 2000 do NOT have these problems.

    To sum up, clicking files (from Windows Explorer) of MS Office
applications (Word, Excel, etc) under Windows 95/98, NT, and 2000 would open
up the files without any problem.  However, clicking files of certain
applications from Windows Explorer on Windows 95 (and again, Windows 98 at
times) will NOT open the files successfully, even though the associated
applications are launched normally.  In addition, batch files with long file
names residing on the Samba server will NOT execute.

    Any ideas?  Is there any flag that will get around this issue?  Thank
you!

Ding

 
 
 

File Mangling Issues for Samba 2.2.1a-4

Post by Edward Forti » Sun, 18 Nov 2001 02:23:39


Try playing with the following switches that are set in your smb.conf file
under the [Global] section.  If they are not there, create them.

client code page = 850
mangled stack = 100
mangled char = ~

Ed Fortin


Quote:

>     Hi,

>     I'm running Samba 2.2.1a-4 on Redhat 7.2 (Kernel 2.4.7-10).  The
version
> of Samba is the package that comes with Redhat 7.2.

>     Here is an example of the problems I'm seeing:

>     I have a file called "Copy of template.txt" on the samba server and
the
> directory where it's located is mapped to my client computer as the W
drive.
> If I go to a Command Prompt under my Windows machines, including Windows
> 95/98, NT, and 2000, the truncated name of that file with long filename
> (located in W:\) is displayed as COPYO~S7.TXT.  Howerver, if I copy that
> same file to a location on my client computer (e.g. C:\), then the
trucated
> name becomes COPYOF~1.TXT, which is different.  If I change the filename
to
> "copy of template.txt", then it's displayed as "COPYO~RI.TXT" under W:\
> while it's still displayed as "COPYOF~1.TXT" under C:\.

>     For applications including Minitab and LView Pro 1.c/32 bit version
> running under Windows 95 (and sometimes on Windows 98), the files would
not
> open if being double-clicked from Windows Explorer, even though  the
> applications would launch.  Interestingly, same versions of the
applications
> running under Windows NT and 2000 do NOT have these problems.

>     To sum up, clicking files (from Windows Explorer) of MS Office
> applications (Word, Excel, etc) under Windows 95/98, NT, and 2000 would
open
> up the files without any problem.  However, clicking files of certain
> applications from Windows Explorer on Windows 95 (and again, Windows 98 at
> times) will NOT open the files successfully, even though the associated
> applications are launched normally.  In addition, batch files with long
file
> names residing on the Samba server will NOT execute.

>     Any ideas?  Is there any flag that will get around this issue?  Thank
> you!

> Ding


 
 
 

1. tons of oplock errors [RH 7.2 + Samba 2.2.1a-4]

I am trying to move files from a Windows 2000 Server to a Redhat Linux
7.2 server running Samba 2.2.1a-4.

My problem is that while copying, I get timeouts on the Windows 2000
machine, and if I cancel the transfer, my user's smbd PID hits 100%
CPU Utilization. Here's a snip of my user's log:

<snip>

[2002/02/12 02:41:22, 0] smbd/nttrans.c:call_nt_transact_ioctl(1798)
  call_nt_transact_ioctl: Currently not implemented.
[2002/02/12 02:49:34, 0] smbd/oplock.c:request_oplock_break(997)
  request_oplock_break: no response received to oplock break request
to pid 2664 on port 32786 for dev = 4808, inode = 262147
  for dev = 4808, inode = 262147, tv_sec = 3c68c8c7, tv_usec = 12ef5
[2002/02/12 02:50:06, 0] smbd/oplock.c:request_oplock_break(997)
  request_oplock_break: no response received to oplock break request
to pid 2664 on port 32786 for dev = 4808, inode = 262147
  for dev = 4808, inode = 262147, tv_sec = 3c68c8c7, tv_usec = 12ef5
[2002/02/12 02:50:38, 0] smbd/oplock.c:request_oplock_break(997)
  request_oplock_break: no response received to oplock break request
to pid 2664 on port 32786 for dev = 4808, inode = 262147
  for dev = 4808, inode = 262147, tv_sec = 3c68c8c7, tv_usec = 12ef5
[2002/02/12 02:50:52, 0] lib/util_sock.c:read_socket_data(478)
  read_socket_data: recv failure for 6028. Error = Interrupted system
call
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(356)
  process_local_message: Received unsolicited break reply - dumping
info.
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(371)
  process_local_message: unsolicited oplock break reply from pid 2669,
port 32786, dev = 4808, inode = 262147
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(356)
  process_local_message: Received unsolicited break reply - dumping
info.
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(371)
  process_local_message: unsolicited oplock break reply from pid 2669,
port 32786, dev = 4808, inode = 262147
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(356)
  process_local_message: Received unsolicited break reply - dumping
info.
[2002/02/12 02:50:52, 0] smbd/oplock.c:process_local_message(371)
  process_local_message: unsolicited oplock break reply from pid 2669,
port 32786, dev = 4808, inode = 262147

<snip>

Here's my PID:

2670 ndelong   14   0  1880 1880  1544 R    99.6  0.5   0:17 smbd

I've gone and grabbed the latest Redhat 7.2 rpm from samba.org, but it
barks at me about samba-common and samba-client mismatches (where can
I find the latest rpms for those? - the ones I found on rpmfind.net
are currently the ones I have installed, and are not 2.2.3a)

Anyway, my question is what should I be looking for? I have
TCP_NODELAY set, and so_sndbuf=8192 , so_rcvbuf=8192 ...

Any direction would be much appreciated.

Nate D.

2. no subdirectory pass - how to ??

3. Samba 2.2.1a Setup Issues

4. remote configuration

5. samba 2.2.1a, delete file when client pc crash/hang, please help!!!

6. Please help with Sequences and Triggers

7. Running bat files on Samba 2.2.1a

8. XP pro and MSN8 Dial up Problems

9. Samba 2.2.1a File Corruption?

10. Samba 2.2.1a -- Win2k -- File Ownership

11. Database speed issues on 2.2.1a ?!

12. win2k to samba 2.2.1a printing