Dear Sir, Recently I've upgraded our Samba installation. After then I find that all WinXP workstations cannot logon to the server. The official HOWTO mentioned this problem and suggested resetting the SID using "net setlocalsid ....". But this does not help in my case. The SID of our server has not been changed. So I've to go to every workstation for rejoin the domain. This is definitely a horrible experience. I would like to ask how to find out what's gone wrong, regarding server and/or workstation configurations. Yours sincerely, S.Y.C.
anctop@hotmail.com wrote:> Dear Sir, > > Recently I've upgraded our Samba installation.... From what version of samba to what version of samba? Mogens -- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: mk@crc.dk Homepage: http://www.crc.dk
On Friday 09 September 2005 20:33, anctop@hotmail.com wrote:> Dear Sir, > > Recently I've upgraded our Samba installation. After then I find that all > WinXP workstations cannot logon to the server. The official HOWTO mentioned > this problem and suggested resetting the SID using "net setlocalsid ....". > But this does not help in my case. The SID of our server has not been > changed. So I've to go to every workstation for rejoin the domain. This is > definitely a horrible experience. I would like to ask how to find out > what's gone wrong, regarding server and/or workstation configurations.First off, I can not help you given the lack of information you have provided. You provide no information regarding what version of Samba you have upgraded from, nor what version you have just installed. You have provided no smb.conf file contents. Nor have you identified the source of your updated Samba. I wrote two books. Both are part of the official Samba documentation. The book "Samba-3 by Example" provides details examples to assist in the deployment of Samba-3. The book included fully documented network deployment guidance for a range of networks, starting with very simple environments right up to very complex networks. Given that the key objective of this book is to provide deployment guidance, the second edition includes a new chapter on the subject of upgrading and updating Samba. That chapter should have saved you from your pain. The book "The Official Samba-3 HOWTO and Reference Guide", is intended as a mechanic's guide to Samba. It's purpose is to document in detail, the various intrinsics of managing Sambas internals, as well as how to use the various tools and utilities that ship with Samba. It includes only one chapter that has a few example Samba configurations, but does not go into enough detail to meaningfully bridge the knowleadge gap of a new non-technical user. The HOWTO books includes several chapters on debugging and validation of your Samba configuration. Perhaps you should follow those chapters so that you can provide a little more information so that we can help you. Both books are available in printed second editions from Amazon.Com. The second editions were released at LinuxWorld, San Francisco, in August 2005. You can also obtain them in PDF and HTML form from the Samba web site at: http://www.samba.org/samba/docs/ Cheers, - John T. -- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO & Reference Guide, 2 Ed., ISBN: 0131882228 Samba-3 by Example, 2 Ed., ISBN: 0131882221X Hardening Linux, ISBN: 0072254971 Other books in production.
>> >> Recently I've upgraded our Samba installation. >... > > From what version of samba to what version of samba? > >Mogens > > >-- >Mogens Kjaer, Carlsberg A/S, Computer Department >Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark >Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 >Email: mk at crc.dk Homepage: http://www.crc.dkDear Sir, I must apologize for not supplying enough information. Here they are: 1. I was upgrading from v3.0.6 to v3.0.20. 2. "configure --prefix=XXXX", "make", and "make install" were all successful. 3. Then I copied the old samba/private/smbpasswd to XXXX/private/ and invoked "nmbd -D" and "smbd -D". 4. There was no problem with Win9x/ME workstations. But users could not logon from WinXP workstations. 5. Then I killed "nmbd" and "smbd", obtained the old SID from the old installation, and set the new SID to this, and invoked "nmbd -D","smbd -D" again. 6. However, the situation remained the same. Our smb.conf file is shown below: [global] netbios name = xxxx server string = Samba server workgroup = SMBDomain ; guest ok = no ; hosts allow = xxx.xxx.xxx. localhost hosts deny = ALL EXCEPT xxx.xxx.xxx. localhost bind interfaces only = yes ; log file = XXXX/var/log.%I max log size = 700 debug timestamp = yes syslog = 1 syslog only = no ; browseable = no browse list = no local master = yes preferred master = yes domain master = yes os level = 999 ; follow symlinks = yes wide links = no ; wide links = yes hide dot files = yes ; map archive = no map system = no map hidden = no create mask = 0600 directory mask = 0700 delete readonly = no ; valid users = root, nobody, @some_groups, some_users security = user ; encrypt passwords = yes unix password sync = yes passwd chat = *new*password* %n\n *re*enter*password* %n\n *password*changed* passwd chat debug = yes update encrypted = yes ; domain logons = yes ; logon script = logon.bat logon path = \\%L\Profiles\%u logon drive = F: ; load printers = yes printcap name = /etc/printcap ; ; dns proxy = no ; socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 time server = yes [netlogon] path = .... read only = yes [homes] read only = no create mask = 0604 directory mask = 0701 [Profiles] path = .... read only = no create mask = 0604 directory mask = 0701