On Thu, 2002-04-25 at 08:10, Dan Horth wrote: > > Basically I want to know has anyone on the list has had success with either the >supplied samba rpm on a freshly set up (and fully updated) 7.2 server, or with >rpms obtained from elsewhere. I'd also be interested in comparing smb.conf files, as >the one I'm currently using has been adapted from ones originally set up on a 6.2 >based server with an earlier version of samba.
Sure, the packages provided with 7.2 work well here, providing domain logins for XP Pro, when I boot it (which is mostly to test samba :) Swat is an excellent way to clean up config files. It should write files that contain only the settings which are not the defaults. That is, if your existing files explicitly set options that are the defaults anyway, swat should remove them, and leave you with a much cleaner config file. A tutorial on setting up domain logins with samba was published very recently on IBM's Developer Domain: http://www-1.ibm.com/servers/esdd/tutorials/samba.html?t=gr,l=805,p=Samba Also see the included documentation: /usr/share/doc/samba-2.2.1a/docs/htmldocs/Samba-HOWTO-Collection.html > Services I'm trying to implement are: > > domain logons - for 98, NT 4, 2000 and XP home clients > profiles that work correctly > profiles that work between OS's - Win98 / NT / XP I don't think you can share profiles between DOS based Windows and NT based windows. Even if you set the "login home" and the "login path" (used by the different families of Windows) to the same value, NT stores the user's registry in a file called NTUSER.DAT, and DOS Windows stores it in USER.DAT. You probably could symlink one to the other, but I have never tried such a thing, and expect it would fail. > file and printer sharing > printer driver installation > dynamically generated netlogon scripts I don't know if that's possible, but you can have per-user scripts. What do you want to do with dynamically generated scripts? > cooperation with / awareness of netatalk server (shared volume) The two should be able to share the same directories, but there won't be a high level of integration between the two.
signature.asc
Description: This is a digitally signed message part
