LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Samba Problem after upgrading (https://www.linuxquestions.org/questions/slackware-14/samba-problem-after-upgrading-816330/)

Manuel-H 06-25-2010 07:54 AM

Samba Problem after upgrading
 
Hi,

I need some expert advice here regarding the samba problem after upgrading. All data migrated with the appropriate permission.
I transfered the /etc/passwd, /etc/shadow and /etc/samba/* files to the new server.

Previous working version (Slackware v11 - 32bits - Old Hardware)
- samba-3.0.25a-i486-1_slack11.0
- XP Pro users are able to login and authenticate (NT DOMAIN)
- Login script and file sharing with permission are okay too

Upgraded to (Slackware 13.1 64bits - New hardware)
- samba-3.5.2-x86_64-1
- if the PC did not logoff, the file sharing and permission works fine.
- If they logoff, they will not able to re-logon.
- If I detach the PC from domain and then rejoin domain, I will be able to login to the domain, So I guess the samba configuration is working

I read it has to do with Machine Trust Account or something.

Questions:
- Can I convert or make samba 3.5 recognize the Machine Trust Account on the new hardware?
- How can I check if the if the entry is successfully registered as machine trust account?
I checked and found the 'machinename$' (example) in all three places /etc/passwd, /etc/shadow and /etc/samba/private/passdb.tdb
I see no differences on the one PC that I unjoin and rejoin the domain versus those old domain name join to the old hardware.

Any help would be very much appreciated.
Note: I will continue to google and try to find the solution.
Hope someone can help me and save me some time :)

Thanks.

el_jauzaa 06-26-2010 11:33 PM

Quote:

Originally Posted by Manuel-H (Post 4014694)
Hi,

I need some expert advice here regarding the samba problem after upgrading. All data migrated with the appropriate permission.
I transfered the /etc/passwd, /etc/shadow and /etc/samba/* files to the new server.

Previous working version (Slackware v11 - 32bits - Old Hardware)
- samba-3.0.25a-i486-1_slack11.0
- XP Pro users are able to login and authenticate (NT DOMAIN)
- Login script and file sharing with permission are okay too

Upgraded to (Slackware 13.1 64bits - New hardware)
- samba-3.5.2-x86_64-1
- if the PC did not logoff, the file sharing and permission works fine.
- If they logoff, they will not able to re-logon.
- If I detach the PC from domain and then rejoin domain, I will be able to login to the domain, So I guess the samba configuration is working

I read it has to do with Machine Trust Account or something.

Questions:
- Can I convert or make samba 3.5 recognize the Machine Trust Account on the new hardware?
- How can I check if the if the entry is successfully registered as machine trust account?
I checked and found the 'machinename$' (example) in all three places /etc/passwd, /etc/shadow and /etc/samba/private/passdb.tdb
I see no differences on the one PC that I unjoin and rejoin the domain versus those old domain name join to the old hardware.

Any help would be very much appreciated.
Note: I will continue to google and try to find the solution.
Hope someone can help me and save me some time :)

Thanks.

did you already update samba with samba-3.5.3-i486-1.txz?


All times are GMT -5. The time now is 06:31 AM.