Displaying 4 results from an estimated 4 matches for "winad".
2008 Apr 04
1
Issue with Samba 3.0.28a and Active Directory
Hi all,
1. We are using Linux kernel 2.6.20.11 64-bit and Samba 3.0.28a
2. We are trying to connect from this linux machine to a Windows ADS
running on a separate Windows 2003 system (WINADS machine).
3. Though we are able to retrieve the name of the WINADS machine from
linux (We see the name of the machine in samba log file), we are
unable to access any of the users in the WINADS machine.
4. The following is our smb.conf file
[global]
preservecase = yes...
2015 Sep 07
1
winbind does not work+sernet package+samba 4.2
Hello
After failing to join my samba box to winAD 2012, I went and downloaded
the sernet packages
and samba box join the AD domain using "samba-tool" with no problems.
However I've got problems with winbind.
wbinfo -u returns:
could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE
could not obtain winbind domain...
2008 Aug 18
1
Win2000 / Win2003 ADS dnsHostName and servicePrincipalName
...uot; which clearly cannot be correct. So i used
SysInternals LDAP Explorer (ADExplorer.exe) to change the entry in
ActiveDirectory to remove any reference to localhost. Unless i changed
/etc/hosts to not have rmonster in
"127.0.0.1 localhost.localdomain localhost rmonster", deleted from WinAD and
rejoined.
dNSHostName: rmonster.snslatc.hp.com
servicePrincipalName: CIFS/rmonster.snslatc.hp.com
servicePrincipalName: CIFS/rmonster
servicePrincipalName: HOST/rmonster.snslatc.hp.com
servicePrincipalName: HOST/rmonster
Is the line "servicePrincipalName: CIFS/rmonster.snslatc.hp.com&quo...
2004 Nov 18
3
Domain authentication failing after a period of time
I am having an unusual bit of behavior with a recently upgraded 3.0.8
installation (from 3.0.2a). I upgraded the server and retained the
secrets.tdb file. The server itself is using security = domain, and it had
been joined to the domain prior to the upgrade. Now, once I started the
new version, I couldn't log on, and would get the error "There are no
logon servers available to service