pages with windows authentication prompt boxes no working

  • Thread starter Thread starter ess
  • Start date Start date
E

ess

Whenever I go to a webpage that has domain/account logon
box (directory with NTFS settings), it doesn't work. My
account does have the correct ntfs settings to allow me
access to the directory. If I click on the link that would
normally display the logon prompt, the IE/Windows logo in
the upper right corner just spins for about 1 second and
nothing happens. This happens for any site I go to, not
just a server I have. If I open the link in a new window I
just get a blank page. This happens on some XP machines,
and some 2000 machines too. I can't find what setting that
is causing this on some machines and not on other
machines. I have show friendly http errors advanced option
unchecked and I still get no error message. I've tried
changing the IE security User Authentication/Logon setting
to different settings (and rebooted) but that has no
effect as well. What is going on? Any suggestions? I've
tried using FileMon and RegMon (www.sysinternals.com) but
I haven't seen anything from those tools to help out yet.
Please help! Thanks.
 
I'm not clear on whether you are seeing the logon boxes
properly in all cases and the problem is that you can't use it
or whether in some cases you are not even getting the logon box.
(At first I thought it might be that some weren't getting the right
kind of logon prompt but I am now assuming that that is not the case.)

In the first case I would guess that that is some kind of security issue
on the client and imagine that you might get better help from a newsgroup
which specializes in that for your OS.

In the second case I would want to rule out the possibility of differences
in the datastreams before worrying about whether the client even has any
of the misconfigurations implied by the first case. E.g. if you can spot
protocol differences in the two cases then to me it makes more sense
to try to understand the causes and the consequences of them.
Doing that would require yet another tool: a packet sniffer such as Ethereal
or Microsoft's netmon.

Alternatively you could just take stabs at what might be causing
the various symptoms and try applying known fixes. For example,
in the case of your W2K systems you could try an IE Repair.
(XP users can only do that if they have installed IE6sp1 separately
before installing XPsp1.) The procedure documented in MS KB281679
is a small subset of what an IE Repair would do.

Or just try some of the IE FAQ suggestions:
< http://support.microsoft.com/default.aspx?scid=fh;EN-US;iepcbdfaq >


BTW are all machines using HTTP 1/1 and can all machines
use https: in other contexts? Does it make any difference if users
are given administrative authority (as a diagnostic or workaround)?
Is there any recent maintenance activity which should be considered?
(E.g. compare Windows Update.log files for otherwise equivalent
systems.)


Good luck

Robert Aldwinckle
 
Back
Top