ISA 2004 unexpectedly throws up username/password box.

Status
Not open for further replies.

thetechmind

Forerunner
Well , here is the problem , plsssss help cause this is causing havoc here.....
the scenario is simple , the users on the floor would be working on something flawlessly without any hitch and out of the blue all of a sudden for no reason at all the ISA server would start asking for authentication / username / password. Even after entering the same , the ISA would not authorise the same and slowly but surely all users start getting affected by the same problem.

The end solution for the same is to go ahead and - Restart the ISA services on the server along with the logon server services.

ISA Server runs -->
Windows 2003 SP2 /
ISA 2004 /
2 GB RAM /
NTLM v2 Authentication.

This happens every 3 hours without fail ! ....and causes a lot of problems and loss of productivity.

So genious's pls help n advise here.................back to some googling ....:@
 
^ i dont think so its free and secondly , i tried calling at this hr and got the reply...."pls try calling later" :P ....i need this resolved asap :(
 
It isn't free, but when you buy Windows you do get something in the form of after sales support.

I doubt you'd find anyone knowlegeable of ISA servers here. Good luck.
 
KingKrool said:
It isn't free, but when you buy Windows you do get something in the form of after sales support.
I doubt you'd find anyone knowlegeable of ISA servers here. Good luck.

why not , am sure we have a lot of sys admins here :ohyeah: .....did some googling and it helped , some policy changes made over authentication , will c how it works tomorrow , any other suggestions please fed in....
 
Well, first off, how long has this problem been occurring? Is the use of ISA server new, or have you been running it for some time, and this has just started? The thing is, if you have been using it without problems, and this has just started, either someone has changed the settings of the server, or a file has been patched/corrupted. I think you should be able to get an idea by looking at the event logs (they should indicate when this problem started happening). Working backwards, you can figure some of it out.

Also, check you disk. Something may have corrupted some files. chkdsk can do wonders.
 
Status
Not open for further replies.