similar to: security = server & encrypted passwords

On Fri, 22 Oct 1999 22:33:37 +1000, samba@samba.org wrote: >Hi, > >I have problems with samba 2.0.5a amd my 3com 3c905b in 100 mbit mode: >writing performance: about 7,5 MB/s (ide hdd !!) That's pretty high! Seems you're using a switch. I just get 3,5 MB/s in both directions using 905b NIC's and a hub, +-100kb, usually reading is slightly higher than writing. (my clients

Hello! I need help (but who doesn's huh? :-) ) I meant to run one program - Money2000 (no, it is _not_ program from Microsoft) together with samba on linux, but i have problems with oplocks. This program is installed locally on win9x/NT and shares its databases. We tried to place databases on novell, on NT server and on win95 acting as server and everything worked fine. But when we tried

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,

Hi, I am running Samba 2.0.3 on Linux Kernel 2.2.5 (SuSE 6.1) in a test environment with a Win NT server (PDC), the Linux box taking over step by step the file- and printserver tasks, and Win 95 clients. Samba is setup with security=domain at this stage. It just happened again what I have seen only a few times before. When I use Outlook 98 on the Win95 machine and want to access the

Hello, I'm new to Samba so sorry for this trivial question. I've configured my smb.conf with all the shares and enabled WINS support. I wanted to know what do I have to configure in my windows 95 machine. My LAN setup is - one Linux Red Hat 6.0 machine Pentium 166 and a windows 95 machine a 486. I've made my Linux m/c the proxy server using Squid. Also whenever I boot my Win m/c it

On Fri, 09 Jul 1999 14:07:10 -0400, David Collier-Brown wrote: >Johann Zuschlag wrote: >> Well, it's just a database residing on a file server. So it will only use smb. >> It's no intelligent database server like an SQL-server. But still, searching >> (with and without index) should be faster. With caching it runs really fast, but >> that is not save and would

On Fri, 20 Aug 1999 01:35:15 +1000, Patrick Joeckel wrote: >I recently set up the Samba Server Version 2.0.5a on a SuSE-Linux 6.0 PC >(Kernel 2.0.36). > >Whenever I try to reach the shares on this machine from Windows 95 or >Windows NT machines (with different user-names) in our Network, >by double-clicking on the servername in the 'networkneighbourhood', >I am

A while back, Wayne Fool wrote: > I am confused about this password issue, I have samba 2.0.5a > running on a 486/dx2/66 as a print server for 3 computers, one is a > win 95b and the other is a win 95 (pre b), the other is a dos > computer (but that is another story, I'll tackle that one later). > > My network administrator says I must use encrypted passwords so I >

I can run OS/2 Warp 4 (no fixpak) as guest in native QEMU (non kqemu). I can also run OS/2 Warp 4 in a domu guest in XEN 3.1 on a Ubuntu 7.04 (Feisty) host. A stripped down eComStation will also work in native QEMU but it will not run in XEN 3.1. When trying to run eComStation in XEN, at boot it will lockup immediately (at boot blob). Any ideas or fixes that might help? thanks

My LAN is running Samba v1.9.18p10 under RedHat Linux v5.2. Using the SMB services are Win95 and OS/2 clients. It's all running fine. I will soon be adding Win98, though, and I understand that there is a question of password encryption. I'm concerned how the encrypted/plain-text communication of password will affect my existing configuration. If I reconfigure Samba to use encrypted

First of all, let me say "I know it's been fixed in Samba 3." That's for those of you who think I'm talking about the requiresignorseal registry hack in Windows XP. I'm not. I ran into an issue when using Windows 95 clients with a Windows 2003 server. (Why not Samba? The customer needs terminal services for some windows-only programs.) Because Windows 2003, by policy,

I have an old Samba network that uses unencrypted passwords. At the time, the posts were running win95. These days they are running win98 for the most part, but introducing new machines onto the network means fiddling with the EnablePlainTextPassword registry key. So currently, all the machines use plain-text passwords. I want to modify them all to use encrypted passwords. Naturally, I want to do

We are seeing some strange inter-subnet browsing issues here, our setup is as follows: .129 subnet [ samba box ] | | [ router ] ^ _.1 subnet _/ \_ .9 subnet_ The .129 subnet contains only the samba server configured to the letter from the browsing.txt file. The .1 subnet conists of win98 and winME boxes all configured from DHCP to use the samba box for WINS lookups.

Is there a tool, either for Perl or C, that will add/change the NT and LM encrypted passwords in the smbpasswd file? I know about the smbpasswd command, but I can't use that function from a script. I tried #!/bin/perl system("smbpasswd \< $oldpassword\n$newpassword\n$newpassword\n"); and some other things, but I couldn't get it to work. TSD

I have a mixed network of Win95, Win98 and Unix machines. I am using Samba very happily. I would like to add a Windows NT 4.0 and Windows 2000 client machine to the network, but don't know how to turn off the password encryption. I am currently editing the registry on the Win98 machines. If someone can tell me how to edit the NT 4.0 and Win2000 registry I would appreciate it. Thanks, Dan

Hi, I'm looking for some help to migrate from plain text to encrypted passwords. I'm using smbpasswd for authentication on a FreeBSD 4.9 server with samba 2.2.8. When we set up our server, we had Win95 clients with plain text passwords. As we introduced Win98 clients, we just kept with the plain text passwords. Now we are looking at XP clients and enctrypted passwords. My understanding

Hello, I'd be very grateful if anyone could share their ideas on this problem. The situation is this: I have a Solaris 8 machine running Samba 2.2.1a. The global configuration has "security = USER" and originally had "encrypt passwords = NO". I was able to map drives to shares on this machine from my WinNT 4 SP 5 workstation when I set the registry key advised by the

I am trying to use Samba 2.0.3 with encrypted passwords. I have everything set up according to the instructions in encryption.txt, and can authenticate into NT 4 Server shares with smbclient. I can also attach to my smb server using either smbclient or Win95. But NT4sp3 won't browse or connect. That I can connect to external NT shares would seem to indicate that samba is correctly sending

Hi, I have a network with a mix of Win95 and 98 machines (thus some use encrypted passwords by default and some don't. I already have all the users in a Unix password file therefore I'd like to use non encrypted passwords if I can and fall back on encrypted passwords if I don't have a choice (patched Win95 and Win98) because that requires people with encrypted password

I may be reading this wrong, but I'm trying to figure out why samba is sometimes trying to do a Unix password lookup to authenticate a samba connect. I have my samba passwords different than my Unix passwords. I'm using my own compiled version of Samba 1.9.18p10. I have an NT4 SP3 box and when I try to access a share through explorer on either of my two Linux boxes with encrypted