But it throw a exception:
org.ntlmv2.liferay.NtlmLogonException:unable to authenticate due to communication failure with server
at org.ntlmv2.liferay.Netlogon.logon(Netlogon.java :96)
...
caused by :jcifs.smb.SmbAuthException: Logon failure: unknown user name or bad password.
...
And when i ping 168.168.12.4 from the Client,The reply immediately.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
The error message is pretty clear: "unknown user name or bad password". This means that the communication with the domain controller works perfectly fine. For some reason, it denies the access. At least that is my experience with this error message. I admit that the "due to communication failure with server" part is irritating, though.
Still, I assume it's not really a communication issue. If it is really an authentication error, you should see something in the logs of the domain controller (although that is a pain in the ass to find out sometimes). Maybe the Windows authentication level settings on the client and the DC do not correspond?
One question about your config: "fengmeng-3eef01" is the DNS hostname of your domain controller, right? Also, is the name of your Windows (!) domain really "demo.com"? Because in that setting, you have to define the Windows domain, NOT the DNS domain name.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have use ntlmv2-auth in our work,but it's throw a exception when i run it.
I think filter's configuration is not right,But i can't find it.
my domain controler's infomation:
domain : demo.com
IP : 168.168.12.4
computerName : fengmeng-3eef01
acountName : Administrator
password : fengmeng1!
my filter configuration:
<filter>
<filter-name>ntlmv2-auth</filter-name>
<filter-class>org.ntlmv2.filter.NtlmFilter</filter-class>
<init-param>
<param-name>ntlm-domain</param-name>
<param-value>demo.com</param-value>
</init-param>
<init-param>
<param-name>ntlm-dc</param-name>
<param-value>168.168.12.4</param-value>
</init-param>
<init-param>
<param-name>ntlm-dc-name</param-name>
<param-value>fengmeng-3eef01</param-value>
</init-param>
<init-param>
<param-name>ntlm-account</param-name>
<param-value>Administrator$@demo.com</param-value>
</init-param>
<init-param>
<param-name>ntlm-password</param-name>
<param-value>fengmeng1!</param-value>
</init-param>
</filter>
But it throw a exception:
org.ntlmv2.liferay.NtlmLogonException:unable to authenticate due to communication failure with server
at org.ntlmv2.liferay.Netlogon.logon(Netlogon.java :96)
...
caused by :jcifs.smb.SmbAuthException: Logon failure: unknown user name or bad password.
...
And when i ping 168.168.12.4 from the Client,The reply immediately.
Hi,
The error message is pretty clear: "unknown user name or bad password". This means that the communication with the domain controller works perfectly fine. For some reason, it denies the access. At least that is my experience with this error message. I admit that the "due to communication failure with server" part is irritating, though.
Still, I assume it's not really a communication issue. If it is really an authentication error, you should see something in the logs of the domain controller (although that is a pain in the ass to find out sometimes). Maybe the Windows authentication level settings on the client and the DC do not correspond?
One question about your config: "fengmeng-3eef01" is the DNS hostname of your domain controller, right? Also, is the name of your Windows (!) domain really "demo.com"? Because in that setting, you have to define the Windows domain, NOT the DNS domain name.