Third problem is locally stored profiles. How I could make such set up that when
user logs out from WS , then WS
would copy changed profile back to server and delete it from WS ?
It's question of security and hard disk space..
you can do that with a setting in gpedit.msc
don't remember
On Fri, 2003-02-28 at 13:09, [EMAIL PROTECTED] wrote:
[netlogon] share is like that:
[netlogon]
comment = Network Logon Service
path = /home/samba/netlogon
guest ok = no
writable = no
browseable = yes
public = yes
this is what i'm using ...
[netlogon]
path =
On Fri, 2003-02-28 at 13:09, [EMAIL PROTECTED] wrote:
[netlogon] share is like that:
[netlogon]
comment = Network Logon Service
path = /home/samba/netlogon
guest ok = no
writable = no
browseable = yes
public = yes
this is what i'm using ...
[netlogon]
path =
On Fri, 2003-02-28 at 13:09, [EMAIL PROTECTED] wrote:
[netlogon] share is like that:
[netlogon]
comment = Network Logon Service
path = /home/samba/netlogon
guest ok = no
writable = no
browseable = yes
public = yes
this is what i'm using ...
[netlogon]
path =
4)
How could i set up client name resolution so that X client canot
announce itself as DC/browse master etc?
I every client resolves names via boadcast then when my DC goes down
and someone brings up his nt/samba server he could do lotof damaga -
collect people passwords etc...
just use
Hi,
I have some strange problems with 3.0a21 PDC (samba and nss use both
ldap) and I can't find any good help with google...
One strange thing is that logon script does'nt work anymore, it worked
at one point and now doesnt (I quite play around here and I dont know in
which point of changing
4)
How could i set up client name resolution so that X client canot
announce itself as DC/browse master etc?
I every client resolves names via boadcast then when my DC goes down
and someone brings up his nt/samba server he could do lotof damaga -
collect people passwords etc...
just use