NTLM Authentication not working (400 and 500)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Hi I have a simple Client:
using System;
using System.ServiceModel;
using System.ServiceModel.Description;
namespace Ntlm
{
public class Program
{
#region Methods
private static void Main()
{
var t = new Program();
Console.WriteLine("Starting....");
t.Run();
}
private void Run()
{
// First procedure:
// create a WSHttpBinding that uses Windows credentials and message security
var myBinding = new WSHttpBinding
{
Security =
{
Mode = SecurityMode.Message, Message = {ClientCredentialType = MessageCredentialType.Windows}
}
};
// 2nd Procedure:
// Use the binding in a service
// Create the Type instances for later use and the URI for
// the base address.
var contractType = typeof(ICalculator);
var serviceType = typeof(Calculator);
var baseAddress = new Uri("http://localhost:8036/SecuritySamples");
// Create the ServiceHost and add an endpoint, then start
// the service.
var myServiceHost = new ServiceHost(serviceType, baseAddress);
myServiceHost.AddServiceEndpoint(contractType, myBinding, "secureCalculator");
//enable metadata
var smb = new ServiceMetadataBehavior {HttpGetEnabled = true};
myServiceHost.Description.Behaviors.Add(smb);
myServiceHost.Open();
Console.WriteLine("Listening");
Console.WriteLine("Press Enter to close the service");
Console.ReadLine();
myServiceHost.Close();
}
#endregion
}
[ServiceContract]
public interface ICalculator
{
#region Public Methods and Operators
[OperationContract]
double Add(double a, double b);
#endregion
}
public class Calculator : ICalculator
{
#region Public Methods and Operators
public double Add(double a, double b)
{
return a + b;
}
#endregion
}
}
and in the app.config there is nothing other than the system.diagnostics
now, I am trying to send a
HttpWebRequest
to get a response from this service. The Wcf Test Client can to this of course, it authenticates itself with this service while scanning the service and then sends a request like this:
<s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Header>
<a:Action s:mustUnderstand="1">http://tempuri.org/ICalculator/Add</a:Action>
<a:MessageID>urn:uuid:dcac8c1e-b552-4011-8cf6-a0d3829aec71</a:MessageID>
<a:ReplyTo>
<a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
</a:ReplyTo>
</s:Header>
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>0</a>
<b>0</b>
</Add>
</s:Body>
</s:Envelope>
NOW: depending on what I send i get different results with the NTLM authentication
CASE 1:
I send the request
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>1</a>
<b>1</b>
</Add>
</s:Body>
</s:Envelope>
with the headers
Content-Type application/soap+xml;charset=utf-8;action="http://tempuri.org/ICalculator/Add"
I get a 400 Bad Request, and this is how I send it:
var req = WebRequest.CreateHttp(m.GetUri());
req.Timeout = Timeout;
req.AllowAutoRedirect = m.AutoRedirect;
req.Method = "Post";
req.AuthenticationLevel = AuthenticationLevel.MutualAuthRequested;
req.Credentials = new CredentialCache {
{ Destination.Host, Destination.Port, "NTLM", new NetworkCredential(Config.Username, Config.Password, Config.AuthenticationDomain) },
};
req.Proxy.Credentials = request.Credentials;
req.ContentType = "application/soap+xml;charset=utf-8;action="http://tempuri.org/ICalculator/Add""
CASE 2: I send the payload
<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"><Header xmlns="http://www.w3.org/2003/05/soap-envelope"><Action xmlns="http://www.w3.org/2005/08/addressing">http://tempuri.org/ICalculator/Add</Action></Header>
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>1</a>
<b>1</b>
</Add>
</s:Body>
</s:Envelope>
with the same settings as above, and I get 500 Internal Server Error
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/fault</a:Action>
</s:Header>
<s:Body>
<s:Fault>
<s:Code>
<s:Value>s:Sender</s:Value>
<s:Subcode>
<s:Value xmlns:a="http://schemas.xmlsoap.org/ws/2005/02/sc">a:BadContextToken</s:Value>
</s:Subcode>
</s:Code>
<s:Reason>
<s:Text xml:lang="de-AT">The message could not be processed. This is most likely because the action 'http://tempuri.org/ICalculator/Add' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.</s:Text>
</s:Reason>
</s:Fault>
</s:Body>
</s:Envelope>
After analyzing the WCF logs, fiddler, and wireshark, I can see that the message is send bare in my case, and the challenge is not arriving somehow, and no 401 for my code. what is the problem? I have the same problem with Kerberos as well
wcf soap soap-client ntlm ntlm-authentication
add a comment |
Hi I have a simple Client:
using System;
using System.ServiceModel;
using System.ServiceModel.Description;
namespace Ntlm
{
public class Program
{
#region Methods
private static void Main()
{
var t = new Program();
Console.WriteLine("Starting....");
t.Run();
}
private void Run()
{
// First procedure:
// create a WSHttpBinding that uses Windows credentials and message security
var myBinding = new WSHttpBinding
{
Security =
{
Mode = SecurityMode.Message, Message = {ClientCredentialType = MessageCredentialType.Windows}
}
};
// 2nd Procedure:
// Use the binding in a service
// Create the Type instances for later use and the URI for
// the base address.
var contractType = typeof(ICalculator);
var serviceType = typeof(Calculator);
var baseAddress = new Uri("http://localhost:8036/SecuritySamples");
// Create the ServiceHost and add an endpoint, then start
// the service.
var myServiceHost = new ServiceHost(serviceType, baseAddress);
myServiceHost.AddServiceEndpoint(contractType, myBinding, "secureCalculator");
//enable metadata
var smb = new ServiceMetadataBehavior {HttpGetEnabled = true};
myServiceHost.Description.Behaviors.Add(smb);
myServiceHost.Open();
Console.WriteLine("Listening");
Console.WriteLine("Press Enter to close the service");
Console.ReadLine();
myServiceHost.Close();
}
#endregion
}
[ServiceContract]
public interface ICalculator
{
#region Public Methods and Operators
[OperationContract]
double Add(double a, double b);
#endregion
}
public class Calculator : ICalculator
{
#region Public Methods and Operators
public double Add(double a, double b)
{
return a + b;
}
#endregion
}
}
and in the app.config there is nothing other than the system.diagnostics
now, I am trying to send a
HttpWebRequest
to get a response from this service. The Wcf Test Client can to this of course, it authenticates itself with this service while scanning the service and then sends a request like this:
<s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Header>
<a:Action s:mustUnderstand="1">http://tempuri.org/ICalculator/Add</a:Action>
<a:MessageID>urn:uuid:dcac8c1e-b552-4011-8cf6-a0d3829aec71</a:MessageID>
<a:ReplyTo>
<a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
</a:ReplyTo>
</s:Header>
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>0</a>
<b>0</b>
</Add>
</s:Body>
</s:Envelope>
NOW: depending on what I send i get different results with the NTLM authentication
CASE 1:
I send the request
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>1</a>
<b>1</b>
</Add>
</s:Body>
</s:Envelope>
with the headers
Content-Type application/soap+xml;charset=utf-8;action="http://tempuri.org/ICalculator/Add"
I get a 400 Bad Request, and this is how I send it:
var req = WebRequest.CreateHttp(m.GetUri());
req.Timeout = Timeout;
req.AllowAutoRedirect = m.AutoRedirect;
req.Method = "Post";
req.AuthenticationLevel = AuthenticationLevel.MutualAuthRequested;
req.Credentials = new CredentialCache {
{ Destination.Host, Destination.Port, "NTLM", new NetworkCredential(Config.Username, Config.Password, Config.AuthenticationDomain) },
};
req.Proxy.Credentials = request.Credentials;
req.ContentType = "application/soap+xml;charset=utf-8;action="http://tempuri.org/ICalculator/Add""
CASE 2: I send the payload
<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"><Header xmlns="http://www.w3.org/2003/05/soap-envelope"><Action xmlns="http://www.w3.org/2005/08/addressing">http://tempuri.org/ICalculator/Add</Action></Header>
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>1</a>
<b>1</b>
</Add>
</s:Body>
</s:Envelope>
with the same settings as above, and I get 500 Internal Server Error
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/fault</a:Action>
</s:Header>
<s:Body>
<s:Fault>
<s:Code>
<s:Value>s:Sender</s:Value>
<s:Subcode>
<s:Value xmlns:a="http://schemas.xmlsoap.org/ws/2005/02/sc">a:BadContextToken</s:Value>
</s:Subcode>
</s:Code>
<s:Reason>
<s:Text xml:lang="de-AT">The message could not be processed. This is most likely because the action 'http://tempuri.org/ICalculator/Add' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.</s:Text>
</s:Reason>
</s:Fault>
</s:Body>
</s:Envelope>
After analyzing the WCF logs, fiddler, and wireshark, I can see that the message is send bare in my case, and the challenge is not arriving somehow, and no 401 for my code. what is the problem? I have the same problem with Kerberos as well
wcf soap soap-client ntlm ntlm-authentication
add a comment |
Hi I have a simple Client:
using System;
using System.ServiceModel;
using System.ServiceModel.Description;
namespace Ntlm
{
public class Program
{
#region Methods
private static void Main()
{
var t = new Program();
Console.WriteLine("Starting....");
t.Run();
}
private void Run()
{
// First procedure:
// create a WSHttpBinding that uses Windows credentials and message security
var myBinding = new WSHttpBinding
{
Security =
{
Mode = SecurityMode.Message, Message = {ClientCredentialType = MessageCredentialType.Windows}
}
};
// 2nd Procedure:
// Use the binding in a service
// Create the Type instances for later use and the URI for
// the base address.
var contractType = typeof(ICalculator);
var serviceType = typeof(Calculator);
var baseAddress = new Uri("http://localhost:8036/SecuritySamples");
// Create the ServiceHost and add an endpoint, then start
// the service.
var myServiceHost = new ServiceHost(serviceType, baseAddress);
myServiceHost.AddServiceEndpoint(contractType, myBinding, "secureCalculator");
//enable metadata
var smb = new ServiceMetadataBehavior {HttpGetEnabled = true};
myServiceHost.Description.Behaviors.Add(smb);
myServiceHost.Open();
Console.WriteLine("Listening");
Console.WriteLine("Press Enter to close the service");
Console.ReadLine();
myServiceHost.Close();
}
#endregion
}
[ServiceContract]
public interface ICalculator
{
#region Public Methods and Operators
[OperationContract]
double Add(double a, double b);
#endregion
}
public class Calculator : ICalculator
{
#region Public Methods and Operators
public double Add(double a, double b)
{
return a + b;
}
#endregion
}
}
and in the app.config there is nothing other than the system.diagnostics
now, I am trying to send a
HttpWebRequest
to get a response from this service. The Wcf Test Client can to this of course, it authenticates itself with this service while scanning the service and then sends a request like this:
<s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Header>
<a:Action s:mustUnderstand="1">http://tempuri.org/ICalculator/Add</a:Action>
<a:MessageID>urn:uuid:dcac8c1e-b552-4011-8cf6-a0d3829aec71</a:MessageID>
<a:ReplyTo>
<a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
</a:ReplyTo>
</s:Header>
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>0</a>
<b>0</b>
</Add>
</s:Body>
</s:Envelope>
NOW: depending on what I send i get different results with the NTLM authentication
CASE 1:
I send the request
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>1</a>
<b>1</b>
</Add>
</s:Body>
</s:Envelope>
with the headers
Content-Type application/soap+xml;charset=utf-8;action="http://tempuri.org/ICalculator/Add"
I get a 400 Bad Request, and this is how I send it:
var req = WebRequest.CreateHttp(m.GetUri());
req.Timeout = Timeout;
req.AllowAutoRedirect = m.AutoRedirect;
req.Method = "Post";
req.AuthenticationLevel = AuthenticationLevel.MutualAuthRequested;
req.Credentials = new CredentialCache {
{ Destination.Host, Destination.Port, "NTLM", new NetworkCredential(Config.Username, Config.Password, Config.AuthenticationDomain) },
};
req.Proxy.Credentials = request.Credentials;
req.ContentType = "application/soap+xml;charset=utf-8;action="http://tempuri.org/ICalculator/Add""
CASE 2: I send the payload
<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"><Header xmlns="http://www.w3.org/2003/05/soap-envelope"><Action xmlns="http://www.w3.org/2005/08/addressing">http://tempuri.org/ICalculator/Add</Action></Header>
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>1</a>
<b>1</b>
</Add>
</s:Body>
</s:Envelope>
with the same settings as above, and I get 500 Internal Server Error
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/fault</a:Action>
</s:Header>
<s:Body>
<s:Fault>
<s:Code>
<s:Value>s:Sender</s:Value>
<s:Subcode>
<s:Value xmlns:a="http://schemas.xmlsoap.org/ws/2005/02/sc">a:BadContextToken</s:Value>
</s:Subcode>
</s:Code>
<s:Reason>
<s:Text xml:lang="de-AT">The message could not be processed. This is most likely because the action 'http://tempuri.org/ICalculator/Add' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.</s:Text>
</s:Reason>
</s:Fault>
</s:Body>
</s:Envelope>
After analyzing the WCF logs, fiddler, and wireshark, I can see that the message is send bare in my case, and the challenge is not arriving somehow, and no 401 for my code. what is the problem? I have the same problem with Kerberos as well
wcf soap soap-client ntlm ntlm-authentication
Hi I have a simple Client:
using System;
using System.ServiceModel;
using System.ServiceModel.Description;
namespace Ntlm
{
public class Program
{
#region Methods
private static void Main()
{
var t = new Program();
Console.WriteLine("Starting....");
t.Run();
}
private void Run()
{
// First procedure:
// create a WSHttpBinding that uses Windows credentials and message security
var myBinding = new WSHttpBinding
{
Security =
{
Mode = SecurityMode.Message, Message = {ClientCredentialType = MessageCredentialType.Windows}
}
};
// 2nd Procedure:
// Use the binding in a service
// Create the Type instances for later use and the URI for
// the base address.
var contractType = typeof(ICalculator);
var serviceType = typeof(Calculator);
var baseAddress = new Uri("http://localhost:8036/SecuritySamples");
// Create the ServiceHost and add an endpoint, then start
// the service.
var myServiceHost = new ServiceHost(serviceType, baseAddress);
myServiceHost.AddServiceEndpoint(contractType, myBinding, "secureCalculator");
//enable metadata
var smb = new ServiceMetadataBehavior {HttpGetEnabled = true};
myServiceHost.Description.Behaviors.Add(smb);
myServiceHost.Open();
Console.WriteLine("Listening");
Console.WriteLine("Press Enter to close the service");
Console.ReadLine();
myServiceHost.Close();
}
#endregion
}
[ServiceContract]
public interface ICalculator
{
#region Public Methods and Operators
[OperationContract]
double Add(double a, double b);
#endregion
}
public class Calculator : ICalculator
{
#region Public Methods and Operators
public double Add(double a, double b)
{
return a + b;
}
#endregion
}
}
and in the app.config there is nothing other than the system.diagnostics
now, I am trying to send a
HttpWebRequest
to get a response from this service. The Wcf Test Client can to this of course, it authenticates itself with this service while scanning the service and then sends a request like this:
<s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing" xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Header>
<a:Action s:mustUnderstand="1">http://tempuri.org/ICalculator/Add</a:Action>
<a:MessageID>urn:uuid:dcac8c1e-b552-4011-8cf6-a0d3829aec71</a:MessageID>
<a:ReplyTo>
<a:Address>http://www.w3.org/2005/08/addressing/anonymous</a:Address>
</a:ReplyTo>
</s:Header>
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>0</a>
<b>0</b>
</Add>
</s:Body>
</s:Envelope>
NOW: depending on what I send i get different results with the NTLM authentication
CASE 1:
I send the request
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>1</a>
<b>1</b>
</Add>
</s:Body>
</s:Envelope>
with the headers
Content-Type application/soap+xml;charset=utf-8;action="http://tempuri.org/ICalculator/Add"
I get a 400 Bad Request, and this is how I send it:
var req = WebRequest.CreateHttp(m.GetUri());
req.Timeout = Timeout;
req.AllowAutoRedirect = m.AutoRedirect;
req.Method = "Post";
req.AuthenticationLevel = AuthenticationLevel.MutualAuthRequested;
req.Credentials = new CredentialCache {
{ Destination.Host, Destination.Port, "NTLM", new NetworkCredential(Config.Username, Config.Password, Config.AuthenticationDomain) },
};
req.Proxy.Credentials = request.Credentials;
req.ContentType = "application/soap+xml;charset=utf-8;action="http://tempuri.org/ICalculator/Add""
CASE 2: I send the payload
<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"><Header xmlns="http://www.w3.org/2003/05/soap-envelope"><Action xmlns="http://www.w3.org/2005/08/addressing">http://tempuri.org/ICalculator/Add</Action></Header>
<s:Body>
<Add xmlns="http://tempuri.org/">
<a>1</a>
<b>1</b>
</Add>
</s:Body>
</s:Envelope>
with the same settings as above, and I get 500 Internal Server Error
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
<s:Header>
<a:Action s:mustUnderstand="1">http://www.w3.org/2005/08/addressing/soap/fault</a:Action>
</s:Header>
<s:Body>
<s:Fault>
<s:Code>
<s:Value>s:Sender</s:Value>
<s:Subcode>
<s:Value xmlns:a="http://schemas.xmlsoap.org/ws/2005/02/sc">a:BadContextToken</s:Value>
</s:Subcode>
</s:Code>
<s:Reason>
<s:Text xml:lang="de-AT">The message could not be processed. This is most likely because the action 'http://tempuri.org/ICalculator/Add' is incorrect or because the message contains an invalid or expired security context token or because there is a mismatch between bindings. The security context token would be invalid if the service aborted the channel due to inactivity. To prevent the service from aborting idle sessions prematurely increase the Receive timeout on the service endpoint's binding.</s:Text>
</s:Reason>
</s:Fault>
</s:Body>
</s:Envelope>
After analyzing the WCF logs, fiddler, and wireshark, I can see that the message is send bare in my case, and the challenge is not arriving somehow, and no 401 for my code. what is the problem? I have the same problem with Kerberos as well
wcf soap soap-client ntlm ntlm-authentication
wcf soap soap-client ntlm ntlm-authentication
asked Nov 26 '18 at 13:36
Omid Chini ForoushanOmid Chini Foroushan
11
11
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53482318%2fntlm-authentication-not-working-400-and-500%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53482318%2fntlm-authentication-not-working-400-and-500%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown