1. Does anyone know what may be happening here? When I try to map a
drive from a PC, I get the following error: "The account is not
authorized to log in from this station.". I can map the drive just fine
from my PC. Does anyone know what may be going on here? Any help would
be greatly appreciated.
2. Also, whenever I use SWAT, it takes a long time for the
information to be displayed on my browser. For example if I hit the
"Status" button on top, it takes a long time before the info. comes
back. Does anybody know what may be going on here?
If anybody has any insight, I would really appreciate it. Thanks!
Rick
Houston, Texas
=====================================================This e-mail message is
intended only for the personal
use of the recipients(s) named above. If you are not
an intended recipient, you may not review, copy or
distribute this message.
If you have received this communication in error,
please notify the Houston Chronicle Postmaster
(postmaster@chron.com) immediately by e-mail and
delete the original message.
======================================================
On Tuesday 12 April 2005 15:24, Rivera, Richard (Houston) wrote:> 1. Does anyone know what may be happening here? When I try to map a > drive from a PC, I get the following error: "The account is not > authorized to log in from this station.". I can map the drive just fine > from my PC. Does anyone know what may be going on here? Any help would > be greatly appreciated.What passwd backend are you using? What account restrictions have been implemented? What is the output of "testparm -s"?> 2. Also, whenever I use SWAT, it takes a long time for the > information to be displayed on my browser. For example if I hit the > "Status" button on top, it takes a long time before the info. comes > back. Does anybody know what may be going on here?What OS? How did you install Samba? How did you configure SWAT? - John T. -- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO & Reference Guide, ISBN: 0131453556 Samba-3 by Example, ISBN: 0131472216 Hardening Linux, ISBN: 0072254971 Other books in production.
I have a share access question for you. I have been running Samba 2.2.7 as
a PDC on my RH7.2 box for several years now. I just setup a new PDC
running Samba 3.0.10 on a FC3 box. I used to control read-write acces to
shares via samba like:
[TRData]
path = /tr/TRData
valid users = administrator,@IT,@fl,@tx,@eu,@ca,@ny,@wa,@uk
write list = administrator,@IT,@FLTR
force group = FLTR
read only = no
create mask = 0777
directory mask = 0777
That would work fine when I was running Samba 2.2.7, but now it doesnt
work with Samba 3.0.10. What can I enter to my new smb.conf (3.0.10) to
get the shares to behave like they did when I ran 2.2.7?
Thanks in advance!!!
Ok, it seems to be an LDAP problem. for some reason linux isnt reading the ldap groups, even though /etc/nsswitch.conf states groups = files ldap Here is my problem: I ran smbldap-groupadd TEST to create the group test. I then ran: smbldap-groupmod -m gerrym,briang TEST to add gerrym (me) and briang to that group. I next created a test linux directory called TESTDIR to check permisions. I changed the ownership to briang.TEST TESTDR (chown briang.TEST ./TESTDIR). I then changed directory permisions to 770 (user and group have read,write,and execute). I then logged in as my self (gerrym) and tried to access that directory and I am unable to. The directory permisions should allow me in w/full control as I am in the group TEST. I run getent group|grep TEST and verify I am a member of that group and I am. I then checked /etc/nsswitch.conf and it shows: group: files ldap Just wondering why it will not let me in that directory if permisions are right? I used IDEALX's smb-ldap script 1.2. Any help or suggestions would be appreciated. THANKS!> I have a share access question for you. I have been running Samba 2.2.7 as > a PDC on my RH7.2 box for several years now. I just setup a new PDC > running Samba 3.0.10 on a FC3 box. I used to control read-write acces to > shares via samba like: > [TRData] > path = /tr/TRData > valid users = administrator,@IT,@fl,@tx,@eu,@ca,@ny,@wa,@uk > write list = administrator,@IT,@FLTR > force group = FLTR > read only = no > create mask = 0777 > directory mask = 0777 > > That would work fine when I was running Samba 2.2.7, but now it doesnt > work with Samba 3.0.10. What can I enter to my new smb.conf (3.0.10) to > get the shares to behave like they did when I ran 2.2.7? > > Thanks in advance!!! > > >
On Wednesday 13 April 2005 13:25, Gerry Maddock wrote:> I have a share access question for you. I have been running Samba 2.2.7 as > a PDC on my RH7.2 box for several years now. I just setup a new PDC > running Samba 3.0.10 on a FC3 box. I used to control read-write acces to > shares via samba like: > [TRData] > path = /tr/TRData > valid users = administrator,@IT,@fl,@tx,@eu,@ca,@ny,@wa,@uk > write list = administrator,@IT,@FLTR > force group = FLTR > read only = no > create mask = 0777 > directory mask = 0777 > > That would work fine when I was running Samba 2.2.7, but now it doesnt > work with Samba 3.0.10. What can I enter to my new smb.conf (3.0.10) to > get the shares to behave like they did when I ran 2.2.7?Did you read the WHATSNEW.txt notes in your Samba 3.0.10 release. I believe you will find the magic answer there. However, since your posting is very short of detailed information it is a little hard to help you with a direct solution. Have you read the Samba-HOWTO-Collection and the Samba-Guide for information? http://www.samba.org/samba/docs/ - John T.
Got it working. I had to restart nscd service. Nscd was not reflecting the group entries.> Ok, it seems to be an LDAP problem. for some reason linux isnt reading the > ldap groups, even though /etc/nsswitch.conf states groups = files ldap > Here is my problem: > > I ran smbldap-groupadd TEST to create the group test. I then ran: > smbldap-groupmod -m gerrym,briang TEST to add gerrym (me) and briang to > that group. I next created a test linux directory called TESTDIR to check > permisions. I changed the ownership to briang.TEST TESTDR (chown > briang.TEST ./TESTDIR). I then changed directory permisions to 770 (user > and group have read,write,and execute). I then logged in as my self > (gerrym) and tried to access that directory and I am unable to. The > directory permisions should allow me in w/full control as I am in the > group TEST. I run getent group|grep TEST and verify I am a member of that > group and I am. I then checked /etc/nsswitch.conf and it shows: > group: files ldap > > Just wondering why it will not let me in that directory if permisions are > right? I used IDEALX's smb-ldap script 1.2. Any help or suggestions would > be > appreciated. THANKS! > >> I have a share access question for you. I have been running Samba 2.2.7 >> as >> a PDC on my RH7.2 box for several years now. I just setup a new PDC >> running Samba 3.0.10 on a FC3 box. I used to control read-write acces to >> shares via samba like: >> [TRData] >> path = /tr/TRData >> valid users = administrator,@IT,@fl,@tx,@eu,@ca,@ny,@wa,@uk >> write list = administrator,@IT,@FLTR >> force group = FLTR >> read only = no >> create mask = 0777 >> directory mask = 0777 >> >> That would work fine when I was running Samba 2.2.7, but now it doesnt >> work with Samba 3.0.10. What can I enter to my new smb.conf (3.0.10) to >> get the shares to behave like they did when I ran 2.2.7? >> >> Thanks in advance!!! >> >> >> > >
On Wednesday 13 April 2005 13:25, Gerry Maddock wrote:> I have a share access question for you. I have been running Samba 2.2.7 as > a PDC on my RH7.2 box for several years now. I just setup a new PDC > running Samba 3.0.10 on a FC3 box. I used to control read-write acces to > shares via samba like: > [TRData] > path = /tr/TRData > valid users = administrator,@IT,@fl,@tx,@eu,@ca,@ny,@wa,@uk > write list = administrator,@IT,@FLTR > force group = FLTR > read only = no > create mask = 0777 > directory mask = 0777 > > That would work fine when I was running Samba 2.2.7, but now it doesnt > work with Samba 3.0.10. What can I enter to my new smb.conf (3.0.10) to > get the shares to behave like they did when I ran 2.2.7? > > Thanks in advance!!!The valid users and write list now require @DOMAIN\IT @DOMAIN\fl etc. - John T. -- John H Terpstra Samba-Team Member Phone: +1 (650) 580-8668 Author: The Official Samba-3 HOWTO & Reference Guide, ISBN: 0131453556 Samba-3 by Example, ISBN: 0131472216 Hardening Linux, ISBN: 0072254971 Other books in production.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John H Terpstra wrote: | On Wednesday 13 April 2005 13:25, Gerry Maddock wrote: |>I have a share access question for you. I have been running Samba 2.2.7 as |>a PDC on my RH7.2 box for several years now. I just setup a new PDC |>running Samba 3.0.10 on a FC3 box. I used to control read-write acces to |>shares via samba like: |>[TRData] |> path = /tr/TRData |> valid users = administrator,@IT,@fl,@tx,@eu,@ca,@ny,@wa,@uk |> write list = administrator,@IT,@FLTR |> force group = FLTR |> read only = no |> create mask = 0777 |> directory mask = 0777 |> ... | | The valid users and write list now require @DOMAIN\IT @DOMAIN\fl etc. John, This is true when using users and group from winbind only. This is a PDC from the orginal post. cheers, jerry ====================================================================Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "I never saved anything for the swim back." Ethan Hawk in Gattaca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCYX4iIR7qMdg1EfYRAjVPAJ9GfcltM8nZpqSI+wL+VI955nwkTwCgpwLp OoQd0ew2/GWVd9JBpDmFmYk=UoZC -----END PGP SIGNATURE-----