Home/ Questions/Q 645157
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T21:28:17+00:00

When I am running a WCF service on my development machine it works as

  • 0

When I am running a WCF service on my development machine it works as long as the client is connected to the domain.

When the machine is disconnected I get the following exception:

System.ServiceModel.Security.SecurityNegotiationException: A call to SSPI failed, see inner exception.
System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. —>
System.ComponentModel.Win32Exception: The system detected a possible attempt to compromise security.
Please ensure that you can contact the server that authenticated you

The service uses security internally (<transport clientCredentialType="Windows" protectionLevel="None"/>) so I can’t easily turn it off.

Is there a way to work around this problem so I can test the service when I am not connected?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Probably won’t work when not connected to the domain.

    The default WCF security for several bindings is “Windows”, e.g. your current user credentials are being passed to the WCF service and the service then attempts to validate those user credentials against the Windows domain.

    If you’re not connected, that verification can’t happen, so the WCF service will refuse the call. Works as designed, I’d say 🙂

    Maybe you could expose a second endpoint for your service (“local dev testing”) that doesn’t require Windows authentication? When off the domain, just connect to that non-secured endpoint so that you can at least test the service and its inner workings.

    • 0