Topic: No windows login after change of password

[JensK]

suddently I am not able to do a windows login to my e-smith 6 final version after change of password. The problem started under 6b3, I upgraded to 6 final but the problem persists.

I use the SME as a domain controller in my home network to the family with roaming profiles for my 3 win2k SP2 workstations.

The users that doesn't change password can still login to the SME-domain. Users that have changed password or newly created users can't login. The problem is the same from all three win2k boxes so i asume that it's a SME 6 that has the error.

I have tried to disable/enable the failing user accounts. I have changed the passwords several times but nothing helps.

In desperation i am doing a full backup of the server and planning to reinstall it but I am afraid that this will leave me with no users that can login at all. My familiy is going to kill me if the can't use the network during christmas.

SOS
JensK

[ryan]

You might do a search...this has been discussed....

My post to an older discussion:

It should be noted that if you upgrade to 6.0, all your XP and 2k systems will 'cut off' from the domain. If the user has logged in prior to the 6.0 upgrade, they can login using the cached profile (this is allowed 10 times by default). If a new account is created on SME 6, that user can't log in. This is a serious problem as it will bring down an entire site in due time if SME is a PDC.

I was able to get the systems to rejoin the domain after putting them in a workgroup. I realized you can not change the system name when you attempt to join the domain or you will get the known user error.

I did this in a test environment with 2 fresh machines..one 2k, the other XP. Both w/ all service/security fixes. I joined them to a fresh SME 5.6u6 server. I then upgraded the SME server to 6.0. They then lost contact. Is this due to a newer samba version? I can't believe a bug this serious made it to final. I guess this final is should be 6.0dumpped instead of 6.0final. If I had applied this upgrade in a production environment, I would have spent hours if not days redoing each client membership.

My webmail also no longer works on the test server. The fixes in the forum allow me to log in, but the Memo, Calendar, and contacts crap out with an error.

SME 6.0 SHOULD BE THOURGHLY TESTED. YOU MIGHT BE SURPRISED WHEN YOU LEARN WHAT WILL BREAK IF AFTER UPGRADING.

I think I will wait to see if SME survives and adopts a new distro before upgrading my 5.6 servers in production. Did 6.0b3 have these issues? What changed? Anyone find a good replacement for SME 5.6...or will this community pull through these problems?


ryan

[Ianluis]

I haven't worked with SME V6, but you might want to check the passwords at the workstations too. Just make them the same, I know for fact you don't need to do it but don't have any suggestions at all other that get back to 5.6.....
Luck....

[JensK]

I tried Ryans remedy. I have made the workstations member of workgroup in stead of domain, I changed the workstation name. Changed the name of the domain i SME. Reconnected the workstation to the new domain.

I have two problem left. My users dosn't seem to be superusers allthough mu sme domain users are made members of the windows group Superusers. Also is seems like my netlogon script  dosn't work. The script is in netlogon.bat in the users homedir but it doesn't get run at login. If run manually it maps drives and printers sets time as expected. I use e-smith-loginscript-0.2-2.noarch.rpm.

I am thinking that everything would be easier if I reinstalled the old sme 5.6. The alternative would to scratch the server and install the 6 final. Does anybody know hov to use the logins scripts without e-smith-loginscript-0.2-2.noarch.rpm.

Has anybody sme 6 final up and running as a domain controller in a win network with roaming profiles and working netlogon.bat and the users as Windows superusers?
Jens

[ryan]

In the past, it was stated in the forums that the netlogin scripts would be wiped when upgrading to SME 5.6.  

On 5.6, the login script is here (no loginscript.rpm):

\home\netlogin\netlogin.bat

Simply edit this file if you can use a single loginscript for all clients.

ryan

[JensK]

Hi Ryan.
Thanks for the information about the login scripting. Do you have any hints about my problem with the user not getting superusers rights allthough they are members of the superusers group in win2k sp2?

Ryan are you using 6 final yourself or are you using 5.6?
Jens

[ryan]

Jens,

Do a author search for "ryan".  I recently wrote a long posting on this topic.  To answer your question, yes you can avoid the users having admin privs...it is a qiuck and easy fix.

Let me know if you find the posting and if it helps.

I am on 5.6 and don't plan to upgrade soon as the current 6.0 final iso will break 5.6 samba and webmail.  I am glad I took time to set up a test lan with XP & 2k to test the 6.0 upgrade...this saved me lots of time (unbillable time).  

Since this forum plans to stay with the rh 7.3 base into 2004,  I don't see a need to use 6.0 as both are rh7.3.  Hopefully the gurus will agree on a different GNU distro and begin converting E-smith.  

Anyone know the status on the samba & webmail bugs?  Can the contribs.orgmunity fix and post a new 6.0 iso, or am I being unrealistic?  I really like the new server-manager interface.

ryan

[JensK]

Hi Ryan.
Thank you for your help. I am now up and running the 6 final release. Part of my problem was corrupt roaming profiles. I have restored alle suer to a default win profile and everything works ok.

Now I need to get an overview over the rpms for the version 6. Is there a listing over theese rpms? I have ssen several postings over this but no answers.

My special interest is a CMS. Before my 6 final upgrade I had a test site running plone. After the upgrade I can't get it to run anymore so i am looking for a new CMS that works with sme 6 final
/jens

[Nathan Price]

Have you submitted the bugs that you found to the bugs phorum?  If not please do that way they will know about them and perhaps try to fix them otherwise they may never get fixed.

-N