similar to: DOS MS client + slow response

Hello, I finally found a solution to allow basic MS DOS client 3.0 redirector to work with Samba. I'm sure you'll find it ugly, but it works. Under CORE protocol, the $"#&^ MS client sends unencrypted passwords to the samba server (maybe there is no support of encryption in CORE, I don't know). So as my clients are either W95, WfW, NT or DOS machines, I simply remove the

Hello, As I mentionned in a previous mail, I cannot connect to Samba 1.9.18p7 using a basic dos redirector and security set to user. I works with share security level or with the full dos redirector which takes 90 k more precious memory ... I got a answer telling me that the dos basic redirector is a piece of ... because it always encrypt the password, even if instructed to use plain text ...

> It turns out that the MS Network Client for DOS Basic Redirector _always_ > sends a 24 byte password. So, I guessed at encryption, got 'libdes', > recompiled my smbd (again), found a 'spare' Silicon Graphics server and > installed Encryption on it. (ENCRYPTION.txt is very good). Yep, good guess. All encrypted passwords in SMB are 24 bytes long. The "basic

Samba Gurus. We run W95 and NT4 clients in a mixed environment of Netware and Samba on SGs. Netware is the primary network login(over IPX/SPX). Am using clear text passwords for the Samba network. NT 4 is patched up to SR 3. Samba version 1.9.18p7. Problem. Samba performance from NT 4 machines is VERY slow. Many orders of magnitude slower than W95 which is very good. This performance

We recently committed to replacing our Netware server with a Samba server running on an old SPARC box (using RedHat 6.0). This seemed like a good idea at the time, but now I'm wondering... We have two labs of PCs (each of 16 machines, all running Windows 95) and we use PC-Rdist to ensure that the hard disk images on the PCs are kept fairly clean and up-to-date. The master disk images are

Hi to all, I'm currently experimenting with implementing a samba server on an SGI o2 running irix 6.5.3. The reason for this is that i am trying to shed some load off a netware server currently serving files to 2 workgroups containing 40 people. One group is a Survey section that has 1.5 gig of Civil engineering and Autocad data - this data tends to be of a dynamic nature. I would like

Subject: Wildcard '*.' matches inproper files (for SAMBA DOS clients) The problem does not appear when using W9x/NT clients. Testing environment: samba: 1.9.18p10i (compiled), 2.0.5a(binary distrib), 2.0.6(compiled) on Linux RedHat 6.0 and Solaris 2.5 smb.conf: | |[global] | workgroup = WORKG | server string = Samba %v | encrypt passwords = Yes | socket

HALLO, HOW IT IS POSSIBLE TO ACCESS FROM A DOS-BOOTDISK (VER.7.0) RUNNING ON A WINDOWS95-MACHINE TO A SAMBA-SERVER (WITHOUT STARTING WINDOWS). IF WIN95 IS RUNNING THE CONNECTION WITH THE SAMBA- NETWORK SERVER IS OK. (MS-NETWARE CLIENT AND TCP/IP) WHICH PARTS OF DRIVER, MANAGER, CLIENTS, PROTOCOLS ARE TO INSTALL ON THE MACHINE AN ON THE BOOTDISK? THANKS, PETER Mail: p_w@aon.at

Try adding "server max protocol = nt1" in the [global] section? On Mon, Dec 24, 2018 at 1:59 PM Steven Hirsch via samba < samba at lists.samba.org> wrote: > Hi, all. > > I know this is ancient history, but I have a couple of DOS machines that > host older device programming hardware. I've been able to access an older > version of Samba for years without

Hi, I'm running Samba as a glorified NAS at the moment - to begin with, I have an ext3 storage partition, /storage. In this is a directory, /storage/Personal, which has its own Samba share (also Personal). At this point, dos attributes using filesystem xattrs work beautifully. The problem comes when I start to fiddle further... I have a Novell NetWare filesystem (ncpmount) mounted at

We have just upgraded from Samba 1.9.18p7 to 2.0.6. We are now encountering this problem with 2.0.6 which was discussed back in 1998. We never had the problem with 1.9.18p7. We haven't changed the smb.conf as we are just using Samba in basic fileserver mode. Is there a change we need to make to get rid of this message and restriction occuring? Andrew 1998 Discusion: >I have a

Beating head on desk again! I have a samba server is running winbind which can access domain. It is working fine and is using domain credentials. I access the samba shares after the user has authenticated against a novell server during the novell logon script. The shares are authenticated with user domain credentials and verified with smbstatus. This works great! If I alternatively use windows

I am hoping someone else has found a solution for this: "A Delay Occurs When You Open a Mapped Network Drive on a Novell NetWare or UNIX NFS Server" This delay is usually 25sec for any mapped drive or network printer when accessed the first time since timeout. Painful for users who need novell and samba shares. (Windows XP sp2, exists on Novell clients 4.9 sp1a, sp1b, sp2, &

I found these articles that talk about the oplock_break problem (specifically they are related to problems with word97): http://support.microsoft.com/support/ntserver/serviceware/nts40/e9msge2bc.asp http://support.microsoft.com/support/kb/articles/q163/5/25.asp Basically they say: either apply sp3 on the winnt client or disable oplock on nt server But they don't say anything about win9x,

On Mon, 24 Dec 2018, Luke Barone via samba wrote: Thanks, Luke. Unfortunately that makes no difference. Still getting: Error 5: Access has been denied at the MS_DOS console. > Try adding "server max protocol = nt1" in the [global] section? > > On Mon, Dec 24, 2018 at 1:59 PM Steven Hirsch via samba < > samba at lists.samba.org> wrote: > >> Hi, all.

Hello, I have a 120 PC netwaork at work and I'm using samba 1.9.17p4 on a linux 2.0.32. Previously, I was using Netware 4.10 and I plan to replace it step by step by Linux/Samba (I have Unix and W95 clients). All samba shares either on a local or on a remote machine are working perfectly fine. But I also have some share on some directories exported by the netware server (in NFS mode,of

Hi, all. I know this is ancient history, but I have a couple of DOS machines that host older device programming hardware. I've been able to access an older version of Samba for years without incident. Last weekend I upgraded my server to Ubuntu 18.04, which provides Samba 4.7.6. Unfortunately, after hours of frustration I find I'm unable to connect from any of the older machines.

Hello, I am wordering how Samba treats the user/account name of a logged in W95 and/or W9x Client? I have the following problem: We want to switch our file- and printer services from netware to samba 2.2.5. The client need also to connect to a netwarebased oracle db 7.x. When I log in to Samba as PDC with capital letters in the username box I am able to use the Software System which is based

Hello Jeremy, > OH - that's *really* interesting ! I wonder how it is > changing the SMB3+ redirector to do this ? It looks like applications could do something and give a hint to SMB3+ redirector, so far not quite sure how to make it, per process monitor (procmon) could show that write I/O size seems could be pass from the application layers,

CentOS Errata and Enhancement Advisory 2010:0460 Upstream details at : https://rhn.redhat.com/errata/RHEA-2010-0460.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: c268c72e77eb82acd082eed5b1ccf341 kmod-spice-usb-redirector-4.5-2.el5_5.x86_64.rpm 2d7522f13423c046574e79f47b3fdf2f