Re: [Samba] Samba Upgrade 3.0.33 to 3.6.13.
On Wed, Apr 3, 2013 at 1:34 PM, TAKAHASHI Motonobu wrote: > From: Rodney Green > Date: Wed, 3 Apr 2013 08:27:57 -0400 > >> My problem is that the SID to UID >> mappings and permissions aren't carrying over to the new version. > > (snip) > >> Current config (3.0.33): >> >> [global] >> >> workgroup = domain > > (snip) > >> winbind separator = + >> idmap uid = 1-2 >> idmap gid = 1-2 >> --- >> New config (3.6.13): >> >> [global] >> netbios name = test-samba >> security = domain >> realm = domain1.domain.com >> password server = domain-server >> idmap config * : backend = tdb >> idmap config * : range = 10001-2 >> idmap config domain : backend = rid >> idmap config domain : range = 1-2 >> idmap config domain : base_rid = 0 >> workgroup = domain > (snip) >> encrypt passwords = yes >> winbind use default domain = yes >> restrict anonymous = 2 >> passdb backend = tdbsam > > Because you use default idmap (tdb) in Samba 3.0.33 and use idmap_rid for > "domain" domain in Samba 3.6.13. > > If you use same mappings, use same winbindd_idmap.tdb file or manually set > the mapping with using wbinfo command. > > --- > TAKAHASHI Motonobu / @damemonyo >facebook.com/takahashi.motonobu > Thanks, Takahashi. That's seems to have gotten things working properly. I noticed that the tdb files for 3.0.33 are in the /var/cache/samba directory. I copied winbindd_idmap.tdb from /var/cache/samba to /var/lib/samba and the mappings problem was corrected. Do you think I should copy all of the tdb files from /var/cache/samba to /var/lib/samba? Thanks again, Rodney -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Upgrade 3.0.33 to 3.6.13.
From: Rodney Green Date: Wed, 3 Apr 2013 08:27:57 -0400 > My problem is that the SID to UID > mappings and permissions aren't carrying over to the new version. (snip) > Current config (3.0.33): > > [global] > > workgroup = domain (snip) > winbind separator = + > idmap uid = 1-2 > idmap gid = 1-2 > --- > New config (3.6.13): > > [global] > netbios name = test-samba > security = domain > realm = domain1.domain.com > password server = domain-server > idmap config * : backend = tdb > idmap config * : range = 10001-2 > idmap config domain : backend = rid > idmap config domain : range = 1-2 > idmap config domain : base_rid = 0 > workgroup = domain (snip) > encrypt passwords = yes > winbind use default domain = yes > restrict anonymous = 2 > passdb backend = tdbsam Because you use default idmap (tdb) in Samba 3.0.33 and use idmap_rid for "domain" domain in Samba 3.6.13. If you use same mappings, use same winbindd_idmap.tdb file or manually set the mapping with using wbinfo command. --- TAKAHASHI Motonobu / @damemonyo facebook.com/takahashi.motonobu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba Upgrade 3.0.33 to 3.6.13.
Hello, I'm attempting to upgrade a server from Samba 3.0.33 to Samba 3.6.13. I'm testing the upgrade on a virtual machine with the same set up and data as the production server. My problem is that the SID to UID mappings and permissions aren't carrying over to the new version. Here's what I'm doing: - Uninstall previous version RPMs (This is a CentOS 5.5 server) - Install new 3.6.13 packages - Run net rpc join to join the machine to our domain (haven't been able to make anything work with ADS security. - Reboot After doing the above, I currently have to set permissions for the shares so I can access them from Windows machines. Please look at my configurations below. A point in the right direction would be most welcome! Current config (3.0.33): [global] workgroup = domain server string = Samba netbios name = fileserver hosts allow = 127. 192.168.115. encrypt passwords = yes security = domain passdb backend = tdbsam password server = * log level = 2 log file = /var/log/samba/samba.log.%m winbind separator = + idmap uid = 1-2 idmap gid = 1-2 --- New config (3.6.13): [global] netbios name = test-samba security = domain realm = domain1.domain.com password server = domain-server idmap config * : backend = tdb idmap config * : range = 10001-2 idmap config domain : backend = rid idmap config domain : range = 1-2 idmap config domain : base_rid = 0 workgroup = domain winbind enum users = yes winbind enum groups = yes winbind refresh tickets = yes template homedir = /shared/HOMEDIRS/%U template shell = /bin/bash client use spnego = yes client ntlmv2 auth = yes encrypt passwords = yes winbind use default domain = yes restrict anonymous = 2 passdb backend = tdbsam log level = 2 log file = /var/log/samba/samba.log.%m -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade problem with ADS
On Fri, 2012-09-07 at 01:41 +, Nitin Thakur wrote: > is it possible to run samba with ad without winbind? It isn't recommended, and won't help the issue you are having. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade problem with ADS
is it possible to run samba with ad without winbind? Nitin Thakur ---Original Message--- From: "Andrew Bartlett" Sent: 6/9/2012 20:42 To: nitintha...@hotmail.com Cc: samba@lists.samba.org Subject: Re: [Samba] Samba upgrade problem with ADS On Wed, 2012-09-05 at 12:07 +, Nitin Thakur wrote: > how about i get rid of secrets file all together? You can delete secrets.tdb and secrets.ldb if either exists. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade problem with ADS
On Wed, 2012-09-05 at 12:07 +, Nitin Thakur wrote: > how about i get rid of secrets file all together? You can delete secrets.tdb and secrets.ldb if either exists. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade problem with ADS
how about i get rid of secrets file all together? Nitin Thakur ---Original Message--- From: "Andrew Bartlett" Sent: 5/9/2012 0:26 To: nitintha...@hotmail.com Cc: samba@lists.samba.org Subject: Re: [Samba] Samba upgrade problem with ADS On Tue, 2012-09-04 at 22:10 -0400, Nitin Thakur wrote: > hi gurus > > My samba upgrade woes: - > > I have to run 2 instances of samba one for dev and one for UAT. both the > instances are giving me hard time after the upgrade. > > One instance keeps giving me following error: - > > connect_to_domain_password_server: unable to open the domain client session > to machine x.x.x.xxx.COM. Error was : > NT_STATUS_CANT_ACCESS_DOMAIN_INFO. > [2012/09/04 16:19:36.993000, 0] > auth/auth_domain.c:292(domain_client_validate) that means it could not find the domain password in secrets.tdb. When you upgraded, did you either copy the secrets.tdb to the new prefix, or use the same prefix? This doesn't explain the re-join issues, unless you are mixing up a 'net' binary from one release (and prefix) with smbd/winbindd from the other however. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade problem with ADS
On Tue, 2012-09-04 at 22:10 -0400, Nitin Thakur wrote: > hi gurus > > My samba upgrade woes: - > > I have to run 2 instances of samba one for dev and one for UAT. both the > instances are giving me hard time after the upgrade. > > One instance keeps giving me following error: - > > connect_to_domain_password_server: unable to open the domain client session > to machine x.x.x.xxx.COM. Error was : > NT_STATUS_CANT_ACCESS_DOMAIN_INFO. > [2012/09/04 16:19:36.993000, 0] > auth/auth_domain.c:292(domain_client_validate) that means it could not find the domain password in secrets.tdb. When you upgraded, did you either copy the secrets.tdb to the new prefix, or use the same prefix? This doesn't explain the re-join issues, unless you are mixing up a 'net' binary from one release (and prefix) with smbd/winbindd from the other however. Andrew Bartlett -- Andrew Bartletthttp://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba upgrade problem with ADS
hi gurus My samba upgrade woes: - I have to run 2 instances of samba one for dev and one for UAT. both the instances are giving me hard time after the upgrade. One instance keeps giving me following error: - connect_to_domain_password_server: unable to open the domain client session to machine x.x.x.xxx.COM. Error was : NT_STATUS_CANT_ACCESS_DOMAIN_INFO. [2012/09/04 16:19:36.993000, 0] auth/auth_domain.c:292(domain_client_validate) It returns this error for all the password servers. I deleted the server from ad and tried to rejoin the domain. it did join the domain but returned the error: - # /opt/local/samba/bin/net -s /opt/local/samba/lib/smb.conf.dev ads join -U admin Enter admin's password: Using short domain name -- Joined '' to realm '...com' DNS Update for x..xx.xxx.com failed: ERROR_DNS_UPDATE_FAILED DNS update failed! since then it keeps giving me error: - [2012/09/04 21:43:10.299657, 0] smbd/server.c:1109(main) standard input is not a socket, assuming -D option [2012/09/04 21:43:10.606915, 0] libads/kerberos_util.c:101(ads_kinit_password) kerberos_kinit_password X$@XXX.XX.XX.COM failed: Preauthentication failed [2012/09/04 21:43:10.608476, 0] printing/nt_printing.c:102(nt_printing_init) nt_printing_init: error checking published printers: WERR_ACCESS_DENIED moving on to other instance: - [2012/09/04 15:51:47.207600, 5] rpc_client/cli_pipe.c:738(rpc_api_pipe_send) rpc_api_pipe: host XX.X.X.XX.COM [2012/09/04 15:51:47.209191, 5] rpc_client/cli_pipe.c:97(rpc_read_send) rpc_read_send: data_to_read: 52 [2012/09/04 15:51:47.209422, 5] rpc_client/cli_pipe.c:1521(check_bind_response) check_bind_response: accepted! [2012/09/04 15:51:47.209687, 5] passdb/passdb.c:2365(get_trust_pw_clear) get_trust_pw_clear: could not fetch clear text trust account password for domain XX [2012/09/04 15:51:47.209844, 5] passdb/machine_account_secrets.c:267(secrets_fetch_trust_account_password_legacy) secrets_fetch failed! [2012/09/04 15:51:47.209998, 5] passdb/passdb.c:2403(get_trust_pw_hash) get_trust_pw_hash: could not fetch trust account password for domain XXX [2012/09/04 15:51:47.210109, 0] rpc_client/cli_pipe_schannel.c:54(get_schannel_session_key_common) get_schannel_session_key: could not fetch trust account password for domain 'X' [2012/09/04 15:51:47.211665, 0] rpc_client/cli_pipe_schannel.c:184(cli_rpc_pipe_open_schannel) cli_rpc_pipe_open_schannel: failed to get schannel session key from server XXX.X.XXX.XX.COM for domain XX. [2012/09/04 15:51:47.211845, 0] auth/auth_domain.c:193(connect_to_domain_password_server) connect_to_domain_password_server: unable to open the domain client session to machine ....COM. Error was : NT_STATUS_CANT_ACCESS_DOMAIN_INFO. [2012/09/04 15:51:47.213484, 0] auth/auth_domain.c:292(domain_client_validate) domain_client_validate: Domain password server not available. [2012/09/04 15:51:47.213654, 5] auth/auth.c:271(check_ntlm_password) check_ntlm_password: winbind authentication for user [] FAILED with error NT_STATUS_CANT_ACCESS_DOMAIN_INFO [2012/09/04 15:51:47.213779, 2] auth/auth.c:319(check_ntlm_password) check_ntlm_password: Authentication for user [X] -> [XX] FAILED with error NT_STATUS_CANT_ACCESS_DOMAIN_INFO [2012/09/04 15:51:47.213950, 3] smbd/error.c:81(error_packet_set) error packet at smbd/sesssetup.c(124) cmd=115 (SMBsesssetupX) NT_STATUS_CANT_ACCESS_DOMAIN_INFO Here is the smbd.conf for 1st instance #=== Global Settings = [global] socket options = TCP_NODELAY IPTOS_LOWDELAY netbios name = X workgroup = X server string = Samba Server ver %v security = ADS log file = /opt/local/samba/dev/logs/log.%m max log size = 50 password server = xx...xxx.com, ...xxx.com encrypt passwords = yes realm = XXX..X.COM local master = no domain master = no domain logons = no dns proxy = no smb passwd file = /opt/local/samba/dev/private private dir = /opt/local/samba/dev/private username map = /opt/local/samba/dev/users.map pid directory = /opt/local/samba/dev bind interfaces only = yes wins support = no domain master = no allow trusted domains = yes locking = yes lock directory = /opt/local/samba/var/dev/locks preserve case = yes short preserve case = yes name resolve order = host bcast load printers = no printcap name = /dev/null deadtime = 15 preferred master = no guest account = nobody guest ok = yes syslog = 0 interfaces = xxx.xxx.xxx.xxx socket address = xxx.xxx.xxx.xxx [share] comment = share path = /share read only = No create mask = 0774 browseable = yes preserve case = yes and smb.conf.uat for second instance [global] socket options = TCP_NODELAY IPTOS_LOWDELAY netbios name = X-UAT workgroup = XX
Re: [Samba] Samba upgrade question
The key advantages of the Solaris provided version is that - someone already did the compilation work - ZFS support is included (this is backported by Sun and not included with 3.0.x source code from samba.) - nsswitch support is also enabled The big problems I had with Sun's version (which is why I also ended up recompiling) - domain trusts don't always work, and the idmap functionality is buggy. So I think 3.0.x is pretty much a dead-end at this point. According to the Oracle forums, Samba 3.4.x is included with the recent Solaris Express release- so I expect it to be included with Solaris 11 (whenever that comes out.) My guess (no evidence to back this up) is that Solaris 10 will stay on samba 3.0.x. You have to make some changes when you change versions and if they pushed that our as an automatic update it could possible break things. With the sunfreeware and blastwave versions of samba- - these might be 32-bit only. - I don't think zfs is included. - nsswitch support may or may not be included.I had problems with this with sunfreeware samba in the past. On 12/20/2010 11:34 AM, Ray Van Dolson wrote: On Thu, Dec 16, 2010 at 07:56:55AM -0800, Chernoguz, Inessa wrote: Hi All, I have a problem with upgrade samba on Solaris 10 (x86). The current version is 3.0.25b (distributed with Solaris 10). I am trying to upgrade version to 3.4.5. I compiled samba from sources, has not any problem with make and installation. Now I have 2 different versions and when I am running "svcadm enable samba" I am receiving old version. The old version installed under: /usr/sfw/sbin, new one under /usr/sbin... # /usr/sfw/sbin/smbd -V Version 3.0.25a # /usr/sbin/smbd -V Version 3.4.5 # ps -ef | grep smbd root 7531 7305 0 17:55:32 pts/1 0:00 grep smbd root 6981 6979 0 15:19:58 ? 0:00 /usr/sfw/sbin/smbd -D root 6979 1 0 15:19:58 ? 0:00 /usr/sfw/sbin/smbd -D Can you, please help me here? Thanks a lot, Inessa As someone already replied, you need to disable the vendor provided Samba first: # svcadm disable samba Then set up SysV init scripts for your new, custom installation of Samba or something via SMF. Alternately, Sunfreeware or Blastwave may have pre-packaged Samba installs that include these scripts. I prefer sticking with the vendor-provided packages when possible (hand built packages don't scale administratively). The latest Sun version of Samba is 3.0.37 for Solaris 10 and I believe they have a refresh due out shortly. Thanks, Ray -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade question
On Thu, Dec 16, 2010 at 07:56:55AM -0800, Chernoguz, Inessa wrote: > Hi All, > > I have a problem with upgrade samba on Solaris 10 (x86). The current > version is 3.0.25b (distributed with Solaris 10). I am trying to > upgrade version to 3.4.5. I compiled samba from sources, has not any > problem with make and installation. Now I have 2 different versions > and when I am running "svcadm enable samba" I am receiving old > version. The old version installed under: /usr/sfw/sbin, new one > under /usr/sbin... > > # /usr/sfw/sbin/smbd -V > Version 3.0.25a > # /usr/sbin/smbd -V > Version 3.4.5 > # ps -ef | grep smbd > root 7531 7305 0 17:55:32 pts/1 0:00 grep smbd > root 6981 6979 0 15:19:58 ? 0:00 /usr/sfw/sbin/smbd -D > root 6979 1 0 15:19:58 ? 0:00 /usr/sfw/sbin/smbd -D > > Can you, please help me here? > > Thanks a lot, > Inessa As someone already replied, you need to disable the vendor provided Samba first: # svcadm disable samba Then set up SysV init scripts for your new, custom installation of Samba or something via SMF. Alternately, Sunfreeware or Blastwave may have pre-packaged Samba installs that include these scripts. I prefer sticking with the vendor-provided packages when possible (hand built packages don't scale administratively). The latest Sun version of Samba is 3.0.37 for Solaris 10 and I believe they have a refresh due out shortly. Thanks, Ray -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade HowTo requested
Hi, Volker! On Sat, Dec 18, 2010 at 10:10 AM, Volker Lendecke wrote: > On Fri, Dec 17, 2010 at 11:26:12AM +0100, Willy Offermans wrote: >> >> 20101026: >> AFFECTS: users of net/samba35 >> AUTHOR: Timur Bakeyev >> >> This is the latest stable release of the Samba3 distribution. It has >> been extended with the experimental support of the NFS4-like ACLs on >> ZFS partitions, thanks to the sysutils/libsunacl library by Edward >> Tomasz Napierala(trasz). This support haven't been tested thoroughly, >> so try it on your own risk. > > This looks interesting. I just did a portsnap fetch update > in my FreeBSD 8.1 box, but I don't find that snippet. Where > can I find those patches? There are small patches in the port itself to detect and incorporate libsunacl via configure and build vfs_zfsacl module OOTB. As for the lib itself - it is situated in /usr/ports/sysutils/libsunacl. With regards, Timur. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade question
You would have to define a new Solaris 10 service for the new samba. I don't know how to do this myself- the solaris documentation should say how, but it always looked pretty complicated to me. You have to define the dependencies. You are probably better off creating an /etc/init.d/samba script and sym linking it to the appropriate rc.d directions- the same way you would have done it in Solaris 9 or earlier. "svcs -a" will list it as a legacy service. This is what I did. You will need to use "svcadm" to disable the bundled samba version. I believe Solaris Express , just released, has samba 3.4.x or 3.5.x higher included. -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of Chernoguz, Inessa Sent: Thursday, December 16, 2010 10:57 AM To: samba@lists.samba.org Subject: [Samba] Samba upgrade question Hi All, I have a problem with upgrade samba on Solaris 10 (x86). The current version is 3.0.25b (distributed with Solaris 10). I am trying to upgrade version to 3.4.5. I compiled samba from sources, has not any problem with make and installation. Now I have 2 different versions and when I am running "svcadm enable samba" I am receiving old version. The old version installed under: /usr/sfw/sbin, new one under /usr/sbin... # /usr/sfw/sbin/smbd -V Version 3.0.25a # /usr/sbin/smbd -V Version 3.4.5 # ps -ef | grep smbd root 7531 7305 0 17:55:32 pts/1 0:00 grep smbd root 6981 6979 0 15:19:58 ? 0:00 /usr/sfw/sbin/smbd -D root 6979 1 0 15:19:58 ? 0:00 /usr/sfw/sbin/smbd -D Can you, please help me here? Thanks a lot, Inessa -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade HowTo requested
On Fri, Dec 17, 2010 at 11:26:12AM +0100, Willy Offermans wrote: > I do not think that this issue is related to dependencies. Of course I need > to be sure that the dependencies are correctly installed as well, but this > job is accomplished by ``portupgrade -R -N'' quite well. > > No, the real problem lays in the settings and databases created in a > previous version of samba, which will be lost, altered or corrupted upon an > upgrade. To phrase the questions again? > > Is there a procedure on how to upgrade samba to a newer version? > > How can the ignorant user be informed when using portupgrade? > > I'm sorry, I just recall the UPDATING file in /usr/ports/. The > following is a cut from this file: > > > > 20101026: > AFFECTS: users of net/samba35 > AUTHOR: Timur Bakeyev > > This is the latest stable release of the Samba3 distribution. It has > been extended with the experimental support of the NFS4-like ACLs on > ZFS partitions, thanks to the sysutils/libsunacl library by Edward > Tomasz Napierala(trasz). This support haven't been tested thoroughly, > so try it on your own risk. This looks interesting. I just did a portsnap fetch update in my FreeBSD 8.1 box, but I don't find that snippet. Where can I find those patches? Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba upgrade question
Hi All, I have a problem with upgrade samba on Solaris 10 (x86). The current version is 3.0.25b (distributed with Solaris 10). I am trying to upgrade version to 3.4.5. I compiled samba from sources, has not any problem with make and installation. Now I have 2 different versions and when I am running "svcadm enable samba" I am receiving old version. The old version installed under: /usr/sfw/sbin, new one under /usr/sbin... # /usr/sfw/sbin/smbd -V Version 3.0.25a # /usr/sbin/smbd -V Version 3.4.5 # ps -ef | grep smbd root 7531 7305 0 17:55:32 pts/1 0:00 grep smbd root 6981 6979 0 15:19:58 ? 0:00 /usr/sfw/sbin/smbd -D root 6979 1 0 15:19:58 ? 0:00 /usr/sfw/sbin/smbd -D Can you, please help me here? Thanks a lot, Inessa -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade question
confirm 91cc11461a9aa5e7548d5df97d93dade856b7c68 _ From: Chernoguz, Inessa Sent: Thursday, December 16, 2010 5:57 PM To: 'samba@lists.samba.org' Subject:Samba upgrade question Hi All, I have a problem with upgrade samba on Solaris 10 (x86). The current version is 3.0.25b (distributed with Solaris 10). I am trying to upgrade version to 3.4.5. I compiled samba from sources, has not any problem with make and installation. Now I have 2 different versions and when I am running "svcadm enable samba" I am receiving old version. The old version installed under: /usr/sfw/sbin, new one under /usr/sbin... # /usr/sfw/sbin/smbd -V Version 3.0.25a # /usr/sbin/smbd -V Version 3.4.5 # ps -ef | grep smbd root 7531 7305 0 17:55:32 pts/1 0:00 grep smbd root 6981 6979 0 15:19:58 ? 0:00 /usr/sfw/sbin/smbd -D root 6979 1 0 15:19:58 ? 0:00 /usr/sfw/sbin/smbd -D Can you, please help me here? Thanks a lot, Inessa -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade HowTo requested
Hello tms3, On Thu, Dec 16, 2010 at 07:27:17AM -0800, t...@tms3.com wrote: > > > > > > >Well, it might be that it has worked in your case, but certainly > >not in > >mine. I do not know what happened to the drivers or database of > >the drivers, but > >something was really messed up. I like to clarify this and to put > >it on a > >higher level. I like to figure out what the procedure is to follow > >and how > >we can inform the users about this procedure. > > Well, it might do you well to go over the list of dependencies that > the port installed initially, and upgrade those components as well. > I'm not sure what is NOT working for you, but as a general rule, I > try to keep those dependecies up to date. > > > > > > > > > >-- I do not think that this issue is related to dependencies. Of course I need to be sure that the dependencies are correctly installed as well, but this job is accomplished by ``portupgrade -R -N'' quite well. No, the real problem lays in the settings and databases created in a previous version of samba, which will be lost, altered or corrupted upon an upgrade. To phrase the questions again? Is there a procedure on how to upgrade samba to a newer version? How can the ignorant user be informed when using portupgrade? I'm sorry, I just recall the UPDATING file in /usr/ports/. The following is a cut from this file: 20101026: AFFECTS: users of net/samba35 AUTHOR: Timur Bakeyev This is the latest stable release of the Samba3 distribution. It has been extended with the experimental support of the NFS4-like ACLs on ZFS partitions, thanks to the sysutils/libsunacl library by Edward Tomasz Napierala(trasz). This support haven't been tested thoroughly, so try it on your own risk. This port reverted back to the pre- net/samba34 layout of the directories and now they are again $PREFIX/etc/samba, /var/run/samba, /var/log/samba, /var/db/samba and /var/spool/samba respectively. In case, you are upgrading from net/samba34, please rename corresponding samba34/ subdirectories into samba/ ones. Upgrades from older versions of Samba and fresh installations should be seamless. Especially the last sentence is of interest. I upgraded from samba 3.3.x to 3.5.6 and went smoothly in general, but only the printer drivers were messed up. Maybe this behavior is not covered by the information in UPDATING. Anyway, to my opinion there is a need for information on how to upgrade samba. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * Dr. W.K. Offermans CAT Postdoctoral Fellow CAT Catalytic Center Institut f�r Technische und Makromolekulare Chemie RWTH Aachen Worringerweg 1, Raum 38C-150 D-52074 Aachen, Germany Phone: +49 241 80 28592 Fax:+49 241 80 22593 Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl e-mail: willy.offerm...@catalyticcenter.rwth-aachen.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade HowTo requested
Hi Willy, > Last weekend I decided to upgrade the samba server. We were running > Samba > 3.3 something and FreeBSD portupgrade was complaining that this > version should be removed and assumingly replaced by the newest > version. I removed the package via portupgrade and installed the 3.5.6 > version. The Are you running winbindd on this server? If yes, does it work properly? In my case it failed to communicate group IDs to the system, so I had to rollback to v. 3.4.9. > And specifically for FreeBSD users: How should we deal with an upgrade of samba via portupgrade? I have upgraded it many times before, and in most cases it was just make deinstall & make reinstall. With best regards, P. Trifonov -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba upgrade HowTo requested
Hello Peter, On Thu, Dec 16, 2010 at 05:42:10PM +0300, Peter Trifonov wrote: > Hi Willy, > > > Last weekend I decided to upgrade the samba server. We were running > > Samba > > 3.3 something and FreeBSD portupgrade was complaining that this version > > should be removed and assumingly replaced by the newest version. I > > removed the package via portupgrade and installed the 3.5.6 version. The > Are you running winbindd on this server? If yes, does it work properly? > In my case it failed to communicate group IDs to the system, so I had to > rollback to v. 3.4.9. > > > And specifically for FreeBSD users: How should we deal with an upgrade of > samba via portupgrade? > I have upgraded it many times before, and in most cases it was just make > deinstall & make reinstall. > > > With best regards, > P. Trifonov Concerning your first question: No, we are not running winbindd, so I cannot tell you if it might work. To your second remark: Well, it might be that it has worked in your case, but certainly not in mine. I do not know what happened to the drivers or database of the drivers, but something was really messed up. I like to clarify this and to put it on a higher level. I like to figure out what the procedure is to follow and how we can inform the users about this procedure. -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba upgrade HowTo requested
Dear Samba friends, Last weekend I decided to upgrade the samba server. We were running Samba 3.3 something and FreeBSD portupgrade was complaining that this version should be removed and assumingly replaced by the newest version. I removed the package via portupgrade and installed the 3.5.6 version. The upgrade went quite smoothly in general, but I encountered some difficulties with the printer drivers. Before the upgrade we were able to print on 4 printers. After the upgrade only 1.5 printer was working. 1 Printer worked as expected, 1 printer printed only garbage and 2 printers were not working at all. I only managed to solve the problems by de-installing and re-installing the printer drivers on the samba server. So somehow the databases in /var/db/samba/*.tdb have been messed up. I do not know what went wrong in detail and neither do I know how to prevent these kind of issues in the next upgrade. What is the procedure to upgrade samba to the newest version? How should one proceed and what are the pitfalls? How should we deal with the printer definitions and printer drivers? What should we in general do with the database files, next to backup? And specifically for FreeBSD users: How should we deal with an upgrade of samba via portupgrade? -- Met vriendelijke groeten, With kind regards, Mit freundlichen Gruessen, Willy * W.K. Offermans Home: +31 45 544 49 44 Mobile: +31 681 15 87 68 e-mail: wi...@offermans.rompen.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba Upgrade: 3.2.14 -> 3.4.1
Hello, i have made a upgrade from Samba 3.2.14 to Samba 3.4.1. The first time everything looks nice. I can login to the Domain Controller without any Problem. But when i login to a trusted domain i got "password expired" - a windows xp dialog. pdbedit -r -u [username] ... Password last set:Son, 04 Jän 2009 15:36:57 UTC Password can change: Son, 04 Jän 2009 15:36:57 UTC Password must change: never ... best regards -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Upgrade
hi, 2009/2/16 Volker Lendecke : > On Mon, Feb 16, 2009 at 01:06:45PM +0100, Bjoern Meier wrote: >> Thx for fast answer. I don't believe that is that keberos-error. the >> file-server (this is my samba server) updates daily with ntpdate on >> the same machine I try to connect. I do this now manually. But it >> changed nothing. > > Then it's very likely it's a different kerberos error. You > might want to sniff your client and/or look at a debug level > 10 log of smbd. > > Volker > I tried. But I grep for the name of the shared and nothing appeared. There is also nothing that would help. Björn -- To boldly go where no man has gone before ... I'll wait there with touristinformation -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Upgrade
On Mon, Feb 16, 2009 at 01:06:45PM +0100, Bjoern Meier wrote: > Thx for fast answer. I don't believe that is that keberos-error. the > file-server (this is my samba server) updates daily with ntpdate on > the same machine I try to connect. I do this now manually. But it > changed nothing. Then it's very likely it's a different kerberos error. You might want to sniff your client and/or look at a debug level 10 log of smbd. Volker pgpL26YItqIoY.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Upgrade
hi, 2009/2/16 Javier Arancibia : > > Try to synchronize the date/time of the clients and server > > Javier > > Thx for fast answer. I don't believe that is that keberos-error. the file-server (this is my samba server) updates daily with ntpdate on the same machine I try to connect. I do this now manually. But it changed nothing. > Bjoern Meier > Enviado por: samba-bounces+jarancibia=nacion-seguros.com...@lists.samba.org > > 16/02/2009 09:21 > > Para > samba@lists.samba.org > cc > Asunto > [Samba] Samba Upgrade > > > > > Hi list, > > I just upgrade my samba and I get from my connected shares: the > specified path does not exist.On ip-adress it works great, but I don't > want to change this on 100 clients. > > A few Infos > > Samba-Version 3.2.5 > security = ADS > getent passwd and getent group works also fine > id could resolv standard-group and the rest group > > Loglevel is 3 but nothing usefull is in there. > > Hope you could help me out. > Greetings, > Björn > -- > To boldly go where no man has gone before ... I'll wait there with > touristinformation > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > > -- To boldly go where no man has gone before ... I'll wait there with touristinformation -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba Upgrade
Hi list, I just upgrade my samba and I get from my connected shares: the specified path does not exist.On ip-adress it works great, but I don't want to change this on 100 clients. A few Infos Samba-Version 3.2.5 security = ADS getent passwd and getent group works also fine id could resolv standard-group and the rest group Loglevel is 3 but nothing usefull is in there. Hope you could help me out. Greetings, Björn -- To boldly go where no man has gone before ... I'll wait there with touristinformation -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba Upgrade to 3.0.25b leads to core dumps with winbind and ldap idmap
I have recently upgraded a Samba server running on a Red Hat Enterprise 4 (32 bit) server. The version of samba upgraded to is 3.0.25b. I noticed that a new index had to be added to my ldap (openldap) server for the sambaSID attribute. So I added the index line to slapd.conf as follows: Index sambaSID eq,sub Afterwards I ran slapindex to recreate the indices in the openldap database. Everything seems to be working fine. However, I now see a large number of Samba core dumps in my /var/log/samba/winbindd-idmap.log file. Here is a sample from the log: [2008/05/14 12:43:37, 0] lib/fault.c:fault_report(41) === [2008/05/14 12:43:37, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 6 in pid 4839 (3.0.25b-1.el4_6.4) Please read the Trouble-Shooting section of the Samba3-HOWTO [2008/05/14 12:43:37, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2008/05/14 12:43:37, 0] lib/fault.c:fault_report(45) === [2008/05/14 12:43:37, 0] lib/util.c:smb_panic(1654) PANIC (pid 4839): internal error [2008/05/14 12:43:37, 0] lib/util.c:log_stack_trace(1758) BACKTRACE: 22 stack frames: #0 winbindd(log_stack_trace+0x2d) [0x3d67b9] #1 winbindd(smb_panic+0x56) [0x3d68c0] #2 winbindd [0x3c2db5] #3 /lib/tls/libc.so.6 [0x59b908] #4 /lib/tls/libc.so.6(abort+0xe9) [0x59d279] #5 /lib/tls/libc.so.6(__assert_fail+0x101) [0x594d91] #6 /usr/lib/libldap-2.2.so.7(ldap_next_entry+0x6b) [0xfb8c2b] #7 winbindd [0x4fab15] #8 winbindd(idmap_unixids_to_sids+0x5e4) [0x4f3c87] #9 winbindd(idmap_uid_to_sid+0x6e) [0x4f714e] #10 winbindd(winbindd_dual_uid2sid+0x50) [0x37a896] #11 winbindd [0x37535d] #12 winbindd [0x376509] #13 winbindd(winbindd_sid2gid_async+0xcc) [0x37794c] #14 winbindd [0x362fa4] #15 winbindd [0x377f1b] #16 winbindd [0x376457] #17 winbindd [0x375e07] #18 winbindd [0x348bac] #19 winbindd(main+0x778) [0x34a044] #20 /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x588de3] #21 winbindd [0x348661] [2008/05/14 12:43:37, 0] lib/fault.c:dump_core(181) dumping core in /var/log/samba/cores/winbindd [2008/05/14 12:43:37, 2] lib/smbldap.c:smbldap_open_connection(786) smbldap_open_connection: connection opened winbindd: ../../../libraries/libldap/getentry.c:48: ldap_next_entry: Assertion `entry != ((void *)0)' failed. And here is the /var/log/openldap.log file output from the same time as the core dump. May 14 12:43:37 s10 slapd[4091]: conn=40 op=284 SRCH base="ou=idmap,dc=rbrooks,dc=com" scope=2 deref=0 filter="(&(objectClass=sambaIdmapEntry)(uidNumber=10020))" May 14 12:43:37 s10 slapd[4091]: conn=40 op=284 SRCH attr=sambaSID uidNumber gidNumber objectClass May 14 12:43:37 s10 slapd[4091]: conn=40 op=284 SEARCH RESULT tag=101 err=0 nentries=2 text= May 14 12:43:37 s10 slapd[4091]: conn=40 fd=11 closed May 14 12:43:37 s10 slapd[4091]: conn=41 op=7 UNBIND May 14 12:43:37 s10 slapd[4091]: conn=41 fd=15 closed May 14 12:43:37 s10 slapd[4091]: conn=42 fd=11 ACCEPT from IP=192.168.10.8:32899 (IP=0.0.0.0:389) May 14 12:43:37 s10 slapd[4091]: conn=42 op=0 BIND dn="cn=Manager,dc=rbrooks,dc=com" method=128 May 14 12:43:37 s10 slapd[4091]: conn=42 op=0 BIND dn="cn=Manager,dc=rbrooks,dc=com" mech=SIMPLE ssf=0 May 14 12:43:37 s10 slapd[4091]: conn=42 op=0 RESULT tag=97 err=0 text= May 14 12:43:37 s10 slapd[4091]: conn=42 op=1 SRCH base="" scope=0 deref=0 filter="(objectClass=*)" May 14 12:43:37 s10 slapd[4091]: conn=42 op=1 SRCH attr=supportedControl May 14 12:43:37 s10 slapd[4091]: conn=42 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= May 14 12:43:37 s10 slapd[4091]: conn=42 op=2 SRCH base="ou=idmap,dc=rbrooks,dc=com" scope=2 deref=0 filter="(&(objectClass=sambaIdmapEntry)(uidNumber=10020))" May 14 12:43:37 s10 slapd[4091]: conn=42 op=2 SRCH attr=sambaSID uidNumber gidNumber objectClass May 14 12:43:37 s10 slapd[4091]: conn=42 op=2 SEARCH RESULT tag=101 err=0 nentries=2 text= May 14 12:43:37 s10 slapd[4091]: conn=42 fd=11 closed May 14 12:43:37 s10 slapd[4091]: conn=43 fd=11 ACCEPT from IP=192.168.10.8:32901 (IP=0.0.0.0:389) May 14 12:43:37 s10 slapd[4091]: conn=43 op=0 BIND dn="cn=Manager,dc=rbrooks,dc=com" method=128 May 14 12:43:37 s10 slapd[4091]: conn=43 op=0 BIND dn="cn=Manager,dc=rbrooks,dc=com" mech=SIMPLE ssf=0 May 14 12:43:37 s10 slapd[4091]: conn=43 op=0 RESULT tag=97 err=0 text= May 14 12:43:37 s10 slapd[4091]: connection_input: conn=43 deferring operation: binding May 14 12:43:37 s10 slapd[4091]: conn=43 op=1 SRCH base="" scope=0 deref=0 filter="(objectClass=*)" May 14 12:43:37 s10 slapd[4091]: conn=43 op=1 SRCH attr=supportedControl May 14 12:43:37 s10 slapd[4091]: conn=43 op=1 SEARCH RESULT tag=101 err=0 nentries=1 text= May 14 12:43:37 s10 slapd[4091]: conn=43 op=2 SRCH base="ou=idmap,dc=rbrooks,dc=com" scope=2 deref=0 filter="(&(objectClass=sambaIdmapEntry)(
[Samba] samba upgrade, now macs can't connect
machine A: samba server, upgraded from 3.0.7 to 3.0.22. solaris 9. machine B: samba client, on powermac G4, OS 10.4 (i believe). i think samba is 3.0.10. after the upgrade of the samba server (A), machine B cannot get onto A. it keeps saying the password is wrong. i've tried tons of stuff. the keychain has been reset. the client has been rebooted. the server has had samba restarted. i've tried 3.0.22, 3.0.24 compiled w/ ldap, and 3.0.24 compiled w/o ldap. all do the same thing. from ANOTHER mac (machine C), the same user from B __can__ get in. is there some cache on machine B i need to clear? it seems like it would have to be a file, since it survives reboot. thanks for any suggs. j. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Upgrade to 3.0.21a
I have just upgrade Samba from version 2.2.8a to 3.0.21a and everything is working fine except for one user. Samba is running on HPUX version 11.11 and we have XP workstation attaching to the shares. One user is running XP but his workstation is running 64bit while all the others that work are 32bit OS. I've looked through all the readme's and install docs I can find and can't locate anything that address this. Can anyone tell me what I might be missing in smb.conf or whatever to get it to work ?? The log shows following: Failing workstation: NativeOS=[Windows XP 3790 Service Pack 1] NativeLanMan=[] PrimaryDomain=[Windows XP 5.2] Working workstation: NativeOS=[Windows 2002 Service Pack 2 2600] NativeLanMan=[Windows 2002 5.1] PrimaryDomain=[] Working then goes on with: [Fri Mar 10 08:16:07 2006 , 3] libsmb/ntlmssp.c:ntlmssp_server_auth(641) Got user=[] domain=[] workstation=[ORL02USERID] len1=1 len2=0 [Fri Mar 10 08:16:07 2006 , 5] auth/auth_util.c:make_user_info_map(162) make_user_info_map: Mapping user []\[] from workstation [ORL02USERID] Where it looks like non working PC keeps trying to authenticate him ??? [Fri Mar 10 08:26:11 2006 , 5] auth/auth.c:make_auth_context_subsystem(476) Making default auth method list for security=server [Fri Mar 10 08:26:11 2006 My global section contains: [global] workgroup = NA netbios name = SAMBA_HPUX netbios aliases = samba_hpux server string = Sources Server security = SERVER map to guest = Bad Password password server = 10.18.0.66, 10.18.6.67, 10.25.160.170, 10.25.159.119 passdb backend = smbpasswd guest account = pcguest log level = 5 log file = /var/log/samba/log.%M.%I deadtime = 10 printcap name = lpstat preferred master = No local master = No domain master = No wins server = 10.25.160.163 admin users = xxx, y, hosts deny = 10.130., 135.108., 10.28., 10.131., 10.200. Thanks, Mike -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Upgrade issues
Over the last three days I've been upgrading my Samba infrastructure. This involved moving from Red Hat Enterprise 3.0 (Samba 3.0.9) to Ubuntu 5.10(Samba 3.0.14) and some new hardware. For the most part things went well. But I do have some unresolved issues that I would like to get some feedback on. Keep in mind that this entire setup has been working properly for more than two years in this fashion. First a bit of ASCII art: --- | Main Office | |PDC | | Master LDAP | --- | | VPN | | -- | | | | | Office No. 1 | | Office No. 2 | | BDC | | BDC | | Slave LDAP | | Slave LDAP | In the "Main Office", we run a 60/40 spit of machines running Windows XP and Windows 2000, leaning heavier toward XP. One laptop (running Windows XP) gave us problems logging onto to the domain for about 20 minutes. After a minor change to the LDAP configuration and a restart of Samba on the PDC, this machine came online. The remaining machines in this office came online with very little issues - the only issue being a slow logon the very first time. In "Office No. 1" every machine runs Windows 2000 and everyone of them had to removed and re-added to the domain before logons would work. We kept getting errors stating that the domain controller was unavailable or the computer account password in the domain was incorrect. These errors happened immediately on the windows clients and nothing was recorded in the Samba logs. In "Office No. 2" we are running Windows 2000 on one machine and Windows XP Pro on all other machines. The Windows 2000 client exhibited the same symptoms as described in Office No. 1. One of the Windows XP clients exhibited the same symptoms as well. The remaining XP machines worked fine. To cure the troublesome XP client, we had to remove the machine from the domain, delete the LDAP computer account and then rejoin the domain. After that process everything seems to be functional. The upgrade process went like this: On Friday of last week, we had every user turn their computer off as they left for the day. We left all of the servers online through the weekend. On Monday, we upgraded the PDC and checked a few workstations to make sure that things were OK. On Tuesday we were involved in getting the rack in the server room buttoned up - no changes with the exception of a machine or two being taken offline for a few minutes while cables were routed. On Wednesday, we upgraded the Office No. 1 BDC, handled the problem with the Laptop in the Main office and then Upgraded Office No. 2 BDC. Because of the problems seen in both of the remote offices, this morning, we went to every workstation in the main office making sure that they functioned properly. So my question is why did we have the problems in the remote offices? Why could they not contact the domain controller? Why would a removal and rejoin cause the problem to go away? Should I be worried about future occurrences of this phenomena? -- Kevin L. Collins, MCSE Systems Manager Nesbitt Engineering, Inc. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] samba upgrade 2.2.3 to 3.0.9 - profile not found
Hi, i'm working on a new maschine with Suse 9.3 and Samba 3.0.9 running. The system on the old Server is Suse 8.2 with Samba 2.2.3. Both sambas are running as PDC with roaming profiles. Both maschines and domains have identical sids. I installed Samba on the new server, configured it, copied some home directories including the profiles from the old maschine to the new server and added some clients to the domain for testing purpose. Up to here everything worked well. But when i try to log in as domainuser, the xp box complains that the serverside stored profile can't be found and that i'm logged in with a temporary profile. After some searching for the error, i found out that the problem is around the ntuser.dat which can't be loaded from the new samba. If i remove the old ntuser.dat, the xp box offers the ntuser.dat from the default user and everything works ok, but the content of the user's desktop is lost and i would have to restore the desktop of over 200 user... this can't be the solution. I read something about sambas profiles tool which can change the sids of the ntuser.dat from the old sid to the new sid. But isn't this sid user/group specific? How can i find out the old/new sid? If i run ' profiles ntuser.dat -v ' i get an endless list of entries of sids, and i don't know which one is the one to change... Thank you for your help, Mitch ___ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Upgrade Process
Hello All, I currently have a working 3.0.7 + ldap. I would like to upgrade to 3.0.11. Can I just copy all the *.tdb's from the old var/locks to the new var/locks?? or is there another more correct way to dump the tdb's from 3.0.7 and upload them to 3.0.11 I guess my question is..is there a mothod for upgrading from one 3.x version to another 3.x version and keep everything working as it currently does with the older 3.x version...??? Thanks for all the great posts and responses. Clay -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Upgrade Yields Undesired Domain-Wide IE High Security
Roy, Have you verified that you are using the same SID after the migration? If the SID has changed, you cannot simply change it back as that will break your machine trusts. I imagine you have not received a response since you are running 2.2.12 which is a deprecated code path. You should really consider upgrading to 3.0.11. At any rate, if you do a smbpasswd -X on the two servers you'll find the two SIDs are different. I venture this guess based on the fact you omit information on secrets.tdb being copied over (and the smbpasswd file). The ntuser.dat files in your user workspaces are not owned by the user since the internal permissions reflect the old SID. There are several choices: 1) use smbpasswd -W to set the old SID on the new server and rejoin everything. Or just copy the secrets.tdb from the old server to the new assuming the servername and domain are the same. 2) Clean all the profiles and start over (not your best option). 3) Upgrade to 3.0.11 and use the profiles command in the bin dir of the distro to modify the internal ACLs of the ntuser.dat Any way you slice it, there's some work to be done. Personally I'd choose #1 to get your users happy and plan an upgrade to 3.0.11 as soon as you an muster the time and be mindful of secrets.tdb in the future since that is your servers identity (so to speak). You can save yourself much work next time by migrating the smbpasswd file in the private folder as well as the secrets.tdb. Bill On Thu, 24 Feb 2005, RA Cohen wrote: > Forgive the repost, but I've changed the subject line since I > haven't seen a reply yet...please help, I don't have much hair > left! > > Hello All, > > I had been successfully running Samba 2.2.8a on a FreeBSD 4.7 > box for a couple years using roaming profiles. The box was > functioning as PDC. The hardware was getting old; I needed to > migrate to a new server. So, I built a FreeBSD 5.3-RELEASE box > on some relatively modern hardware and installed Samba 2.2.12. I > copied the master.passwd file to the new box, did the pwd_mkdb, > also copied the group file. Then I tarred all the home > directories on the old server, and untarred them on the new > server. Same with all the shares. Also used the same smb.conf > file. > > As far as the users go, I am having them re-initialize their > passwords thru Usermin so their Samba passwords are now synched > with their FreeBSD/Unix passwords. I also manually joined each > machine to the domain, first on the server by smbpasswd -a -m > MACHINENAME, then actually went around to each (thank goodness > only 65 machines) machine, unjoined it from the domain by > putting them back into a workgroup, then joined the domain > again. No problem. Users can log into the domain from any > machine, get their roaming profiles, use their shares, etc. In > short, everything seems to work BUT here's the "gotcha": > > Somehow, the security settings for Internet Explorer have been > set to medium for the entire domain. I have not a clue how this > has happened, but it means the users have to click thru numerous > "When you send information to the internet, it might be possible > for others to see that information. Do you want to continue?" > This pops up anytime a form is submitted. Also, file downloads > are now not possible. > > I fail to understand how this has happened. And, the IE settings > cannot be changed, they simply revert back to the medium > setting. It is this behavior that makes me conclude this is a > domain-wide situation. When I log in to any of the machines as a > local administrator, the IE settings are at a custom level that > does permit more unrestricted browsing. I never created any > policies for this, so I assume they were the defaults for Win2K > with pretty much the latest patches, etc. I've also compared > file permissions and ownerships with those on the old server, > they seem to be the same. > > Any help would be greatly appreciated...Thank you in advance. > > Roy > > PS Here's the relevant parts of smb.conf: > > [global] > workgroup = > netbios name = > server string = Samba PDC running %v > encrypt passwords = Yes > passwd program = /usr/bin passwd %u > passwd chat = *New*UNIX*password* %n\n > *Retype*new*UNIX*password* %n\n *Enter*new*UNIX* > password* %n\n *Retype*new*UNIX*password* %n\n *passwd: > *all*authentication*tokens*updated*succ > essfully* > unix password sync = Yes > log level = 2 > log file = /var/log/samba/log.%m > max log size = 50 > name resolve order = wins lmhosts hosts bcast > time server = Yes > lpq cache time = 20 > socket options = TCP_NODELAY IPTOS_LOWDELAY > SO_SNDBUF=8192 SO_RCVBUF=8192 > total print jobs = 100 > logon drive = Q: > logon home = \\%L\%U\.profile > domain logons = Yes > os level = 255 > preferred master = Yes > domain master = Yes > w
[Samba] Samba Upgrade Yields Undesired Domain-Wide IE High Security
Forgive the repost, but I've changed the subject line since I haven't seen a reply yet...please help, I don't have much hair left! Hello All, I had been successfully running Samba 2.2.8a on a FreeBSD 4.7 box for a couple years using roaming profiles. The box was functioning as PDC. The hardware was getting old; I needed to migrate to a new server. So, I built a FreeBSD 5.3-RELEASE box on some relatively modern hardware and installed Samba 2.2.12. I copied the master.passwd file to the new box, did the pwd_mkdb, also copied the group file. Then I tarred all the home directories on the old server, and untarred them on the new server. Same with all the shares. Also used the same smb.conf file. As far as the users go, I am having them re-initialize their passwords thru Usermin so their Samba passwords are now synched with their FreeBSD/Unix passwords. I also manually joined each machine to the domain, first on the server by smbpasswd -a -m MACHINENAME, then actually went around to each (thank goodness only 65 machines) machine, unjoined it from the domain by putting them back into a workgroup, then joined the domain again. No problem. Users can log into the domain from any machine, get their roaming profiles, use their shares, etc. In short, everything seems to work BUT here's the "gotcha": Somehow, the security settings for Internet Explorer have been set to medium for the entire domain. I have not a clue how this has happened, but it means the users have to click thru numerous "When you send information to the internet, it might be possible for others to see that information. Do you want to continue?" This pops up anytime a form is submitted. Also, file downloads are now not possible. I fail to understand how this has happened. And, the IE settings cannot be changed, they simply revert back to the medium setting. It is this behavior that makes me conclude this is a domain-wide situation. When I log in to any of the machines as a local administrator, the IE settings are at a custom level that does permit more unrestricted browsing. I never created any policies for this, so I assume they were the defaults for Win2K with pretty much the latest patches, etc. I've also compared file permissions and ownerships with those on the old server, they seem to be the same. Any help would be greatly appreciated...Thank you in advance. Roy PS Here's the relevant parts of smb.conf: [global] workgroup = netbios name = server string = Samba PDC running %v encrypt passwords = Yes passwd program = /usr/bin passwd %u passwd chat = *New*UNIX*password* %n\n *Retype*new*UNIX*password* %n\n *Enter*new*UNIX* password* %n\n *Retype*new*UNIX*password* %n\n *passwd: *all*authentication*tokens*updated*succ essfully* unix password sync = Yes log level = 2 log file = /var/log/samba/log.%m max log size = 50 name resolve order = wins lmhosts hosts bcast time server = Yes lpq cache time = 20 socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 SO_RCVBUF=8192 total print jobs = 100 logon drive = Q: logon home = \\%L\%U\.profile domain logons = Yes os level = 255 preferred master = Yes domain master = Yes wins support = Yes logon script = %u.bat domain admin group = netadmins [netlogon] path = /usr/local/samba/lib/netlogon browseable = No root preexec = perl /usr/local/samba/lib/netlogon/genlogon.pl %u %g %m root postexec = perl /usr/local/samba/lib/netlogon/genlogoff.pl %u __ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Upgrade...
Brent Smith wrote: Sorry if this is a dup. I sent right before I subscribed to the list, so I'm not sure if it made it. I have just taken over a redhat system with Samba 3.0.0 configured with security = user, and domain logins enabled. I've included the smb.conf at the end of this message. I would like to upgrade to 3.0.10 for a numbers of reasons, one being security and one being that password changes don't work from workstation machines because of the Windows KB828741 patch. What I want to know, is if I should expect any incompatibilities between versions or if my existing config files will work with the new version? This is a mission critical system, so I really don't want to upgrade unless there are going to be very minimal issues. Will a simple rpm -Uvh ./samba-3.0.10-1_rh9.i386.rpm put me in the clear? Thanks for your help. Here is some information about the system: - OLD RPM PACKAGE - $ rpm -qi samba Name: sambaRelocations: /usr Version : 3.0.0 Vendor: (none) Release : 2 Build Date: Thu 09 Oct 2003 05:12:20 PM PDT Install date: Sat 11 Oct 2003 10:41:04 PM PDT Build Host: *removed* Group : NetworkingSource RPM: samba-3.0.0-2.src.rpm Size: 46416163 License: GNU GPL version 2 Packager: Gerald Carter [Samba-Team] <[EMAIL PROTECTED]> Summary : Samba SMB client and server - NEW RPM PACKAGE - $ rpm -qpi ./samba-3.0.10-1_rh9.i386.rpm Name: sambaRelocations: /usr Version : 3.0.10Vendor: Samba Team Release : 1 Build Date: Wed 15 Dec 2004 02:04:19 PM PST Install date: (not installed) Build Host: rh9 Group : NetworkingSource RPM: samba-3.0.10-1.src.rpm Size: 45453218 License: GNU GPL version 2 Packager: Gerald Carter [Samba-Team] <[EMAIL PROTECTED]> Summary : Samba SMB client and server - smb.conf file - [global] netbios name = *removed* workgroup = *removed* preferred master = yes domain master = yes wins support = yes os level = 85 encrypt passwords = yes interfaces = eth0 hosts allow = *removed* invalid users = bin daemon adm sync shutdown logon path = logon drive = U: logon script = logon-%G.bat add machine script = /usr/sbin/useradd -d /dev/null -s /bin/false -c 'Machine Account' -M %u admin users = @smbadmin printer admin = @smbadmin domain logons = Yes min protocol = NT1 [homes] comment = User Directory path = /usr/export/home/%U read only = NO browseable = NO # only user = %S [netlogon] comment = Network Logon Service path = /etc/samba/netlogon guest ok = yes browseable = no [print$] path = /var/samba/printers write list = @smbadmin guest ok = yes [printers] comment = All Printers path = /tmp guest ok = Yes printable = yes printing = lprng browseable = No If you are going from a Red Hat supplied Samba release to one released by samba.org various things will be in different places. /etc/samba/ will remain the same however and your config files should translate over. Also keep in mind that Red Hat has split it's Samba package into three groups (samba, samba-client, samba-common). My advice is to remove all of your existing samba packages (backing up your config files of course) and then doing a clean install if this is the case. Christian -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Upgrade...
Sorry if this is a dup. I sent right before I subscribed to the list, so I'm not sure if it made it. I have just taken over a redhat system with Samba 3.0.0 configured with security = user, and domain logins enabled. I've included the smb.conf at the end of this message. I would like to upgrade to 3.0.10 for a numbers of reasons, one being security and one being that password changes don't work from workstation machines because of the Windows KB828741 patch. What I want to know, is if I should expect any incompatibilities between versions or if my existing config files will work with the new version? This is a mission critical system, so I really don't want to upgrade unless there are going to be very minimal issues. Will a simple rpm -Uvh ./samba-3.0.10-1_rh9.i386.rpm put me in the clear? Thanks for your help. Here is some information about the system: - OLD RPM PACKAGE - $ rpm -qi samba Name: sambaRelocations: /usr Version : 3.0.0 Vendor: (none) Release : 2 Build Date: Thu 09 Oct 2003 05:12:20 PM PDT Install date: Sat 11 Oct 2003 10:41:04 PM PDT Build Host: *removed* Group : NetworkingSource RPM: samba-3.0.0-2.src.rpm Size: 46416163 License: GNU GPL version 2 Packager: Gerald Carter [Samba-Team] <[EMAIL PROTECTED]> Summary : Samba SMB client and server - NEW RPM PACKAGE - $ rpm -qpi ./samba-3.0.10-1_rh9.i386.rpm Name: sambaRelocations: /usr Version : 3.0.10Vendor: Samba Team Release : 1 Build Date: Wed 15 Dec 2004 02:04:19 PM PST Install date: (not installed) Build Host: rh9 Group : NetworkingSource RPM: samba-3.0.10-1.src.rpm Size: 45453218 License: GNU GPL version 2 Packager: Gerald Carter [Samba-Team] <[EMAIL PROTECTED]> Summary : Samba SMB client and server - smb.conf file - [global] netbios name = *removed* workgroup = *removed* preferred master = yes domain master = yes wins support = yes os level = 85 encrypt passwords = yes interfaces = eth0 hosts allow = *removed* invalid users = bin daemon adm sync shutdown logon path = logon drive = U: logon script = logon-%G.bat add machine script = /usr/sbin/useradd -d /dev/null -s /bin/false -c 'Machine Account' -M %u admin users = @smbadmin printer admin = @smbadmin domain logons = Yes min protocol = NT1 [homes] comment = User Directory path = /usr/export/home/%U read only = NO browseable = NO # only user = %S [netlogon] comment = Network Logon Service path = /etc/samba/netlogon guest ok = yes browseable = no [print$] path = /var/samba/printers write list = @smbadmin guest ok = yes [printers] comment = All Printers path = /tmp guest ok = Yes printable = yes printing = lprng browseable = No -- Brent Smith <[EMAIL PROTECTED]> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Upgrade
Hi guys! I have a samba 3.0.5pre1 installed in my system and using openldap 2.2.13 and it's working OK except for the annoying desktop.ini popping up everytime an ordinary logs on. Now what I want is to uprade Samba to a stable release like 3.0.7? but Im worried that there may be issues that I should be aware of. Im asking anyone who may provide with the specifics on how to go about the upgrade process and the things that should consider. Thanks in advance Jan - Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba upgrade
I noticed v 3.05 came out with some security fixes. I'm still using v 3.0.0 and it seems to work just fine. I've never done an upgrade on Samba which I'd like to do by the end of the summer. I've already upgraded the backend support, OpenLDAP and Berkeley DB. What do I need to backup before compiling and installing a new version besides smb.conf? All my accounts are in LDAP. Kent N -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Upgrade
If you could find a spare server box somewhere, it is always nice to have the luxury of building a test machine to trial a new system before finally pulling the plug on a reliable known-to-work system. AFAIK samba 3.0.4 is the latest stable version, most new distros now include it (eg Slackware 10 which was released a couple of weeks back). If you're going to upgrade, you may as well go for the latest stable version as a general rule. Michael Hall On Tue, 2004-07-20 at 15:14, Nik Trevallyn-Jones wrote: > Hi Folks, > > I would really appreciate any words of wisdom people here could provide me. > > I have Samba 2.2.7a, as shipped with RH 9.0, running on a server, supporting > about 25 W2k clients. The linux kernel is running in SMP mode to use the > Hyper-Threaded Pentium-4 CPU. I have tried to create the simplest SAMBA setup > possible, so have no LDAP, ACLS, etc. The 25 w2k clients are all architects > running CAD software and working on a major building design, so I cannot > afford down time, nor unexpected server behaviour. The 2.2.7a Samba has been > the epitome of reliability and efficiency. > > However, I really need to enable recycle bins, to better recover accidentally > deleted files. I have tried to enable the recycle VFO in 2.2.7a, but with no > success, so I am considering upgrading to Samba 3.x. > > My current plan is to shut down the SAMBA services, backup the /etc/samba > directory, uninstall samba 2.2.7, install SAMBA 3.x, copy my /etc/samba back > in, and restart samba. > > Q: Is there any advice that people would offer me on this? > > Q: Is there a particular version of Samba that I should upgrade to in > preference to others? > > Q: Is there a simple HOW-TO on the recycle-bin VFO for 2.2.7? > > Q: Are there any additional procedures I should employ in the upgrade? > > Thanks in advance for any and all advice. > > Cheers! > Nik -- -- Ninti Systems: Smart IT Solutions Michael Hall Mobile: 0429 095 392 Ph/Fax: 08 8953 1442 Email: office at ninti dot com dot au Web:http://ninti.com.au -- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Upgrade
Hi Folks, I would really appreciate any words of wisdom people here could provide me. I have Samba 2.2.7a, as shipped with RH 9.0, running on a server, supporting about 25 W2k clients. The linux kernel is running in SMP mode to use the Hyper-Threaded Pentium-4 CPU. I have tried to create the simplest SAMBA setup possible, so have no LDAP, ACLS, etc. The 25 w2k clients are all architects running CAD software and working on a major building design, so I cannot afford down time, nor unexpected server behaviour. The 2.2.7a Samba has been the epitome of reliability and efficiency. However, I really need to enable recycle bins, to better recover accidentally deleted files. I have tried to enable the recycle VFO in 2.2.7a, but with no success, so I am considering upgrading to Samba 3.x. My current plan is to shut down the SAMBA services, backup the /etc/samba directory, uninstall samba 2.2.7, install SAMBA 3.x, copy my /etc/samba back in, and restart samba. Q: Is there any advice that people would offer me on this? Q: Is there a particular version of Samba that I should upgrade to in preference to others? Q: Is there a simple HOW-TO on the recycle-bin VFO for 2.2.7? Q: Are there any additional procedures I should employ in the upgrade? Thanks in advance for any and all advice. Cheers! Nik -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba upgrade on dedrat linux
On Tue, 23 Sep 2003, Andre de Koning wrote: > I'm running samba 2.2.5 on a redhat 9.0 server. I'm planning on upgrading > it to 2.2.8a tomorrow. > > My questions are thus: > 1) I has hassles before when doing this on another redhat box because samba > was installed with redhat's own rpm's which install in different locations. > Would it be OK to do rpm --erase for all the redhat packages (samba, common, > client, swat, redhat-config-samba) and then just do a normal rpm -i with the > samba-2.2.8a package from the samba d/l server? I made the mistake of doing > rpm -Uvh last time which of course told me it was not installed so I > did --force etc. BIG mess. You really should build the Red Hat packages using the tools we provide in the ~samba/packaging directory. It will ensure that your file locations will match the Red Hat native package file locations. > 2) What do I need to back up? smb.conf, smbpasswd, what else? This is a > seperate server at a remote branch so it's not using ldap yet. Any .tdb or > .SID files I need to backup? If you install the Samba-Team provided RPMs your configuration should be preserved. None the less, it is ALWAYS a good idea to backup config files. Save all tdb files as well as your smb.conf. > 3) How do I backup the SID (on old versions it was just MACHINE.SID but I > believe you do this via smbpasswd now)? And how would I restore it again > after reinstalling? Read the man page for smbpasswd (for samba-2.2.x) or the man page for 'net' (for Samba-3.0.0). > 4) Would my smb.conf still work without changes? Should do. > > It's not a DC, just a member server but I've got a script that copies > passwd, group, shadow, gshadow and smbpasswd accross from their pdc every > 30min - would this still be ok? > Any other pointers would be appreciated. If you plan to update to Samba-3.0.0 (good idea), read the Samba-HOWTO-Collection.pdf that shipped as part of samba-3.0.0RC4. - John T. > André de Koning > IT Manager (Chief computer mechanic) > Softline VIP Payroll > Tel: +27 12 420 7000 > [EMAIL PROTECTED] > > -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba upgrade on dedrat linux
I'm running samba 2.2.5 on a redhat 9.0 server. I'm planning on upgrading it to 2.2.8a tomorrow. My questions are thus: 1) I has hassles before when doing this on another redhat box because samba was installed with redhat's own rpm's which install in different locations. Would it be OK to do rpm --erase for all the redhat packages (samba, common, client, swat, redhat-config-samba) and then just do a normal rpm -i with the samba-2.2.8a package from the samba d/l server? I made the mistake of doing rpm -Uvh last time which of course told me it was not installed so I did --force etc. BIG mess. 2) What do I need to back up? smb.conf, smbpasswd, what else? This is a seperate server at a remote branch so it's not using ldap yet. Any .tdb or .SID files I need to backup? 3) How do I backup the SID (on old versions it was just MACHINE.SID but I believe you do this via smbpasswd now)? And how would I restore it again after reinstalling? 4) Would my smb.conf still work without changes? It's not a DC, just a member server but I've got a script that copies passwd, group, shadow, gshadow and smbpasswd accross from their pdc every 30min - would this still be ok? Any other pointers would be appreciated. André de Koning IT Manager (Chief computer mechanic) Softline VIP Payroll Tel: +27 12 420 7000 [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] SAMBA Upgrade
Currently I am running SAMBA 2.2.2 on my Solaris 8 server locally, I wanted to upgrade to SAMBA 2.2.8a. I want to know how I can do this, and are there any issues with upgrading. SAMBA 2.2.8a is a patch correct ? Any help is greatly appreciated, thanks. Huzefa "ZAK"ir IT Systems Engineer CONFIDENTIALITY NOTICE: The information contained in this ELECTRONIC MAIL transmission is confidential. It may also be privileged work product or proprietary information. This information is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution [other than to the addressee(s)], copying or taking of any action because of this information is strictly prohibited. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba upgrade and NT domain membership
Hi all, I have a number of Samba servers that are members of an NT domain (i.e. the PDC/BDC runs NT.) This works fine until I need to upgrade Samba - then it loses it's membership of the domain. (I take a copy of the current Samba directory and install the new version over the top so that the secrets.tdb file etc. are retained.) The only way I found to restore the domain membership is to delete the Samba server from the domain on the PDC and add it back again, then run "smbpasswd -j " on the Samba server. Is there a way to keep the previous domain membership across an upgrade? Failing that, is there a simpler way to restore the domain membership? (Preferably without needing access to the PDC.) Thanks in advance. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Paul Taylor [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba upgrade
> From: "Norman Zhang" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Date: Fri, 20 Dec 2002 15:09:53 -0800 > Subject: [Samba] samba upgrade > > Hi, > > LM 9.0 (samba 2.2.6) can setup to authenticate using winbind. When I do > wbinfo -u, only > users of my NT domain is listed, > > e.g., > user_a > user_b > ... > > Now I upgrade to 2.2.7 using Mandrake update, and wbinfo -u, I see > > e.g., > MYDOMAIN\user_a It works here for me (testing agianst a samba3alpha21 DC). But I am not running the official update packages, I had 2.2.7-5mdk, and now using 2.2.7a-1mdk, which you can find at http:/ranger.dnsalias.com/mandrake/samba , new updates to 2.2.7a should be available soon. The parameter you need is "winbind use default domain = yes". I normally update via urpmi, instead of MandrakeUpdate, the update shouldn't have messed with your configuration ... Regards, Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] samba upgrade
Hi, LM 9.0 (samba 2.2.6) can setup to authenticate using winbind. When I do wbinfo -u, only users of my NT domain is listed, e.g., user_a user_b ... Now I upgrade to 2.2.7 using Mandrake update, and wbinfo -u, I see e.g., MYDOMAIN\user_a MYDOMAIN\user_b ... Which option in smb.conf can I suppress the printing of MYDOMAIN? Regards, Norman -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba upgrade questions - resent *with* subject...
Hello, Samba user folks :) I have a few very likely newbie questions: 1. I installed Samba 2.2.6 from sources and I don't seem to have smbclient or nmblookup. Did I goof somewhere and forget something that would have included them? 2. I am curious about upgrading samba via CVS - I've looked at the instructions and it seems pretty straightforward. Is there anything to watch out for as far as updating Samba files while the smbd is running? 3. Windows has this nasty (okay, it's actually a decent thing - if you could turn it off...) where it creates a brand new profile if you join a new domain - even if that new domain has the exact same name. Will upgrading the Samba files trigger this behavior? I'm thinking not, but after the havoc this caused after the switch from NT to Linux - along with the unexpected "gift" of Win2K autmatically creating roaming profiles (which it had never done before when connecting to a new Windows domain), I am, I believe, rightly paranoid about all this. Many thanks in advance, /===\ | Michael Luevane +| | System Administrator + mikel @ quantec llc . com| | Quantec, LLC + www.quantecllc.com | | 503-228-2992 +| \===/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA upgrade
On Sun, 2002-10-20 at 20:53, Jennifer Crusade wrote: > Hello, > > I have downloaded the 2.2.6 tar file for Samba and followed all of the > procedures and all works as far as the make and make install but it does not > run off of the latested install. I ran a script that is suppoesed to link > it to the proper path but to no avail. How can I make this work. My > original install is in the /etc/samba but the new one goes into > /usr/local/bin/. How can I either make it run from the new location or > change the default install path? I'd recommend using a binary package for your operating system... If you want to compile and install from the sourceball you need to learn how to use the ./configure --help to understand what all the various options do... For example you can tell samba where to keep various things (logs, variable data, etc.) brad -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] SAMBA upgrade
Hello, I have downloaded the 2.2.6 tar file for Samba and followed all of the procedures and all works as far as the make and make install but it does not run off of the latested install. I ran a script that is suppoesed to link it to the proper path but to no avail. How can I make this work. My original install is in the /etc/samba but the new one goes into /usr/local/bin/. How can I either make it run from the new location or change the default install path? Jennifer Crusade GTESS Corp. CCNA, MCSE W2k\NT 4.0, MCP +I -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Upgrade
Title: Message Is there documentation that I can download or does someone have a procedure for upgrading my current version of Samba to the latest version? Or is it best to uninstall the current version and re-install the latest? Pati Moss Unix Systems Administrator First Consulting Group, Inc. http://www.fcg.com Phone: (610) 989-7105 Fax: (610) 989-3207 [EMAIL PROTECTED]
[Samba] Samba Upgrade Weirdness
Hi all, I'm trying to upgrade Samba from v2.2.1a-4 to 2.2.4-2 and I've having some problems. First off when trying to use the rpm -U command I get an error that samba is dependant on samba-swat (which I cant seem to find the same version as sambe for) so I decide to remove both the existing Samba and Samba swat and then install the new one. I uninstall both of them but then while trying to install the new version I get error saying that there are conflicts with files from the older version (which should no longer be there). I confirm the files are present so I remove them manually (rpm confirms the packages are no longer installed) however when trying to install the new version again I still get an error that there are conflicts with the older files I just manually deleted. I'm pulling my hair out over this, can anyone tell me what I'm doing wrong? Cheers Ash -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
