Everyone, I upgraded Solaris 2.6 box running Samba 2.0.4 to a Solaris 7 with a new version of Samba 2.0.6 I used all my old smb.conf files on this new server and now I can see the server but when you try to connec to it is give the message " Not accessable " Unexpected network error occured" Thanks for any help getting this figured out it must be some thing small I am missing Jon Crabtree IRSS UNC CHAPEL HILL
Hey quick question: I just upgraded Samba 2.05a to 2.06-9, from the Red Hat RPM. The upgrade created /etc/smb.conf.rpmnew and /etc/smb.conf.rpmsave and erased /etc/smb.conf. Do I still need a smb.conf file? I havent checked out your latest updates, so I figured I'd ask. Either way I still copied the rpmsave to /etc/smb.conf b/c I figured it still needs to be there.
On Wed, 13 Sep 2000, Gerry Maddock wrote:> Hey quick question: I just upgraded Samba 2.05a to 2.06-9, from the Red > Hat RPM. The upgrade created /etc/smb.conf.rpmnew and > /etc/smb.conf.rpmsave and erased /etc/smb.conf. Do I still need a > smb.conf file? I havent checked out your latest updates, so I figured > I'd ask. Either way I still copied the rpmsave to /etc/smb.conf b/c I > figured it still needs to be there.I think that this is an RPM question, rather than a Samba question. You do still need an smb.conf file. I think that RPM has detected that you had customised your smb.conf, and didn't want to overwrite it with the new smb.conf that it would normally have installed. Ideally you need to merge your personal changes back into the new RedHat smb.conf, I think (though, chances are, you could probably just re-install /etc/smb.conf.rpmsave as /etc/smb.conf). Regards, -- Neil Hoggarth Departmental Computer Officer <neil.hoggarth@physiol.ox.ac.uk> Laboratory of Physiology http://www.physiol.ox.ac.uk/~njh/ University of Oxford, UK
Hi i have just installed samba-2.2.1a and I ma getting the following Error failed to open byte range locking database when i run smbstatus Regards Keith
On Wed, 31 Oct 2001 keith.nyabako@nds.group-services.com wrote:> Hi i have just installed samba-2.2.1a and I ma getting the following > > Error failed to open byte range locking database when i run smbstatusI think this was fixed between 2.2.1a and 2.2.2 cheers, jerry> > Regards > > Keith > > >-- --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca--
I have a redhat 6.0 server that has a old version of samba running. Now i want to upgrade to the latest version. Can i just remove de samba directory and install the new version or is there a certain procedure i have to follow? The old version is installed by someone else and is probebly created from sourcecode. The samba files are found in /usr/local/samba . The new version is a RPM binary package wich i downloaded from a mirror. I installed this binary RPM package on another redhat 6.0 server and the samba files were installed in a different directory (as they should propably). Everything works allright. I want to install this package also on the other server but first i want to remove the old one. Can anyone answer my question? Regards, Pieter
I have a redhat 6.0 server that has a old version of samba running. Now i want to upgrade to the latest version. Can i just remove de samba directory and install the new version or is there a certain procedure i have to follow? The old version is installed by someone else and is probebly created from sourcecode. The samba files are found in /usr/local/samba . The new version is a RPM binary package wich i downloaded from a mirror. I installed this binary RPM package on another redhat 6.0 server and the samba files were installed in a different directory (as they should propably). Everything works allright. I want to install this package also on the other server but first i want to remove the old one. Can anyone answer my question? Regards, Pieter
I have a redhat 6.0 server that has a old version of samba running. Now i want to upgrade to the latest version. Can i just remove de samba directory and install the new version or is there a certain procedure i have to follow? The old version is installed by someone else and is probebly created from sourcecode. The samba files are found in /usr/local/samba . The new version is a RPM binary package wich i downloaded from a mirror. I installed this binary RPM package on another redhat 6.0 server and the samba files were installed in a different directory (as they should propably). Everything works allright. I want to install this package also on the other server but first i want to remove the old one. Can anyone answer my question? Regards, Pieter
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 <http://www.fcg.com/> Phone: (610) 989-7105 Fax: (610) 989-3207 pmoss@fcg.com <mailto:pmoss@fcg.com> -------------- next part -------------- HTML attachment scrubbed and removed
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
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
> From: "Norman Zhang" <nzhang@arkon-group.com> > To: <samba@lists.samba.org> > 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_aIt 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 Milne Mechanical 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
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. ************************************************************************