Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Olle Maartensson on May 07, 2001, 01:28:51 PM
-
Hi!
Here's a way to get Win2k clients to login to a E-smith PDC.
1.Download Samba2.20
http://se.samba.org/samba/ftp/Binary_Packages/redhat/RPMS/7.0/samba-2.2.0-20010417.i386.rpm.
2.Install the new version by running"rpm -i --force samba-2.2.0-20010417.i386.rpm"
I'm sure theres alot of better ways to do this, all I know is when you do a regular "rpm -i filename" the e-smith complains about conflicting files.
3.Reboot the system
4.The first thing I noticed was that the users samba passwords settings were gone so I guess we have to update the samba passwd file. Enter the E-smith-Manager, enter "user accounts" and then do a reset password for all users.
5.As far as I noticed e-smiths templates solution didn't apply to our new samba version so, changes to the smb.conf file has to be made in /etc/smb.conf
6.Create a UNIX user account for the win2k machine account " useradd -c 'win2k workstation' -M -s /bin/false -n workstationname$"
7.When the win2k workstation asks for a user with permissions to join you to the domain the root account has to be created for samba.
Add root to the smbpasswd file:
"smbpasswd -add root"
Changing root password in smbpasswd:
"smbpasswd root"
Enable the user root account:
"smbpasswd -e root"
8. On the win2k client logon as the Administrator, right click the My Computer Icon and select properties from the popup menu, select the Network Identifications tab and click the properties button and change the settings to join your domain.
After a while you will be asked to enter a name and a password of a user with permissions to join the domain, use the root account we created earlier.
9.Thats It! The sweet "WELCOME TO THE YOURDOMAN DOMAIN" message should appear if everything wen't your way.
Note! This is not a professional way of doing things, but I had nothing to lose when I decided to brutally --force the new samba version into e-smith. I suggest that you do this in a test enviorment where you have absolutely nothing to lose.
Best of luck // Olle Maartensson // SWEDEN
-
Well, I can't get it working. Perhaps it's because i didn't do rpm -i --force
but did rpm -e --nodeps samba samba-common before.
It always reports that I'm using a wrong useraccount...
Both password and usernamen are fine - tried with the root account and one that I've created with e-smith-manager.
Any suggestions?
David
-
I tried to log on to the e-smith server after updating SAMBA.
I only got the message:
The account user is a computer account, Use your global or local user account to access the server.
What should I do?
I use my account I also used with Windows 98 before switching to W2k.
-
To join the domain yo must use the root account
After you put the workstation in the domain using the root account
you can logon using the account created on the e-smith admin
I had a prblem setting the samba root password because it was disbaled, there is a D after the password in smbpasswd file remove this an all
works fine I still have some problem saving user preferences.
For better description see
http://it.samba.org/samba/docs/Samba-HOWTO-Collection.html#AEN760
Bye
Lorenzo
-
btw make sure you join any w2k machine up to your samba pdc _before_ applying service pack2.
As long as you've previously joined the domain before applying sp2 you'll be fine, otherwise you'll need to wait for a samba update that addresses the rpc change sp2 makes on win2k.
--
Damien
-
I tried this and when I go to join the domain I get the message "the procedure number is out of range'. any help...
-
I followed your instructions but I used a WinXP workstation in stead of a Win2k workstation. Also I used version 2.2.5 of Samba. When I try to add the workstation to my domain I get the following error message:
"Computer Name Changes
The following error occured attempting to join the domain "ESMITH":
Multiple connections to a server or shared resource by the same user, using more then one username, are not allowed. Disconnect all previous connections to the server or shared resource and try again.."
Is this a WinXP issue and how can I solve it?
Kees Pimpelmees
-
To get your Windows Client to a domain, you must remove it from the domain and make it part of a windows workgroup. Reboot and then add the client to the domain again.
sqlerror