Authentication problem with FP98

[Rick [MVP IIS]]

Do the ones that are trying to publish have "Log On Local" right on the NT
server? If not give them that right.

Mark Schrijen wrote in message <6i8gj6$c9...@reader2.wxs.nl>...
>The context:
>We are supporting a company in establising an intranet, with the use of
FP98
>as authoring tool.
>Last week the company started with deploying a standard Win95
implementation
>on the PC's.
>Their NOS is still Novell 3.12 (alas), and they decided to use the Novell
>client for Win95.
>Some employees had already a Win95 implementation in order to publish
>content on the intranet with FP98.
>The intranet server has NT 4.0, SP3, NT Option pack & FP server extensions
>installed.
>
>The problem:
>After installing the new standard implementation, users were unable to gain
>access with FrontPage to their subwebs on the NT-server.
>Yours truly however, was still able to gain access. After some
experimenting
>we discovered that expanding the rights of the users to Administrator
>equivalence (like my own account) did the trick. Of course our customer
does
>not enjoy the idea of 'commoners' with administrator equivalence.
>
>The question:
>Is this a known problem and what is the solution. And no, the customer will
>not install the microsoft client :(.
>
>Best regards,
>Mark Schrijen,
>CCO IT Consultants.
>Company E-mail: in...@cco.nl
>
>
>

[Mark Schrijen]

[Cowboy]

On Tue, 28 Apr 1998 08:31:54 -0700, "Rick [MVP IIS]"
<ri...@di-wave.com> wrote:

>Do the ones that are trying to publish have "Log On Local" right on the NT
>server? If not give them that right.

That sounds a little scary. Plus, what good would it do?

>Mark Schrijen wrote in message <6i8gj6$c9...@reader2.wxs.nl>...

The option pack uses a slightly different method of assigning web
permissions. Chances are this is where your problems are. In the MMC,
open that server and hten right click on the web(s) in question. Add
users that need web admin rights to the web operators tab. This should
solve your problems unless you have some strange permissions
elsewhere.

GB

When you leave this place, you can only take your name.
That's why I'm making this world a better place,
one promise at a time.

NoSpAMM...@home.comNoSpAMM

remove NoSpAMM from front and back to reply

[Frans L. Plöen]

Cowboy wrote in message <35493423.89781799@news>...

>On Tue, 28 Apr 1998 08:31:54 -0700, "Rick [MVP IIS]"
><ri...@di-wave.com> wrote:
>
>>Do the ones that are trying to publish have "Log On Local" right on the NT
>>server? If not give them that right.
>
>That sounds a little scary. Plus, what good would it do?
>

"Log on locally" is necessary because the IIS will make a local login on
your behalf with your username in order to obey NTFS security. Failing to
set "Log on local" is the most common cause of access problems with IIS.

Another thing; FP98 itself uses a slightly different way of assigning rights
than IIS itself. It is my experience that if you try to change rights in
both places, you get unexpected results. It might help to simply re-install
the FP98 Server Extensions and make sure all rights are assigned through FP.

Rgds,
Frans Plöen

[Cowboy]

On Fri, 1 May 1998 08:11:22 +0200, "=?iso-8859-1?Q?Frans_L._Pl=F6en?="
<fploen[DeleteThisPart]@timesystem.dk> wrote:

>
>Cowboy wrote in message <35493423.89781799@news>...
>>On Tue, 28 Apr 1998 08:31:54 -0700, "Rick [MVP IIS]"
>><ri...@di-wave.com> wrote:
>>
>>>Do the ones that are trying to publish have "Log On Local" right on the NT
>>>server? If not give them that right.
>>
>>That sounds a little scary. Plus, what good would it do?
>>
>"Log on locally" is necessary because the IIS will make a local login on
>your behalf with your username in order to obey NTFS security. Failing to
>set "Log on local" is the most common cause of access problems with IIS.

Excuse me? Since when do people have to have the ability to log on to
the server locally to publish webs? This is a potential security
breach. In a domain setting, the user needs to be able to use the
Inetpub directory (or the particular web directory at the very least),
but he does not have the ability to log into the server locally. I
have users that publish webs without having any local rights
whatsoever.

If however, you mean they have to have rights to the directories, that
is true.

>Another thing; FP98 itself uses a slightly different way of assigning rights
>than IIS itself. It is my experience that if you try to change rights in
>both places, you get unexpected results. It might help to simply re-install
>the FP98 Server Extensions and make sure all rights are assigned through FP.
>
>Rgds,
>Frans Plöen
>

With IIS, you need to have the person who publishes have the right to
administer the web. This is added through the MMC or the HTML
Administration pages.

With NT, the user also has to have rights to the directories. Since
Inetpub is a share, you also need to check to make sure they have the
proper share permissions (esp. if your Sys Admin has tightened
security by using share permissions).