Engelbert
Tue Apr 11 06:33:33 CDT 2006
The effect of Local Intranet will depend on the company settings for
Intranet.
In the present case we don't know why some users can access the site without
logging in and some not. Usually if the system is identifying a site as
Intranet it will identify the site for all users as Intranet. (It's unlikely
that most users have specified this site themselves as Intranet).
Adding things to Trusted Sites should never be done wildly and without
thought. I suspect that if IT suggests adding a site to trusted sites, the
next thing you will see is that users follow this idea and add lots of
suspicious sites to Trusted Sites. Not Good.
That said both of your suggestion might have an effect but the most common
reason for some users being able to access a site directly and others not is
the logon one I mentioned earlier.
Engelbert
"Robin Meuré" <RobinMeur@discussions.microsoft.com> wrote in message
news:0A973D1F-6F08-4204-846B-07D2206F2042@microsoft.com...
> Or add the site to their 'local intranet' or 'trusted sites'
>
> "Engelbert" wrote:
>
>> Change their IE settings so that it uses the domain logon information
>> that
>> they used to logon to their PC.
>>
>> Internet Options / Security / Custom Level and then right at the end
>> Logon /
>> Automatic Logon with username and password
>>
>> Engelbert
>>
>>
>> "wss 2.0" <txl008@hotmail.com> wrote in message
>> news:eiufQAVXGHA.4324@TK2MSFTNGP03.phx.gbl...
>> > wss 2.0 sp2 installed on a windows server 2003 R2.
>> > A top level website, say, companyweb has been created.
>> > "domain\domain users" group has been added to the reader group.
>> > Most users have no problem in browing to
http://companyweb/
>> > But a few users are prompted to enter username/password every time
>> > browing
>> > to that site.
>> > How to get rid of that?
>> >
>> >
>>
>>
>>