kkruger
Using Samba to share files with Windows (part 2)
Previously, in Using Samba to share files with Windows (part 1), the LDAP configuration that were required specifically for Samba were completed. All that’s left to do is to create the Samba setup, add some users, and test the result.
This configuration is a good basic starting point for implementing Samba, which is on CentoS 6.2 with openLDAP 2.4.23 using the cn=config RTC, and Samba 3.5.10. It looks like this is turning into more of a series because these posts are turning out a lot longer than originally intended.
Using Samba to share files with Windows (part 1)
Whether it’s for home, for an office, or in an enterprise, there will always be a need to share files and media. Samba enables this functionality between the Linux/UNIX and Windows operating systems.
When Samba is installed and configured on our CentoS 6 server, we’ll be able to access it from any Windows computer or laptop on the local network. Access to different files and directories can be controlled based on the user accounts and groups maintained in an LDAP database on the server. Using LDAP with Samba is optional, but offers greater flexibility.
Configuring OpenLDAP server on CentoS 6
Introduction
LDAP (Lightweight Directory Access Protocol) is commonly used for managing users and groups for authentication purposes, or for system configuration information. It can also serve as a virtual phone directory and address book, allowing users to access information about other users in the directory.
CentoS 6.2 ships with OpenLDAP 2.4.23 which contains the cn=config Directory Information Tree (DIT) that is used to dynamically configure the slapd daemon. This allows modification of schema definitions, indexes, ACLs, etc without stopping the service.
The goal in this post is to configure OpenLDAP so that it can be used for user authentication. For simplicity, the Samba file sharing configuration and user migration will be handled in separate posts.
A blank Icon after an Internet Explorer upgrade
Every once in a while, when we upgrade Internet Explorer, an issue arises where the icon turns into the blank default icon instead of changing to the new one.
I’ll add a screenshot the next time I run into it, but here is the answer for going from ie6 to ie7. I have only seen this happen going from ie7 to ie8 a couple of times and only in XP. The same resolution seems to work in that case as well.
Go into the registry and look for the registry key…
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\IEXPLORE.EXE\DefaultIcon
I’ll bet yours looks as mine did and has…
C:\Program Files\Internet Explorer\iexplore.exe,-7.
Installing Microsoft UAA on XP SP3
Today I had an issue with Microsoft Windows XP Service Pack 3 with HD audio/modem devices that are not recognized even after installation of proper drivers. This happens because they require that the Microsoft Universal Audio architecture driver be installed first.
After a long search, I found a registry trick that allows the Microsoft UAA driver to install.
The file name that is actually needed is kb888111xp2.exe which Microsoft does not publicly available, but it can be found on the Internet. An alternative is to download the driver for your audio device from the hardware manufacturer and extract it from the download. In some cases, the driver will actually install it, sometimes not.
