Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have an asp.net web application on a windows server 2003 box calling a web service on a different windows server 2003 box.

The web application and web service have disabled anonymous, use windows authentication and do not impersonate. The web application uses an app pool that runs with an identity xyz. The web service is set to only allow user xyz access. This allows us to secure the web service to only specific applications and/or users. Restricting the web service to a user that the application is running as also avoids the double hop problem.

This all works well on almost all of our servers, but we have one server that if we deploy the web service to, it will always deny authorization even. That web server is exactly the same code base, has the same settings and is configured exactly the same under iis as it is on all the other servers, yet it is the only deployment instance to does not seem to work.

I'm not sure if it's an IIS configuration issue, and AD issue, or a machine configuration issue. Any ideas?

Edit: None of our servers or AD users are set to allow delegation, but that shouldn't matter because this is a one hop scenario

share|improve this question
    
Have you done a wireshark trace on the end web service to see what's coming in from the screwy server? –  Christopher_G_Lewis Nov 13 '09 at 3:08
    
I haven't used wireshark. I will look into this. Thanks. –  Jeremy Nov 15 '09 at 20:41
    
Has anyone managed to solve this? –  Irfy Nov 25 '09 at 17:48
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.