Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: 1 [2]
16
Installation and Upgrades / Re: eBox 1.3 - Samba PDC
« on: November 19, 2009, 12:00:19 am »
Sure, i can do that if my time permits. Tomorrow I will be in another job. As soon as i am done with that, i will join the irc channel.
17
Installation and Upgrades / Re: eBox 1.3 - Samba PDC
« on: November 18, 2009, 10:09:55 pm »
javi,
the SAMBA domain name is "SMBDOMAIN", the netbios name is "server".
The user i tried to join the domain with had admin rights enabled.
the SAMBA domain name is "SMBDOMAIN", the netbios name is "server".
The user i tried to join the domain with had admin rights enabled.
18
Installation and Upgrades / Re: eBox 1.3 - Samba PDC
« on: November 18, 2009, 08:59:42 pm »
J. A. Calvo,
no, i didn't change the domain name either. I reproduced the situation three times in Virtualbox with all machines setup from scratch each time.
Out of curiosity/frustration, I installed another setup with the LDAP and the samba server on the same machine an hour ago. Well, that works!
Is this going to be a supported scenario? As i said in an earlier post, that would be exactly what i am looking for.
So there's definitely something funny going on with the LDAP server being on a dedicated machine. Somehow, the Samba slave can't access the user information in the tree. Or maybe it has something to do with the internal networking option of Virtualbox?
I will investigate further
no, i didn't change the domain name either. I reproduced the situation three times in Virtualbox with all machines setup from scratch each time.
Out of curiosity/frustration, I installed another setup with the LDAP and the samba server on the same machine an hour ago. Well, that works!
Is this going to be a supported scenario? As i said in an earlier post, that would be exactly what i am looking for.
So there's definitely something funny going on with the LDAP server being on a dedicated machine. Somehow, the Samba slave can't access the user information in the tree. Or maybe it has something to do with the internal networking option of Virtualbox?
I will investigate further
19
Installation and Upgrades / Re: eBox 1.3 - Samba PDC
« on: November 18, 2009, 06:38:00 pm »
Hey, thanks for the tip dragonslayr! I will check that out and see if it is of any help.
Though the IP addresses of the machines were not changed during the test.
Though the IP addresses of the machines were not changed during the test.
20
Installation and Upgrades / eBox 1.3 - Samba PDC
« on: November 17, 2009, 09:18:46 pm »
Hi everyone,
i am currently evaluating eBox 1.3 beta to see if it fits our company needs. The new central LDAP feature is exactly what i was looking for as a replacement for our current setup.
I use Virtualbox to test the new topology - currently with 3 machine instances:
gateway:
classic ebox gateway setup + ebox-dns, but with 1.3 packages to make it possible to include mail/jabber connected to the central ldap on this machine in the future.
ldap:
ebox-usersandgroups only
server:
samba pdc, ldap slave
Ideally, i would like to merge samba and ldap into one machine, but according to the tutorial that is not possible at the moment. So i stick with this setup for testing purposes.
I followed the tutorial to the point and with the exception of a missing "disabled" directory in /etc/apparmor.d/ on the samba server, everything went smooth.
Currently, everything looks good. LDAP slaves are synced correctly - Users and Groups appear in the respective configuation panels on the samba server. I am, however, unable to join any version of Windows to the domain.
I tried both, WinXP Sp3 and Windows 7 RTM+registry fixes. Every time i try to join the domain, i get an error message saying "Unknown user or wrong password". The user i am trying to join with has administration rights and the password is correct (i am able to log into the usercorner on the ldap server, but not on the samba server).
While Windows tries to join, i get the following error message in /var/log/syslog:
Note the double "sambaDomainName=" entry here. Could this be the problem?
Does anyone else have trouble joining Windows machines to the Samba Domain on 1.3?
Cheers,
Ralf
i am currently evaluating eBox 1.3 beta to see if it fits our company needs. The new central LDAP feature is exactly what i was looking for as a replacement for our current setup.
I use Virtualbox to test the new topology - currently with 3 machine instances:
gateway:
classic ebox gateway setup + ebox-dns, but with 1.3 packages to make it possible to include mail/jabber connected to the central ldap on this machine in the future.
ldap:
ebox-usersandgroups only
server:
samba pdc, ldap slave
Ideally, i would like to merge samba and ldap into one machine, but according to the tutorial that is not possible at the moment. So i stick with this setup for testing purposes.
I followed the tutorial to the point and with the exception of a missing "disabled" directory in /etc/apparmor.d/ on the samba server, everything went smooth.
Currently, everything looks good. LDAP slaves are synced correctly - Users and Groups appear in the respective configuation panels on the samba server. I am, however, unable to join any version of Windows to the domain.
I tried both, WinXP Sp3 and Windows 7 RTM+registry fixes. Every time i try to join the domain, i get an error message saying "Unknown user or wrong password". The user i am trying to join with has administration rights and the password is correct (i am able to log into the usercorner on the ldap server, but not on the samba server).
While Windows tries to join, i get the following error message in /var/log/syslog:
Code: [Select]
Nov 15 21:51:57 server slapd[10957]: conn=381 op=2 do_search: invalid dn (sambaDomainName=,sambaDomainName=SMBDOMAIN,dc=domain,dc=tld)Note the double "sambaDomainName=" entry here. Could this be the problem?
Does anyone else have trouble joining Windows machines to the Samba Domain on 1.3?
Cheers,
Ralf
21
Installation and Upgrades / Re: Force sync of pending operations
« on: November 15, 2009, 12:11:39 am »
Hi,
i had a similar problem in my testing environment. LDAP Slaves wouldn't sync automatic or manually.
After some time i noticed following entry in /var/log/ebox/ebox.log on my LDAP machine:
Then i realized that i forgot to create proper DNS entries for my test machines. The LDAP sync tries to reach the slaves via their hostnames ("server" in this case is my samba LDAP slave). As soon as i defined DNS entries for the slaves, the sync went ok.
Hope that helps.
i had a similar problem in my testing environment. LDAP Slaves wouldn't sync automatic or manually.
After some time i noticed following entry in /var/log/ebox/ebox.log on my LDAP machine:
Code: [Select]
SOAPClient.pm:108 EBox::SOAPClient::__ANON__ - 500 Can't connect to server:443 (Bad hostname 'server')Then i realized that i forgot to create proper DNS entries for my test machines. The LDAP sync tries to reach the slaves via their hostnames ("server" in this case is my samba LDAP slave). As soon as i defined DNS entries for the slaves, the sync went ok.
Hope that helps.
Pages: 1 [2]