Re: [Samba] Linux Primary Domain Controller Authentication
Felipe Augusto van de Wiel wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cynthia Jeness escreveu: I have setup my Linux server as a Primary Domain Controller using Samba 3. All other computers on the network run various versions of Windows from 95 to XP. All computers are able to join my Samba domain and the user computers can log onto the network. However, if they try to access a file resource on one of the Windows 2003 file servers, the authentication fails with System Error 1789. With they you mean all computers? Or some particular version? AFAICT, Win95 does not have crypto passwords, which means that it is not going to work properly. Windows users computers (all versions 98, 2000, XP Pro) can access all shared resources on the Linux server. However, if one of these Windows user computers attempts to share a resource on the Windows 2003 File Server (which did successfully join the domain), then error 1789 is returned. Encryption is turned on and the passwords are stored on smbpasswd. The Windows 2003 file server did successfully join my domain.I am not running Winbindd primarily because it was not part of the Samba packaging provided by Suse. Is it necessary to run Winbindd in order to have the Windows 2003 servers validate? Looks like more a permission problem than a 2003 validation problem. The idea behind winbindd is share the user list between servers and, from your description, does not sounds like you need it, althoght there is not enough information to be sure. :-) Did you map users? Which version of Samba are you running? In which MS Windows versions the problem occurs? Any suggestions would be greatly appreciated. Hope it helps, kind regards. We added the users as regular users on the Linux computer and to the smbpasswd file. Except for Administrator which I did map to root, the user name on the Windows end user computer is the same as the user name on the Linux Samba Primary Domain Controller. We are using Samba version 3.0. The latest available from Suse. If I make the Windows 2003 computer a member of a workgroup and add the users directly to the Windows 2003 computer, then the users can access resources on the Windows 2003 file server. The error (1789) indicates that the Windows 2003 Server cannot verify the user name and password against the primary domain controller; i.e., the Linux box. As part of one of my Google searches, some news group responder indicated that Windbind was necessary to make this work. - -- Felipe Augusto van de Wiel [EMAIL PROTECTED] Coordenadoria de Tecnologia da Informação (CTI) - SEDU/PARANACIDADE http://www.paranacidade.org.br/ Phone: (+55 41 3350 3300) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFDb09qCj65ZxU4gPQRAop7AKCf9H9A1CYeiNmoe656Y52w8GV0FQCgmcbt 3SW8mNYe0tnZwKSAXw9gw1o= =KcOE -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Linux Primary Domain Controller Authentication
I have setup my Linux server as a Primary Domain Controller using Samba 3. All other computers on the network run various versions of Windows from 95 to XP. All computers are able to join my Samba domain and the user computers can log onto the network. However, if they try to access a file resource on one of the Windows 2003 file servers, the authentication fails with System Error 1789. The Windows 2003 file server did successfully join my domain.I am not running Winbindd primarily because it was not part of the Samba packaging provided by Suse. Is it necessary to run Winbindd in order to have the Windows 2003 servers validate? Any suggestions would be greatly appreciated. Cynthia Jeness -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Error 1326 Connecting from Windows XP
I am using Samba 3.0.13-1.1 which I installed as part of installing Suse 9.3. I started working my way through the Samba manual and set up the following simple configuration file: [general] workgroup = TUX-NET [homes] guest ok = no read only = no I was then able to successfully connect from another Linux client also running Suse 9.3. However, when I moved to my Windows client, I received the following error when I used net use z: \\fragbox\cj user:cj pippin System error 1240 - The account is not authorized to log in from this station. I did some googling and some Microsoft postings which indicated that this was related to encryption or not having guest enabled. So I changed my configuration to the following [general] workgroup = TUX-NET encrypt passwords = yes [homes] guest ok = yes read only = no Now I get the following error: System error 1326 has occurred. Logon failure: unknown user name or bad password. Also, with encryption on, my test from the Linux client also fails. Several other points. I do have a user account on the my Samba server (fragbox) with the user name cj and the password pippin. Also, I did change my work group name on Microsoft to TUX-NET and I see TUX-NET when I use the Microsoft browse facility. I have looked at the two logs under /var/log/samba and there is no message in the logs when I initiate anything from the Windows side. I have used Samba successfully a couple of years ago but only with unencrypted passwords. Given the concerns about security, I do not want to resort to that again. We are proposing to replace an old Novell server with a new Linux server at a non-profit agency. So I need to verify that this will really work before I recommend that they make such a move. Please note that this is all volunteer and not for profit on my part. Thanks, Cindy Jeness -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Error 1326 Connecting from Windows XP
Thank-you. This solved my immediate problem under both Linux and Windows. As I said in my post, I am working my way through the documentation and got stuck on the section that had you test the installation (Chapter 1 page 5-6).This section did not address the encryption problem which will obviously show up when anyone tries to test their installation under Windows. It did list some common problems but not encryption. This is not meant to be a criticism; I greatly appreciate the effort that has been put into all aspects of the Samba project. Cindy Jeness Mogens Kjaer wrote: Cynthia Jeness wrote: ... encrypt passwords = yes ... Also, with encryption on, my test from the Linux client also fails. Several other points. I do have a user account on the my Samba server (fragbox) with the user name cj and the password pippin. You must add the password to the smbpasswd file (as root) on the server: smbpasswd -a cj Mogens -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
