Discussion Locked

File sharing using Samba

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm not the only one this exactly this kind of problem and, since nobody has the answer at this time, but I'll expose it very precisely, in an attempt to avoid stupid answers. And I dont want answers like "Don't use Windows", thank you.

We are running DOS application writtent with Clipper using DOSEMU on a LINUX server.

Some workstation use Telnet (either Linux and Windows workstations), and some are directly connected on a TCP-IP LAN and acces to the application and files using SAMBA.There is no problem at all with the Telnet clients (except for display and keyboard problems, but this is another story, men).

The problem is with the network clients through Samba. The files/records locking just seem not to work. Everyone can access to anything in write or exclusive mode simultaneously !!!

The software has been carefully designed to ensure correct sharing (and it's been working for years on Novell, Mircosoft, etc. networks) but of course all goes wrong with Samba allowing anybody to access to already locked records, such as several people creating an invoice with the same number at the same time and so on.

The effect is that the locking functions always return a success even if the file or record is already locked by another user.

This occurs only with Samba. Well the only solution we can see for now it putting everybody under Telnet, even users on the LAN, but all the Telnet emulators available for Windows display ugly with special IBM characters ! What's more, they can't send accented european characters, which makes documents very uneasy to read (that's the problem I evoked precedently)

Anyone having a solution about parameters to allow file sharing using Samba would be welcomed, but I'm beginning to suspect a bug that has yet to be fixed.

3 replies

by rush2112

Have you tried Attachmate for Windows?
Chameleon?
Omni VT-420?
Powerterm can be found at
http://www.c2000.com/products/csp_pterm.htm
A simple search on Google.com turned up many
hits for terminal emulation for windows and unix.

A second thought reminds me of some article
that I read that Samba recently had an update
I presume that you are running the most
current version?
http://de.samba.org/samba/whatsnew/samba-2.0.5a.html
(watch the word wr-
-ap)

You might also goto
http://lists.samba.org/pipermail/samba-announce/1999-July/000052.html
and read the section on OPLOCKS.
It sounded to me to be similar to your situation.

by z80man

Sorry I was so late to rate your answer, I really didn't know if it helped me or not ; the point was you responded in a sensible and helpul manner, not only replied by nonsenses as most people here do, so it was worth examining carefully.

As a result, no, i did not help correct my problem, but I'll close this question, because I found the right answer by myself.

For all those who'd be interested, the problem IS NOT WITH SAMBA. We even tested connecting the Windows workstation directlyto the Linux server using a NFS client, with the same results.

The problem is with Windows !!! It is even provided with the cure !!! I eventually searched for more information about the troubleshooting tag in system performance box, as there is no explanation at all about all those topics, even in Windows help. Baut the Windows Technical Resource Kit gives the answer !

The first topic, "Disable new file sharing and locking semantics", is the good one !!! In fact, it seems that Microsoft introduced a "new" (read "different") way of sharing file that is incompatible with any other know way. Checking this option is said to solve sharing problems with, for example, Novell Netware, and attracted my attention. So I checked the option, and - miracle ! - it worked ! The files were shared the normal way again !

Conclusion : Microsoft set up a new sharing system compatible only with Windows !!! Fortunately, it can be disabled and set back to normal. But will this feature be available in all future versions of Windows, that is the question now... Well, it is said to set up SoftCompatMode=0 in the Registry, so i guess it would be possible this way for some time.

This discussion is closed to new replies.