samba - Nov 1997 - problem with self-extracting exefiles on samba-drive (again)

Hello,

Some weeks ago I posted this problem we have with samba.
( There were some people with the same problem..)
I also posted it to samba-bugs, but no reaction yet.
The problem doesn't occure on an NTFS file-system.
Can someone from the samba-team can look into this problem??

Here is the problem ....

We are running samba on SGI/SUN/HP file-servers.
We have about 600 concurrent clients.

We are using samba version 1.9.17p4 en have a problem with
self extracting exe-files on a samba-mounted disk from NT 4.0.
( This problem also exists with earlier versions of samba e.g. 1.9.16p11 )

If you place the exe-file in a directory called "12345678.123"
( 8.3 filename ), there is no problem.

If you place the exe-file in a directory called "123456789" ( long
filename),
you get a message window which says it couldn't locate the exe-file.

I reported this problem ( with a sample exe-file ) to samba-bugs.

Has anybody seen this before???
( I can send to sample exe-file again if needed ).

Our smb.conf file is as follows :

   workgroup = cos
   os level = 0
   preferred master = no
   remote announce = cos
   server string = hpomega
   browse list = no
   domain master = no
   wins support = no
   wins server = wins1
   guest account = ntguest
   security = server
   password server = ntfile4,ntprint1
   preserve case = yes
   short preserve case = no
   guest ok = no
   read only = no
   create mask = 640
   directory mask = 750
   debug level = 1
   socket options = TCP_NODELAY

   [homes]


Thanks...

Eddy Reniers
-- 
    Reniers, ing. C.M.E.             

    Philips Research Laboratories
    Building WY p 023, Prof. Holstlaan 4, 5656 AA Eindhoven, The Netherlands
    Phone: +31-40-2744327

    E-mail: reniers@natlab.research.philips.com

On Tue, 25 Nov 1997 reniers@natlab.research.philips.com wrote:
> Here is the problem ....
> 
> We are running samba on SGI/SUN/HP file-servers.
> We have about 600 concurrent clients.
> 
> We are using samba version 1.9.17p4 en have a problem with
> self extracting exe-files on a samba-mounted disk from NT 4.0.
> ( This problem also exists with earlier versions of samba e.g. 1.9.16p11 )
> 
> If you place the exe-file in a directory called "12345678.123"
> ( 8.3 filename ), there is no problem.
> 
> If you place the exe-file in a directory called "123456789" (
long filename),
> you get a message window which says it couldn't locate the exe-file.
> 

Yes, it happens if you try run a 16 bit application (e.g. WinZIP
se-archive). Note, that it does *not* happen if I run *the same*
application from NT server. To test is very simple:

  create self-extracting archive e.g. with WinZIP (be shure to mark
  16 bit)

  rename archive to something like 123456789.exe

  try to start it from SAMBA - you get error message "123456789.exe not
  found"

  Now, copy *the same* archive to NT server and run it from there - runs
  perfectly. Note, that WinZIP gets mangled name - something like 
  123456~1.exe

Most probably, there *is* a difference in API calls between 32 and 16 bit
programs, which are not taken into account by SAMBA. Working on WinNT 4.0
I could not force SAMBA (1.9.18alpha11) to mangle names at all - in
spite of *all* mangling parameters set to yes. 

Note, that the same problem applies to directories as well - currently I
am forced to name all directories on SAMBA in 8.3 format, because LFNs
make installations of 16 bit programs fail (the same names on NT work
fine). Not very handy.

-------------------------------------------------------------------------
Andrej Borsenkow 		Fax:   +7 (095) 252 01 05
SNI ITS Moscow			Tel:   +7 (095) 252 13 88

NERV:  borsenkow.msk		E-Mail: borsenkow.msk@sni.de
-------------------------------------------------------------------------

> If you place the exe-file in a directory called "12345678.123"
> ( 8.3 filename ), there is no problem.
>
> If you place the exe-file in a directory called "123456789" (
long filename),
> you get a message window which says it couldn't locate the exe-file.
This is a known bug with NT4.x and long directory names with
a 16 bit executable. NT behaves the same way if you try to
run the binaries from a Win95 server in a long directory name.

However, I believe the problem is related to the fact
that Samba does not support NT-specific SMB calls. When
we add these (on the to-do list) this should be fixed 
with Samba (I'll announce it in the WHATSNEW when it's
done :-).

In the meantime you could add a short name symbolic link to
the long directory name and execute the 16 bit self extracting
files from there.

Hope this helps,

	Jeremy Allison,
	Samba Team.

-- 
--------------------------------------------------------
Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.
--------------------------------------------------------