Configuring Windows XP client to login to Directory Server account

  • Thread starter Thread starter kingrob
  • Start date Start date
K

kingrob

Guest
Ok, this one has got me scratching my head.

I have installed CentOS Directory Server on a server, created user accounts and now want them to login with their XP laptops to the server.

As I understand it, it's as simple as changing the network ID in Windows XP, or joining a domain and put in the directory server details....and all seems good until Windows complain that it does not have a computer account in the domain.

Now where on the directory server do you create a computer account???

Was thinking of creating a new group, name it computers and add the client's hostname to the group, but does not seem to work.

I need your help, please!
 
Look in the /docs for samba, there's a whole howto tutorial to setup AD.
 
Its been a long while since I have done this. But you should be able to "join domain" from the windows box. This will create an entry on you server although you still will need to setup the credential etc. on the server but atleast you will have a starting point.

Make sure your time is sync'ed perfectly as Kerberos is pedantic about time and will through wierd and wonderful non-descript errors.
 
IIRC it's only xp pro which can join domains, xp home cannot.

The client is XP Pro.....goes without saying. :)

But Samba is for shares, I just need the 389 Directory Server to authenticate users and run login scripts.
 
+ Samba needs a Windows server to do its magic.

We dont have a Windows server on our network. :)
 
Nope SAMBA does not require a windows box do its "magic" you need slapd backend which 389 Directory Server does as well as specify the Kerberos domain. For a working AD replacement you need a LDAP, Kerberos and SAMBA which handles the roaming profiles etc. All of which is in 389 already.

When you do a network scan scan in 'doze do yo at least see the domain controller you setup?
 
When you do a network scan scan in 'doze do yo at least see the domain controller you setup?

Think you have nailed the problem.

I had to add the 389 server to the XP client's host file, otherwise the XP client cannot ping the server. Both are on the same subnet & switch. :)
 
I'm in! Got it working. Woohoo!

Most important was to go into Windows User Accounts, advanced user info and create user account for login to the CentOS server. Very interesting.
 
Top
Sign up to the MyBroadband newsletter
X