similar to: Microsoft Windows Network: The local device name is already in use.

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

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, We have been experiencing problems where workstations (Win2K SP3, latest updates) have their registry setting for EnablePlainTextPassword set to 0 after reboot. We have Samba 2.27 and a pilot of Samba 3.0 Could it be one of MSs sercurity updates ? Has anyone seen this before ? Any input would be welcome ! Thanks, Laurent Biron Motorola.

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

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

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

I have a question about Win98 and Samba. Is there a registry fix similar to the WinNT plaintext passwd that needs to be performed? Win95, and WinNT can see Linux via Netbios, but the same machine, running Win98 cannot see the Linux box. I am running the most current version of Samba. The WinNT box can see the 98 machine fine. Does anyone have any experience with this? Please let me know if

hello! thanks for your link, i already tried with this documentation but it does not work, do you have any other ideas? gianluca -----Urspr?ngliche Nachricht----- Von: =?X-UNKNOWN?Q?Marcos_Jos=E9_de_Barros_Silva_-__#19000000000?= =?X-UNKNOWN?Q?000#_?= [mailto:byteunix@unicamp.br] Gesendet: Freitag, 28. Juni 2002 15:01 An: Gianluca Urbano Betreff: Re: [Samba] Join the Samba-Domain with win2k pc

Hi Rowland sorry for not being clear. In my first post I already wrote: Now I have to tight security with setting those flags in the windows client: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] EnablePlainTextPassword=0 EnableSecuritySignature=1 RequireSecuritySignature=1 . . . when I change registry to RequireSecuritySignature=0, everything works like

Dear all, I recently upgraded to Samba 2.0.3 and read the doc files about NT machines because I cannot connect to the Samba server. In the WinNT.txt file there is the following proposal: [ --- Start of pasted text --- ] The following registry entry change will re-enable clear text password handling: Run regedt32.exe and locate the hive key entry:

I'm just about to give up in despair of getting Samba working on my network. I've browsed through several books, HOWTOs and websites and still can't figure out what I'm doing wrong. Before I quit, could someone double check this and maybe spot what I've missed? First, let me describe my network. Names and IP addresses have been changed to protect the innocent. :-)

Hello I have an samba server with a public share. It was configured with security=share. Now I have to tight security with setting those flags in the windows client: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters] EnablePlainTextPassword=0 EnableSecuritySignature=1 RequireSecuritySignature=1 Since this change the public share is not working anymore. I found