At the moment we identified that the error is due to security issues.

The old server ServerA managed to communicate with WebServerC without problems, now the new server ServerB can connect but the provided credentials are not enough for it to access WebServerC which has the Web Service.

ServerA –> WebServerC (Connection OK and Security OK)
ServerB –> WebServerC (Connection OK and Security Failed) Instead of showing the Web Service it shows the asp.net "Login" screen.

This is all under a Corporate Active Directory with Windows Server 2008. What could be the problem? ServerA has nothing special and ServerB is new but the App running is the same.

  • What exact error-message were you getting on ServerB? Were you getting any error-messages on ServerC? – david Jun 30 '15 at 19:47

Probably for ServerB the flag Trusted For Delegation is not set. In this case a user can be authenticated on the ServerB, but ServerB can't use this credential to authenticate on the WebServerC.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.