samba - Mar 2002 - Samba Upgrade question

I am a nubie to linux.  I have a Redhat Linux 7.2 server running Samba
2.2.1a-4.  How would I upgrade it to Samba 2.2.3a?  I am also having
problems with connecting to a W2K SP2 pdc using security=domain.  Passwords
are encrypted.  I get the error: NT_STATUS_WRONG_PASSWORD.  Would upgrading
to 2.2.3a solve that problem?

Thanks,
Kevin Bramblett

Hi
whats the best way to upgrade samba, am currently running 2.0.7 and would
like to upgrade to 2.2.5, 
the machine account is now moved to secrets.tdb, can i simply move the
existing machine SID to private directory in new version
or i have delete the old one and and rejoin samba again
thanks in advance

Hi 

Am about to upgrade samba227a to 228a on solaris boxes.

In the past I have copied secrets.tdb from private dir to updgraded version
private dir.

I was just curious every time I upgrade, do I need to rejoin the samba to
domain, which creates secrets.tdb or using a old copy is harmless.

Thanks in advance

-

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 24 Apr 2003, Javid Abdul-AJAVID1 wrote:
> Am about to upgrade samba227a to 228a on solaris boxes.
> 
> In the past I have copied secrets.tdb from private dir to updgraded version
> private dir.
> 
> I was just curious every time I upgrade, do I need to rejoin the samba to
> domain, which creates secrets.tdb or using a old copy is harmless.
The copy should be fine.




cheers, jerry
 ----------------------------------------------------------------------
 Hewlett-Packard            ------------------------- http://www.hp.com
 SAMBA Team                 ---------------------- http://www.samba.org
 GnuPG Key                  ---- http://www.plainjoe.org/gpg_public.asc
 "You can never go home again, Oatman, but I guess you can shop
there."
                            --John Cusack - "Grosse Point Blank"
(1997)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE+qUWZIR7qMdg1EfYRAs+RAKCUQiRhxYPfRmaNrwuLcNCEHnX9TwCgzTEL
2m0JVA0GcLBgOspHjmvBaDw=qYWk
-----END PGP SIGNATURE-----