Members of the Domain Admin Group will not have this issue. You may or
may not want to resolve it this way, since it does elevate regular users
priveledges. If its a small install of responsible users, it may not
matter. see man smb.conf domain admin group =.
g
Ainsworth, Joshua B. wrote:
I
Dude -- Your arrogant attitude towards getting help and resolving your
problem is not getting you anywhere -- its obviously problematic to pump
SMB/CIFS into the internet the way you would like to. Why don't you
look at a simpler solution like running an anonymous ftp server and then
your
, Gordon Russell wrote:
Date: Thu, 10 Feb 2005 09:22:48 -0500
From: Gordon Russell [EMAIL PROTECTED]
Cc: JLB [EMAIL PROTECTED], samba@lists.samba.org
Subject: Re: [Samba] Firewall piercing - The Specified network name is no
longer available.
Dude -- Your arrogant attitude towards getting help
Hello--
I upgraded my RH9 samba PDC server from 3.0.9pre3 to 3.0.11 using
packaged RH9 rpm from samba site, using rpm -U samba*rpm.
no complaints from rpm. samba stops/starts fine. However, clients can
no longer log in to domain. All clients (W2k,XP) get the same error
message The system
Hello--
I upgraded my RH9 samba PDC server from 3.0.9pre3 to 3.0.11 using
packaged RH9 rpm from samba site, using rpm -U samba*rpm.
no complaints from rpm. samba stops/starts fine. However, clients can
no longer log in to domain. All clients (W2k,XP) get the same error
message The system
I have determined that members of the root group can logon to domain, no
problem. If you are not a member of the unix root group, you are sol...
file permissions somewhere not right? please, i dont want to have to
add all my users to root group before tomorrow morning ;-)
g
Gordon Russell
Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 8 Feb 2005, Gordon Russell wrote:
I have determined that members of the root group can logon to domain, no
problem. If you are not a member of the unix root group, you are sol...
file permissions somewhere
W2k by default runs scheduled tasks as system user, which isnt a samba
user. somewhere in the config of the W2K job schedule interface (it may
be under an advanced button) you can change the user that the job runs
under. Change it to a user who is in your samba system, and can
read/write the
I can think of a couple of ways to accomplish this. You could create
unix groups that contain users that can see some shares, then remove the
read/write/execute bit (or specifically the -x bit) for world/others on
the directorys that you want hidden from others. these same directories
need to
I can think of a couple of ways to accomplish this. You could create
unix groups that contain users that can see some shares, then remove the
read/write/execute bit (or specifically the -x bit) for world/others on
the directorys that you want hidden from others. these same directories
need to
you can get samba 2.2.2 in solaris pkgadd format at:
http://www.sunfreeware.com
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
guess that nt4 at jobs are running as some kind of
'system' user that samba doesnt know of. Does anyone know the workaround
here?
thanks
Gordon Russell
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
12 matches
Mail list logo
