StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>You can eliminate the client from the problem by using <a href="http://support.microsoft.com/kb/284285">wftech</a>, this is an old tool but I have found it useful in diagnosing authentication issues. wfetch allows you to specify NTLM, Negotiate and kerberos, this may well help you better understand your problem. As you are trying to call a service and wfetch knows nothing about WCF, I would suggest applying your endpoint binding (PROVIDERSSoapBinding) to the <a href="http://msdn.microsoft.com/en-us/library/ms731317.aspx">serviceMetadata</a> then you can do an HTTP GET of the WSDL for the service with the same security settings. </p> <p>Another option, which may be available to you is to force the server to use NTLM, you can do this by either editing the metabase (IIS 6) and removing the Negotiate setting, more details at <a href="http://support.microsoft.com/kb/215383">http://support.microsoft.com/kb/215383</a>.</p> <p>If you are using IIS 7.x then the approach is slightly different, details of how to configure the authentication providers are here <a href="http://www.iis.net/configreference/system.webserver/security/authentication/windowsauthentication">http://www.iis.net/configreference/system.webserver/security/authentication/windowsauthentication</a>.</p> <p>I notice that you have blocked out the server address with xxx.xx.xx.xxx, so I'm guessing that this is an IP address rather than a server name, this may cause issues with authentication, so if possible try targeting the machine name.</p> <p>Sorry that I haven't given you the answer but rather pointers for getting closer to the issue, but I hope it helps.</p> <p>I'll finish by saying that I have experienced this same issue and my only recourse was to use Kerberos rather than NTLM, don't forget you'll need to register an SPN for the service if you do go down this route. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload