I don't know the configuration details of your test environment, but it might be that the domain account you're using may not be allowed to log on to the server computer (non-admins can't, by default). If you're trying to start and run a process on the server computer as an unprivileged user, that could explain what you're seeing.

If you can RDP into a workstation on that same network, and put some debug code in your ASP.NET app you could hit your app from the workstation and see what happens.

>Some of you may have seen a couple of threads I created where I am trying to make my ASP.NET page to read the domain username who is currently logged into PC. It does not work by default.
>
>So, I asked the customer IT guy to create a domain account and give me credentials so that I can impersonate this account and make my ASP.NET page run with the credentials of this account. The IT guy did that and I set up impersonation (in web.config file). He created account TestAcct. I impersonate that account as DomainName\TestAcct and entered password. But then when I run the page, I get an error:
>

>Could not created Windows user token for the credentials specified in the configuration file.  
>The referenced account is currently locked out and may not be logged on to
>

>
>Then I tried to set up impersonation for a couple of other valid domain usernames/accounts that this organization has. And the same error message. So, I am doubtful the the account is really locked.
>
>Any ideas of where I should look for? Or tell the IT guy to look for?
>
>TIA for any input.