Error 401.2

From: Ravi (hkravi4u_at_hotmail.com)
Date: 10/21/03 

Date: Tue, 21 Oct 2003 03:11:05 -0700

Hi all,
Am getting the 401.2 Error "Unauthorized: Logon failed due to server configuration" whenever i try to connect to a webserver using http://Ipaddress.
But the same works fine when i give http://machinename
Am not sure what exactly the problem is.
BTW, i have "Integrated Windows authentication" enabled and i dont have any proxy/firewall.
I checked the permissions for the root virtual folder and it has full control for everyone.

Any Ideas ???

Am getting the following also as part of the error message.

"This is usually caused by a server-side script not sending the proper WWW-Authenticate header field. Using Active Server Pages scripting this is done by using the AddHeader method of the Response object to request that the client use a certain authentication method to access the resource. "

Any help is much appreciated.

Rgds
Ravi

Relevant Pages

  • Re: fbsd safety of the ports
    ... That may be true for the core files, but what about ports. ... On the net I read _never_ to let the webserver be the owner of its ... prior to updates/config changes to temporarily open the permissions. ... You can always jail the webserver as well. ...
    (freebsd-questions)
  • Re: COM Remote Server Machine Unavailable, Event 10016
    ... Just to make sure I watched the ports being accessed using Systernals TCP View, and the webserver app never made any calls to a remote endpoint, only loopbacks. ... Right now I am just trying to get the client & server running on the same server. ... I did change the Access, and the Launch and Activation permissions using dcomcnfg to explicitly allow the NETWORK SERVICE user, and this made no difference. ...
    (microsoft.public.vb.com)
  • Re: how to restrict developers in /var/www/html directory...??
    ... The permissions on the directory should look like this when you perform an "ls -la". ... This will allow the webserver to read the files for display, but will only allow the owner to modify them. ... The "www-data" user as I understand it, exists primarily as a safeguard to protect the rest of the system against hacking. ... IMHO it should never be, because if write permissions are accidentally set for www-data (even system administrators make mistakes) that gives someone who breaches the Apache webserver security or the www-data group the ability to rewrite your website files. ...
    (Debian-User)
  • Re: Deleting Image Files from CMS
    ... Owner Group Permissions ... ... permissions didn't work:( ... > This error happens because the UID of the webserver process is not ... > Quick solution probably to make the image dirs group writeable to ...
    (comp.lang.php)
  • Re: Suexec with Apache 1.3.29
    ... > that Apache itself runs as user nobody. ... Technically if no other other users tha www itself is member of the www group I find the more sophisticated way of setting permissions you gain would be more important. ... It is my believe that suexec by being too paranoid removes some great configuration options. ... Also the problem when running a webserver with many users you don't know is to get them to use the right permissions. ...
    (freebsd-questions)