Re: Logon Failures
- From: "Mike Walsh" <englantilainen@xxxxxxxxxxx>
- Date: Thu, 4 Aug 2005 19:10:32 +0300
You can't in SharePoint Team Services set permissions lower than the subweb
level.
In order to get permissions at List level you need to move to the newer (and
current) product Windows SharePoint Services. (which of course needs Win
2003 Server not 2K)
-----------------
Oops, reads again and sees you probably mean something else.
Probably not. You can create different roles to the standard ones and assign
users (and probably user groups - I never did that in STS so I'm not 100%
sure) to one of your newly created roles and in that way those users would
have different rights to users who were allocated to the normal roles
(Reader; Contributor, Designer, Administrator) - but I'm not sure if that
covers what you want.
Mike Walsh, Helsinki, Finland
"JimW" <JimW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:53F19A52-D70F-4764-9FB8-C795929ECC3D@xxxxxxxxxxxxxxxx
> Mike:
>
> Thanks for the post.
>
> The Domain issue dosen't seem to be the problem. We were logging on as
> domain\username.
>
> I created a test site without STS, set it to no anonymous access and was
> able to login with the users who cannot log into the STS site.
>
> While we are talking I also need to know if it is possible to set
> different
> permissions for seperate lists based on users and/or groups.
> --
> Thanks in advance for your help.
>
> Jim
>
>
>
> "Mike Walsh" wrote:
>
>> I wonder if this is anonymous access at all. You seem to have the same
>> problem of non-recognition with or without anonymous access being
>> specified.
>>
>> I've had quite a lot of cases where people who have been given rights on
>> a
>> STS site have not been recognized. This usually happens after they have
>> received a new PC and they are logging in with their username only which
>> means the system is assuming <clientcomputername>\username rather than
>> <domainname>\username (or if a local user on the STS server
>> <servername\username).
>>
>> That's maybe one thing to check. Another reason for the same problem is
>> if
>> Terminal Server or Citrix is involved. Again the wrong assumption about
>> the
>> "domain" (in login form terms) is made because of the way they are
>> accessing
>> and the need to specify <servername>\username (these are locally defined
>> users) is not known to them and they keep just writing username.
>>
>> I don't have any other reason I can think of.
>>
>> Mike Walsh, Helsinki, Finland
>> STS FAQ http://www.collutions.com/Lists/FAQ
>> WSS FAQ http://wss.collutions.com
>> please reply to the newsgroup only
>>
>> "Jim Welborne" <Jim.Welborne@xxxxxxxxxxxxx> wrote in message
>> news:%23DMzXoGmFHA.2060@xxxxxxxxxxxxxxxxxxxxxxx
>> > We are running STS on Windows 2000 SP4 and if I set no anonymous access
>> > some people can logon others cannot.
>> >
>> > Also, if I allow anonymous access some people have there names
>> > recognized
>> > others do not.
>> >
>> > If anonymous access is not allowed and Integrated Windows
>> > authentication
>> > is checked in IIS shouldn't the credentials used at network logon be
>> > used
>> > to authenticate?
>> >
>> > The client computers are Windows XP Pro Windows XP Pro and Windows
>> > 2000
>> > Pro.
>> >
>> > Any ideas?
>> >
>> >
>>
>>
>>
.
- Follow-Ups:
- Re: Logon Failures
- From: Jim Welborne
- Re: Logon Failures
- References:
- Logon Failures
- From: Jim Welborne
- Re: Logon Failures
- From: Mike Walsh
- Re: Logon Failures
- From: JimW
- Logon Failures
- Prev by Date: Re: Help with calculated field
- Next by Date: Re: Help with calculated field
- Previous by thread: Re: Logon Failures
- Next by thread: Re: Logon Failures
- Index(es):
Relevant Pages
|
Loading