A wierd thing happened to our server

[HairyMonkeyMan]

I have an application thats been ticking away nicely on our server (MS Windows Server 2003). The application uses windows authentication for users - so they are not asked for usernames and passwords as they are authenticated as whatever user they are signed into their workstation as.

We had a full system crash yesterday, and ever since this application has been asking users to authenticate themselves.

I've been through all the settings and everything is still set for windows authentication, but its not working for some reason. Anyone have any idea why it mightn't be working?

I'm just about to call in the big guns on this one, and thats going to cost quite a few £££. Thanks for your time :wave:

[mcmcom]

is the application just producing the standard windows login and password? if so does it STILL ask even if you click the "Remember my password" feature? Is the server back on the domain fully? as a member of the win domain or a PDC?

mcm

[HairyMonkeyMan]

Thanks for your reply mcmcom.

Yes, it is the standard msie login box. I should have said that users are unable to login though (even with the correct details supplied).

I am getting a few errors in the event log:

Event code: 4008
Event message: File authorization failed for the request.
Event time: 21/12/2006 15:36:14
Event time (UTC): 21/12/2006 15:36:14
Event ID: e7a12b18f51545fc99e9a9ad57548aed
Event sequence: 7
Event occurrence: 3
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1962384230/Root-2-128111888653855559
Trust level: Full
Application Virtual Path: /
Application Path: C:\Inetpub\pmacs\
Machine name: SERVERMND

Process information:
Process ID: 11148
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Request information:
Request URL: http://pmacs/TimeEntry.aspx
Request path: /TimeEntry.aspx
User host address: 192.168.1.137
User: MND\michael.eller
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE

I'll check whether its back on the domain fully.. But I imagine it is. Theres an exchange server on the same machine and its also a fileserver.. there are no problems with anything else.

Thanks for the help buddy :wave: