similar to: Windows losing EnablePlainTextPassword settings after reboot

Installed v205 for Solaris8, and successfully exec'd tests 1-7 -- but failed 8-10 -- in //doc/docs/textdocs/DIAGNOSIS.txt. Errors... TEST 8 "System error 5 has occured. Access is denied." TESTS 9 & 10 "The account is not authorized to log in from this station." I recall from a previous life that the solution is to modify a registry key (EnablePlainTextPassword or

PAM Unable to dlopen /usr/lib64/sercurity/pam.winbind.so:version SAMBA_4.8.3 not found (required by usr/lib64/security//pam.winbind.so. I cannot authenticate AD users and the error above appears in the logs. I may could have corrupted this when I was trying to resolve my issues with UIDs. Is there a way I can recompile or re-download these packages?

Does anyone Know the procedure for Windows 2000 workstation, in order to not encrypt passwords. What I needed is something similar to the transcription I make below that works for windows nt4 and 98. Thank's Emanuel Duarte (Portugal) ********************************** This should take care of the "clear text password" problemsyou've encountered: For Win 98 (To enable

Hello All: I would love to RTFM on multiple ADS servers being configured for ADS sercurity, but I can't find anything. Specifically: I have 2 ADS servers at 1 site. I have 4 SAMBA file servers at said site. If ADS server 1 goes down -- It will not cascade to ADS Server 2. How can I set that up? I have seen when using "security = server" multiple server names listed, but have

Hello I have 4 NT server : so 4 NT Domain and 1 Linux Box with samba 1.9.18p4-50.4 in smb.conf, I configure netbios aliases = TEST1 TEST2 TEST3 TEST4 sercurity = server include = /etc/samba/server.%L ... and in /etc/samba/server.TEST1 password server = NTSERV1 and in /etc/samba/server.TEST2 password server = NTSERV2 but when I read the nmbd and smbd logs , %L is replaced by a null string

About 3 month ago, I installed samba on a university linux box. I edited the smb.conf so that filesharing worked for me from a Windows NT 4 workstation. The problem is that it doesnt work anymore, maybe because of service pack 3? I dont know. I get this messages when I try to access my home-directory from the NT workstation: translated from danish, offcourse: "no authority to log on from

I'm trying to set up a samba server, such that 60 or so win 98 users can log into the linux box and be plopped into their respective home directories on it. I don't want them to be promted for passwords, I want the PDC, an NT box, to take care that in such a wy that I do not need a smbpasswd file. I know almost nothing about NT, but the server running works just fine, and will let people

We are using SAMBA 2.2.4 to support a large community of Windows users. The latest deployment of PC's come with Windows XP, and we need to disable Password Encryption on those to use SAMBA. We need help in locating the "EnablePlainTextPassword" key. Thanks in advance Jaime A Cifuentes

we are using samba Version 1.9.18p8 and want to connect WIN-NT 3.5.1 to Samba- supportet Unix-Drives; but for any reason the password for this connection is always needed (we did the registry for enableplaintextpassword); the same connection is done well on WIN95 could you figure out, what our problem is??? thank you Klaus-Dieter Wurm (dieter.wurm@de.origini-it.com)

Hello, I'm a new subscriber and hope I don't break any rules. We have just bought some new PC's pre-installed with Windows 2000. On our previous installations (NT and 95/98) we applied the EnablePlainTextPassword registry patch to allow our PCs to communicate with our Unix server and other systems - no problem. Is there a similar patch for Windows 2000? We can't communicate,

After I have upgraded from previous version to 2.0, I don't manage to authenticate from clients (winnt4) to DigitalUnix3.2c with Samba anymore. Before the upgrade it worked fine. After the upgrade, my password is rejected. It's really a authentication problem because it works fine if I add "guest ok = yes". On the server I have: security = share On the client:

Hi Rowland, Thanks for the quick response. My response is inline below... On 02/19/2016 06:32 PM, Rowland penny wrote: > What are you feelings on using the command line ? > You could always open a terminal on the Samba 4 DC, enter: > > ldbedit -e nano -H /usr/local/samba/private/sam.ldb > > press enter > > press Ctrl+w > type 'dn: cn=domain users' > then

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

Hello, I've got a problem. I've installed on a SuSE Linux 7.0 the Samba version 2.2.4. Now if i trie to join the domain with a win2k pc I get an error message back saying that the username and/or password I supplied does not match the ones Samba has got. On the win2k machine I have set the registry entry "enableplaintextpassword" and also in the smb.conf file I have set "nt

Hello, I have a configuration issue that I cannot seem to fix. Running Samba 2.2.2 on Sun Solaris servers using NIS Scenario: I have 5 different samba servers that I map permanent drives to in Windows 2000. When I boot 2000 I get a login for my username and password then it starts to automatically map the samba drives. I am then prompted for a username and password for each separate samba

Hi, We are using samba 2.2.8.1 on Unix 4.3.3.0 and getting this error. We have both win 2000 and XP. I get this error on XP. Never had the problem on Win98 and previous versions. An error occurred while reconnecting O: to \\dev\growrg Microsoft Windows Network : The local device name is already in use. The connection has not been restored. We can fix the problem by removing all mapped

I'm writing because I had a problem with Samba, while installing it on some of our computers with Windows 98 (beta 3). We have an internal network not accessible from the outside, in which we use the sending in the clear (I.E. not encrypted) of the access passwords to Samba running on a Sun machine with Unix Solaris OS. We use unencrypted passwords because Windows 95 doesn't support

Hallo Liste Derzeit mache ich meine ersten Gehversuche mit Linux (SuSE). Bis jetzt habe ich in einem kleinen Netzwerk f?r meine Tauchschule vier Rechner betreut. Einer davon war WinNT-4.0 Server und Arbeitsplatz zugleich. Nachdem ich nicht mehr bereit bin, mich mit dem w?chentlichen "blue screen" und dem monatlichen Neuinstallieren von NT abzufinden, bin ich derzeit beim Umsteigen auf

Problem: -------- On the client mascines I get the msg: "The account is not authorized to log in from this station." This has bugged me for days now, so I am posting this sloution around varius places on the net... Analysis: --------- from a round of analysis by Jamz Boman B.Sc (Jamz@Boman.com), Toby Corkindale (tjcorkin@steadycom.com.au) Andreja Zivkovic (zivkotech@ozemail.com.au) at

I've looke throught the archives and can't find much to help my situation. I have a Slackware 10 server running Samba 3.0.4 on a Win2k/2K3 Active Directory Domain. My win2k clients can connect to the samba shares but the WinXP clients cannot. I've tried the enableplaintextpassword hreg hack but that doesn't solve the issue. Here is my [global] section of my smb.conf Can anyone