Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ASP Spell Checker Username Problem?

Status
Not open for further replies.
May 9, 2000
446
GB
Hi, i've just added a spell checker to my asp pages so that users can check the spelling in their forms before submitting them. Anyway the page the spell checker is on is secure as users have to login, a session variable holds their login details until they sign out.

Anyway my users use the spell checker wih no problems but then when they try and do anything on the page like submit they find out they've been logged out! The spell checker automates word '97 on the server using the IUSR and IWAM accounts so could this be afecting their login status / login session variables?
Any help'd be great
 
you may find that the problem could lay in the fact that the session variables have timed out.. In some cases it may take longer to generate the email and then do the check, than the session variables last, Just a thought

 
Hi krappleby025

Cheers for the response but the timeout is set at 30 minutes and according to my users t does last 30 minutes. This problem can happen at any time, basically as quick as you get to the web page with the spell checker on and open the spell checker..... im pretty sure its not a timeout problem but cheers for the suggestion...

Any other ideas? Please!!!!
 
You may want to check the permissions on the page calling the spell checker. When you log in IIS stops using the ISR_MachineName account starts using the account of the login.

To get around this you need to allow the user account access to read the pages. Hope this helps
 
Hey DataLust, cheers for the reply. Do you mean I'd need to give the ISR_MachineName account permissions to use the pages that are protected or something else?

Being thick!
 
If a web user uses Page A and then is asked to login to access Page B, the login they are using is no longer the anonymous machine account(IUSR_MachineName). Once they log in the machine uses the access they just provided to access page B.

If they then return to Page A they're account must have rights to that page. I would suggest the Authenticated User account with read access. Or you could allow IUSR_MachineName access to Page B then the user wouldn't be required to log in.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top