samba - Oct 1998 - Installing shared Windoze executables on a Samba share (fwd)

Hi,

I've got a Samba server here that runs great!  I've got an NT machine on
my laptop and I can interface with the Samba server directly in any way
I want, except for one thing:

When I try to install a program (Visio) as a network shared app, the
installation always tells me "I've determined that the target drive
doesn't support long file names" after I choose to install to the Samba
share.  This is obviously ubll, but how do I convince the install?

I've tried fiddling around with "mangled names", "preserve
case", "short
preserve case", etc. (I've read the manpage and looked in the
/usr/doc/examples directory for some clues ...)

Any ideas?  I notice that the Samba share has "Filesystem: Samba" when
I
look at its properties in Explorer ... do I need to change that?

--
Nathan Norman
MidcoNet  410 South Phillips Avenue  Sioux Falls, SD
mailto:finn@midco.net           http://www.midco.net
finger finn@home.midco.net for PGP Key: (0xA33B86E9)

Hi

I followed with big interest the discussion about oplock from th 1836
digest of the list.

I had too some problems with oplock_break, on samba-1.9.18pl10 too, with
Win95 only as clients too, but somehow different. 

Well, I have some supplemental details to provide:

First, the oplock errors appear in strictly determined circumstances: when
the 10/100Base-T Ethercard (3COM905B) gets unplugged from a line of 10Mb
and replugged on a 100Mb line. Otherwise, the same config functions
marvelously (but the server has to be connected through the 10Mb line).

Then, these are some hard facts: 
Server: RH Linux 5.1 with samba-1.9.18pl10
Clients: Win95 (all are 4.00.950B)
Server's ethercard: 3COM905B (and it seems a 3COM905A makes the same
	problems)
Server's ethercard driver: stock driver in the 2.0.35 kernel
Cabling: 100Mb twisted pairs (RJ-45 connectors)
Clients' ethercards: variety (3COM, SMC)


The error messages from the debugging smb.log are included below:

=============[snip]================1998/09/17 16:03:15 tconX service=profile
user=marc cnum=59
1998/09/17 16:03:15 Transaction 3 of length 60
switch message SMBunlink (pid 887)
chdir to /home/samba/profiles
reply_unlink : \MARC\PRO2003.TMP
unix_clean_name [./MARC/PRO2003.TMP]
1998/09/17 16:03:15 request_oplock_break: sending a oplock break message
to pid 882 on port 1144 for dev = 811, inode = 15d044
1998/09/17 16:03:33 request_oplock_break: no response received to oplock
break request to pid 882 on port 1144 for dev = 811, inode = 15d044
1998/09/17 16:03:33 request_oplock_break: broke oplock.
1998/09/17 16:03:33 request_oplock_break: sending a oplock break message
to pid 882 on port 1144 for dev = 811, inode = 15d044
1998/09/17 16:03:47 request_oplock_break: no response received to oplock
break request to pid 882 on port 1144 for dev = 811, inode = 15d044
1998/09/17 16:03:47 request_oplock_break: broke oplock.
1998/09/17 16:03:47 request_oplock_break: sending a oplock break message
to pid 882 on port 1144 for dev = 811, inode = 15d044
1998/09/17 16:04:01 Transaction 1 of length 158
==================[snip]==================
Lots of those. LOTS.

Any hint is GREATLY appreciated.

Cristian Tibirna           ::  ctibirna@gch.ulaval.ca
Net.Admin.; PhD Student    ::  WT: (1-418-) 656-2131/6224
GCH - U.Laval, QC, Canada  ::  HT: (1-418-) 658-2286

>we are pretty sure to have our Samba version 1.9.18p10 configured for
>running a logon.bat which mounts a SMB filesystem on Win95 client logon.
>Funnily enough we see the message "Win NT logon script: Executing logon
>script" but obviously this is not actually true, as the filesystem is
not
>mounted after this message box (a DOS box flashes up briefly as well)...
The DOS box you're seeing shows the batch file (logon.bat) as it's
executing. I wasn't sure from your message, but it sounds as if
your NET USE isn't working. If not, can you run it from the
command line (DOS prompt) on the Win 95 client? If there's an
error, what is it?

Daryl
Daryl Biberdorf		darylb@superserve.com

Visio's install program use the GetVolumnInformation() API  to check for
long filename support.  The docs say that if the value 255 is returned, then
the (FAT/NTFS) file system supports long filenames.  For various reasons, it
actually checks for this return value to be >= 240 in order for there to be
long filename support.

Samba has a hard-coded return value of 128 (see trans2.c, somewhere around
line 1100), thus the failure.  I suppose you could change this value to 240
and recompile Samba, but I really wouldn't recommend that since it would
probably cause other catastrophic problems.

...Craig...

(Opinions expressed are my own.)

		-----Original Message-----
		From:	Nathan E Norman [mailto:finn@midco.net]
		Sent:	Wednesday, October 07, 1998 6:48 PM
		To:	Multiple recipients of list
		Subject:	Installing shared Windoze executables on a
Samba share (fwd)

		Hi,

		I've got a Samba server here that runs great!  I've got an
NT machine on
		my laptop and I can interface with the Samba server directly
in any way
		I want, except for one thing:

		When I try to install a program (Visio) as a network shared
app, the
		installation always tells me "I've determined that the
target drive
		doesn't support long file names" after I choose to install
to the Samba
		share.  This is obviously ubll, but how do I convince the
install?

		I've tried fiddling around with "mangled names", "preserve
case", "short
		preserve case", etc. (I've read the manpage and looked in
the
		/usr/doc/examples directory for some clues ...)

		Any ideas?  I notice that the Samba share has "Filesystem:
Samba" when I
		look at its properties in Explorer ... do I need to change
that?

		--
		Nathan Norman
		MidcoNet  410 South Phillips Avenue  Sioux Falls, SD
		mailto:finn@midco.net           http://www.midco.net
		finger finn@home.midco.net for PGP Key: (0xA33B86E9)

samba goes through the trouble of converting the IP numbers x.y.z.a into
names.You can use 'nslookup' command on LINUX (not available on
win95/98)
wherein you can type in the name and it will give you the IP address.
Then go to any of the win95/98 machines and do your nbstat command.
If the netbios name you get is DIFFERENT from the %m portion of the
log file (log.%m) then you have a serious problem.
If they match, then you found your answer to your question below in
'nslookup'.

> Subject: Resolving from ip to get a netbeui name ???
> I am very interested in resolving from ip to netbeui as you can do with
> nbtstat from a 95 box:
> nbtstat -A xxx.xxx.xxx.xxx  (when it works)
> will return the netbeui name of the box with that ip.
>
> Since something similar is happening since the log.%m stores the machine
> name can you get this info out of samba from the command line??????
>