I had problems with a small server and ended up wiping the darned thing 
and reinstalling. I also took the opportunity to upgrade from Win2k to 
WinXp Pro (SP1) at the same time. 

Under the old Win2k system, all my CSP pages detected the username / 
password from the Win2k login and was used to present the correct menu 
to the user - this as been happily running for months and months. 

in order to get the username etc, I followed the exact instructions 
from George James 
      1 In IIS for the Virtual Directory go to the Directory Security
          tab of the Virtual Directory Properties window. Select 
          Anonymous Access and Authentication Control to open the 
          Authen[t]ication Methods window. Then uncheck Anonymous 
          Access, uncheck Basic Authentication and check Integrated 
          Windows Authentication. 
      2 In your CSP application the *authenticated* users Id will then
          be available in %request.CgiEnvs("REMOTE_USER")

Like I say, this has been working fine.

suddenly in XP, security has been clamped down so much, that it's no 
longer working. On the server, the user can log in fine, view the CSP 
pages and all works OK. On clients (only three of them) I am 
continually presented with a UserName / Password popup. If I cancel 
these, (5 of them) I get a popup that asks for the firewall password, 
ntlm: realm, username and password 

Never having needed to (or come across) the ntlm realm - I'm unsure of 
what I need to uncheck / remove / disable to let me carry on as usual. 

I've been doing some research on the net and I now know the ntlm is the 
NTLanMan authentication process. the one note I came across asks to 
make sure that the page has not been hijacked (no it hasn't) check the 
username is not being blocked by the proxy (no its not) 

the five popup usernames does equate to five Java applets that are 
displayed on the menu page I have checked the security privileges on 
the csp directory and ensured (I hope) that IIS has been correctly 
setup. 
 

I have installed IE6sp1 and the latest Java runtime's on the server as 
part of the upgrade but nothing has changed on the clients, they still 
run IE6sp1 and the latest Java runtime's 

so of course the question is:
     Anyone got a clue where to look next.

its a real pain in the **** I've already lost a lot of hair today and 
need to retain some just for my handsome looks ! ! ! can anyone help 
please. 

just one last thing, after pulling the hair out all day, I've come home 
hoping that everyone can chip in and send me back tomorrow with all the 
answers (this ultimately means that I can't quickly check settings and 
get back to the newsgroup.) 

here's praying that there are some good trichologist's out there and 
someone can prevent premature baldness

kev


Reply via email to