Wednesday, 14 April 2010

Windows7 Professional and Samba domain. History of failure.

It doesn't work with SAMBA versions before 3.3. Please see the link below.
From SAMBA wiki:
Windows7 - SambaWiki

Install samba 3.4 on CENTOS 5.4 server. Removal of all old samba packages are mandatory! All packages downloaded from ftp://ftp.sernet.de/pub/samba/3.4/centos/5/i386/
rpm -ivh libwbclient0-3.4.7-42.el5.i386.rpm
rpm -ivh libsmbclient0-3.4.7-42.el5.i386.rpm
rpm -ivh samba3-client-3.4.7-42.el5.i386.rpm
rpm -ivh samba3-3.4.7-42.el5.i386.rpm

All configuration performed as usual. See Samba domain controller setup.
Note: I can't use Microsoft's ifmember utility with Windows 7 (Useful to map resources based on group membership ) . I'll have to find an alternative.

Problems:
  • I have encounter some delay when Windows 7 logging to SAMBA domain. The solution described in the link solved the problem.
  • Windows 7 does not see domain groups when processing logon.bat (see Note above). I tried to use kix32, but not succeeded. Solution still not found. Drives mapper based on usernames instead of SAMBA groups.
  • After upgrade to Samba 3.4 SQUID domain authorization stopped to work . Authorization tests from console did not pass. Only fast solution I have found is to change script from included smb_auth to the script by this link.
So after these tests we were forced to downgrade Windows 7 Proffesional to Windows XP Professional and all systems began to work smooth, fast, responsible and predictably.

Update 20101207: All problems solved. Later I'll write how...

No comments: