You merely need to ask... # Samba config file created using SWAT # from 0.0.0.0 (0.0.0.0) # Date: 2002/11/16 16:26:49 # Global parameters [global] workgroup = HOMEWG netbios name = SERVER1 encrypt passwords = Yes map to guest = Bad User time server = Yes unix extensions = Yes socket options = SO_KEEPALIVE IPTOS_LOWDELAY TCP_NODELAY printcap name = CUPS character set = ISO8859-15 domain admin group = @ntadmin logon script = logon.bat logon path = \\server1\profiles\%U logon drive = U: logon home = \\server1\%U domain logons = Yes os level = 64 preferred master = True domain master = True wins support = Yes kernel oplocks = No printing = cups veto files = /*.eml/*.nws/riched20.dll/*.{*}/ [profiles] comment = Network Profiles Service path = /var/lib/samba/profiles/%U read only = No create mask = 0600 directory mask = 0700 nt acl support = No browseable = No [homes] comment = Home Directories valid users = %S read only = No create mask = 0640 directory mask = 0750 browseable = No [printers] create mask = 0600 browseable = No comment = All Printers writeable = yes printable = Yes path = /var/tmp [netlogon] comment = Netlogon path = /var/lib/samba/netlogon write list = @ntadmin [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 Thanks, Stuart. -----Original Message----- From: Praise [mailto:praisetazio@tiscalinet.it] Sent: Saturday, December 07, 2002 14:43 To: suse-linux-e@suse.com Subject: Re: [SLE] New SAMBA PDC does not run logon script Alle 21:36, giovedì 5 dicembre 2002, Stuart Powell ha scritto:

Hello, everyone.

I have my new server (SuSE 8.1 Pro) up and running, but there are a couple of nagging issues with Samba.

I have transferred my old Samba settings/files to my new server, and my shares all show up fine, and I can map drives as before. However, the logon script no longer runs when a user logs in on a client PC. I mainly use this file to map the drives to the correct share, which I have been able to set up manually. My concern is that this problem points to Samba not being set up properly, which bothers me a great deal.

Anyone else had a similar problem and managed to overcome it ? I have installed the latest Samba updates via YOU, but that didn't help.

That's impossible to say without seeing smb.conf Praise -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com