You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Seema Patel <se...@hotmail.com> on 2013/08/01 10:25:42 UTC

java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

Hi,
 
I am not sure if this is the right List to post this on, please advise if it isn't and let me know where is best to post.
 
I am getting the following error on one of our applications running on our intranet:
 
2013-07-31 17:15:11,180 [http-xxx.xxx.x.xxx-xx-x] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/forms].[action] - Servlet.service() for servlet action threw exception
java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx.LOCAL
at jcifs.smb.SmbSession.getChallengeForDomain(SmbSession.java:187)
at jcifs.http.NtlmHttpFilter.negotiate(NtlmHttpFilter.java:150)
at jcifs.http.NtlmHttpFilter.doFilter(NtlmHttpFilter.java:114)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:465)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:837)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:640)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1287)
at java.lang.Thread.run(Unknown Source)
 
In my tomcat/conf/server.xml file I have:
 
<Realm className="com.viatel.tomcatrealms.ADJNDIRealm"
debug="01" resourceName="ActiveDirectory"
connectionURL="ldap://xxx:xxx"
alternativeURL="ldap://xxx:xxx"
connectionName="LDAP@xxx.local" connectionPassword="xxx"
referrals="follow" userBase="dc=vtlwavenet,dc=local"
userSearch="(sAMAccountName={0})" userSubtree="true"
roleBase="dc=xxx,dc=local" roleSearch="(member={0})"
roleName="cn" roleSubtree="true" />
 
I have 2 .war files running from this tomcat - 1) intranet portal A, 2) intranet helpdesk page and also another intranet portal B (both run from slightly different URLs).
When tomcat was restarted the intranet portal A runs, intranet portal B runs but the intranet helpdesk portal doesn't run.  For this we get the error message shown above.
 
I don't know if it is the java code, some setting in the tomcat catalina base or if it is a tomcat network issue.
 
We are running Tomcat 5.5.29.
java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode, sharing) 
It is on a Windows Server 2003 R2 SP2 VM box.
 
Any help on this is appreciated.
Thanks in advance
 
Seema
 
 
 
 		 	   		  

Re: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

Posted by David kerber <dc...@verizon.net>.
On 8/1/2013 2:24 PM, Caldarale, Charles R wrote:
>> From: Seema Patel [mailto:seema165@hotmail.com]
>> Subject: RE: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx
>
>> When upgrading Tomcat from version 5.5 to 7, would I need to upgrade to
>> version 6 first and then to 7 or can I go straight from 5.5 to 7?
>
> Do it in one step - there's no point in doing it twice.  The migration guide is here:

Yep, it will just about twice as long to do it in two steps as it does 
to do it in one.  Ask me how I know this...



>
> http://tomcat.apache.org/migration.html
>
> It doesn't specifically cover going from 5.5 to 7.0, so read all the sections before proceeding.
>
>   - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Seema Patel [mailto:seema165@hotmail.com] 
> Subject: RE: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

> When upgrading Tomcat from version 5.5 to 7, would I need to upgrade to 
> version 6 first and then to 7 or can I go straight from 5.5 to 7?

Do it in one step - there's no point in doing it twice.  The migration guide is here:

http://tomcat.apache.org/migration.html

It doesn't specifically cover going from 5.5 to 7.0, so read all the sections before proceeding.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

Posted by Seema Patel <se...@hotmail.com>.

> Date: Thu, 1 Aug 2013 15:55:37 +0200
> From: aw@ice-sa.com
> To: users@tomcat.apache.org
> Subject: Re: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx
> 
> Seema Patel wrote:
> > 
> >> Date: Thu, 1 Aug 2013 12:06:39 +0200
> >> From: aw@ice-sa.com
> >> To: users@tomcat.apache.org
> >> Subject: Re: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx
> >>
> >> Seema Patel wrote:
> >>> Hi,
> >>>  
> >>> I am not sure if this is the right List to post this on, please advise if it isn't and let me know where is best to post.
> >>>  
> >>> I am getting the following error on one of our applications running on our intranet:
> >>>  
> >>> 2013-07-31 17:15:11,180 [http-xxx.xxx.x.xxx-xx-x] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/forms].[action] - Servlet.service() for servlet action threw exception
> >>> java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx.LOCAL
> >>> at jcifs.smb.SmbSession.getChallengeForDomain(SmbSession.java:187)
> >>> at jcifs.http.NtlmHttpFilter.negotiate(NtlmHttpFilter.java:150)
> >>> at jcifs.http.NtlmHttpFilter.doFilter(NtlmHttpFilter.java:114)
> >>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
> >>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> >>> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> >>> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
> >>> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:465)
> >>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> >>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> >>> at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
> >>> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> >>> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
> >>> at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:837)
> >>> at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:640)
> >>> at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1287)
> >>> at java.lang.Thread.run(Unknown Source)
> >>>  
> >> I believe that you should read this page carefully, in particular the blue text at the 
> >> beginning : http://jcifs.samba.org/src/docs/ntlmhttpauth.html
> >>
> >> Can you have a look at the WEB-INF/web.xml file *of your application*, and check if there 
> >> is a servlet filter configured there, which matches the name above ?
> >>
> >> If so, make a backup copy of that web.xml file, and then edit it to remove that filter 
> >> from it, and try again.
> >> I am not quite sure, but it looks possible to me that you have a duplicate authentication 
> >> mechanism in use : one at the container (Tomcat) level, and one at the application level.
> >> And the one used at the application level is obsolete, unsupported, unmaintained etc..
> >>
> > 
> > I have found out that JCIFS is no longer supported, but it will take a lot of time, development and resources to update it to the recommended Jespa.  In my web.xml file I have the following:
> > 
> > <filter>
> >         <filter-name>NtlmHttpFilter</filter-name>
> >         <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
> >            
> >         <!--
> >             always needed for preauthentication / SMB signatures
> >         -->
> >         <init-param>
> >             <param-name>jcifs.smb.client.domain</param-name>
> >             <param-value>xxx</param-value>
> >         </init-param>
> >         <!-- SMB message signing requires a valid existing login -->
> >         <init-param>
> >             <param-name>jcifs.smb.client.username</param-name>
> >             <param-value>xxx</param-value>
> >         </init-param>
> >         <init-param>
> >             <param-name>jcifs.smb.client.password</param-name>
> >             <param-value>xxx</param-value>
> >         </init-param>
> >         <!-- Set the logging level -->
> >         <init-param>
> >             <param-name>jcifs.util.loglevel</param-name>
> >             <param-value>3</param-value>
> >         </init-param>
> >         <!--  allow non-IE browsers to use basic auth -->
> >         <init-param>
> >             <param-name>jcifs.http.insecureBasic</param-name>
> >             <param-value>true</param-value>
> >         </init-param>
> >     </filter>
> >     <filter>
> >         <filter-name>HRADGroupFilter</filter-name>
> >         <filter-class>xxx.ADGroupFilter</filter-class>
> >         <init-param>
> >             <param-name>AllowedGroups</param-name>
> >             <param-value>G-HR,G-MIS</param-value>
> >         </init-param>
> >     </filter>
> >         <filter>
> >         <filter-name>SuggestionsGroupFilter</filter-name>
> >         <filter-class>xxx.ADGroupFilter</filter-class>
> >         <init-param>
> >             <param-name>AllowedGroups</param-name>
> >             <param-value>xxx, xxx</param-value>
> >         </init-param>
> >     </filter>
> >     
> >     <filter-mapping>
> >         <filter-name>NtlmHttpFilter</filter-name>
> >         <url-pattern>/suggestions/*</url-pattern>
> >     </filter-mapping>
> >     <filter-mapping>
> >         <filter-name>SuggestionsGroupFilter</filter-name>
> >         <url-pattern>/suggestions/*</url-pattern>
> >     </filter-mapping>
> >     <filter-mapping>
> >         <filter-name>NtlmHttpFilter</filter-name>
> >         <url-pattern>/xxx/*</url-pattern>
> >     </filter-mapping>
> >     <filter-mapping>
> >         <filter-name>HRADGroupFilter</filter-name>
> >         <url-pattern>/xxx/xxx.do</url-pattern>
> >     </filter-mapping>
> > 
> > 
> > So, are you saying to just remove the following from the above?:
> >        <filter-name>NtlmHttpFilter</filter-name>
> >        <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
> > 
> > Is there anything else in there that needs to be removed?  Sorry for my lack of understanding, but this was all developed by previous developers, who are no longer working here and have left no documentation.
> > 
> 
> Neither I nor the other contributors on this list knows what your application(s) really 
> do, nor how your whole system really fits together.
> In addition, this list is for the support of Tomcat, and your issue is not really with 
> Tomcat, but seems to be really at the application level and how this application
> a) performs user authentication
> b) later uses the results of the user authentication
> The fact that there is no documentation and that the relevant delevelopers have left is a 
> pity, but not really something we can do anything about.
> 
> What I really suggest, if this application is important for you (and apart from what Chuck 
> already mentioned) is this : get in touch with the Jespa authors, at www.ioplex.com (email 
> : support@ioplex.com) , present the issue to them, and ask them how they could help.
> 
> Maybe first though : download the Jespa Operator's Guide from their website, and read it.
> That will already tell you a lot of what you need to know.
> 
> Replacing the jCIFS HTTP filter by Jespa is not very hard, and mostly consists of 
> installing Jespa and modifying the web.xml to use the Jespa filter instead of the jCIFS 
> filter.  That would be the following sections of your current web.xml :
> 
>  > <filter>
>  >         <filter-name>NtlmHttpFilter</filter-name>
>  >         <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
>  >
>  >         <!--
>  >             always needed for preauthentication / SMB signatures
>  >         -->
>  >         <init-param>
>  >             <param-name>jcifs.smb.client.domain</param-name>
>  >             <param-value>xxx</param-value>
>  >         </init-param>
>  >         <!-- SMB message signing requires a valid existing login -->
>  >         <init-param>
>  >             <param-name>jcifs.smb.client.username</param-name>
>  >             <param-value>xxx</param-value>
>  >         </init-param>
>  >         <init-param>
>  >             <param-name>jcifs.smb.client.password</param-name>
>  >             <param-value>xxx</param-value>
>  >         </init-param>
>  >         <!-- Set the logging level -->
>  >         <init-param>
>  >             <param-name>jcifs.util.loglevel</param-name>
>  >             <param-value>3</param-value>
>  >         </init-param>
>  >         <!--  allow non-IE browsers to use basic auth -->
>  >         <init-param>
>  >             <param-name>jcifs.http.insecureBasic</param-name>
>  >             <param-value>true</param-value>
>  >         </init-param>
>  >     </filter>
> 
> and
> 
>  >     <filter-mapping>
>  >         <filter-name>NtlmHttpFilter</filter-name>
>  >         <url-pattern>/suggestions/*</url-pattern>
>  >     </filter-mapping>
> 
> and
> 
>  >     <filter-mapping>
>  >         <filter-name>NtlmHttpFilter</filter-name>
>  >         <url-pattern>/xxx/*</url-pattern>
>  >     </filter-mapping>
> 
> The sections above have a direct equivalent with Jespa, and there should in principle not 
> be any code changes to make in your applications.
> Just the parameters in web.xml differ somewhat.
> 
> Both the jCIFS filter and the Jespa filter are servlet filters, and they basically do the 
> same thing :
> - authenticate the current user of the application with the Windows Domain Controllers 
> (and whatever is used as their back-end authentication mechanism)
> - "set" the internal "Tomcat user" to this user-id
> 
> Then, after that, runs the other filters that are configured above, and your application.
> What they do with whatever information the authentication filter (jCIFS or Jespa) has 
> passed to Tomcat, we do not know, and there could be a problem there (but more likely not).
> If there was a problem, then the people most likely to be able to help you are the Jespa guys.
> 
> 
> In theory, there could be another way : replace this "application-level" filter-based 
> authentication by a container-level authentication (and get rid of the filters), but in 
> your current situation, I believe that the Jespa solution is really the simplest one.
> 
> And, really, consider upgrading your Tomcat version.  Nothing which you are currently 
> using is supported anymore.

When upgrading Tomcat from version 5.5 to 7, would I need to upgrade to version 6 first and then to 7 or can I go straight from 5.5 to 7?
I will first try all this in a test environment.  Please bare with me, I may come back with further questions to your responses.
But thanks for all the feedback, its appreciated (especially as I'm a newbie to this). 



> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
 		 	   		  

Re: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

Posted by André Warnier <aw...@ice-sa.com>.
Seema Patel wrote:
> 
>> Date: Thu, 1 Aug 2013 12:06:39 +0200
>> From: aw@ice-sa.com
>> To: users@tomcat.apache.org
>> Subject: Re: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx
>>
>> Seema Patel wrote:
>>> Hi,
>>>  
>>> I am not sure if this is the right List to post this on, please advise if it isn't and let me know where is best to post.
>>>  
>>> I am getting the following error on one of our applications running on our intranet:
>>>  
>>> 2013-07-31 17:15:11,180 [http-xxx.xxx.x.xxx-xx-x] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/forms].[action] - Servlet.service() for servlet action threw exception
>>> java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx.LOCAL
>>> at jcifs.smb.SmbSession.getChallengeForDomain(SmbSession.java:187)
>>> at jcifs.http.NtlmHttpFilter.negotiate(NtlmHttpFilter.java:150)
>>> at jcifs.http.NtlmHttpFilter.doFilter(NtlmHttpFilter.java:114)
>>> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>>> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>>> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
>>> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
>>> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:465)
>>> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>>> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>>> at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
>>> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>>> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
>>> at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:837)
>>> at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:640)
>>> at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1287)
>>> at java.lang.Thread.run(Unknown Source)
>>>  
>> I believe that you should read this page carefully, in particular the blue text at the 
>> beginning : http://jcifs.samba.org/src/docs/ntlmhttpauth.html
>>
>> Can you have a look at the WEB-INF/web.xml file *of your application*, and check if there 
>> is a servlet filter configured there, which matches the name above ?
>>
>> If so, make a backup copy of that web.xml file, and then edit it to remove that filter 
>> from it, and try again.
>> I am not quite sure, but it looks possible to me that you have a duplicate authentication 
>> mechanism in use : one at the container (Tomcat) level, and one at the application level.
>> And the one used at the application level is obsolete, unsupported, unmaintained etc..
>>
> 
> I have found out that JCIFS is no longer supported, but it will take a lot of time, development and resources to update it to the recommended Jespa.  In my web.xml file I have the following:
> 
> <filter>
>         <filter-name>NtlmHttpFilter</filter-name>
>         <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
>            
>         <!--
>             always needed for preauthentication / SMB signatures
>         -->
>         <init-param>
>             <param-name>jcifs.smb.client.domain</param-name>
>             <param-value>xxx</param-value>
>         </init-param>
>         <!-- SMB message signing requires a valid existing login -->
>         <init-param>
>             <param-name>jcifs.smb.client.username</param-name>
>             <param-value>xxx</param-value>
>         </init-param>
>         <init-param>
>             <param-name>jcifs.smb.client.password</param-name>
>             <param-value>xxx</param-value>
>         </init-param>
>         <!-- Set the logging level -->
>         <init-param>
>             <param-name>jcifs.util.loglevel</param-name>
>             <param-value>3</param-value>
>         </init-param>
>         <!--  allow non-IE browsers to use basic auth -->
>         <init-param>
>             <param-name>jcifs.http.insecureBasic</param-name>
>             <param-value>true</param-value>
>         </init-param>
>     </filter>
>     <filter>
>         <filter-name>HRADGroupFilter</filter-name>
>         <filter-class>xxx.ADGroupFilter</filter-class>
>         <init-param>
>             <param-name>AllowedGroups</param-name>
>             <param-value>G-HR,G-MIS</param-value>
>         </init-param>
>     </filter>
>         <filter>
>         <filter-name>SuggestionsGroupFilter</filter-name>
>         <filter-class>xxx.ADGroupFilter</filter-class>
>         <init-param>
>             <param-name>AllowedGroups</param-name>
>             <param-value>xxx, xxx</param-value>
>         </init-param>
>     </filter>
>     
>     <filter-mapping>
>         <filter-name>NtlmHttpFilter</filter-name>
>         <url-pattern>/suggestions/*</url-pattern>
>     </filter-mapping>
>     <filter-mapping>
>         <filter-name>SuggestionsGroupFilter</filter-name>
>         <url-pattern>/suggestions/*</url-pattern>
>     </filter-mapping>
>     <filter-mapping>
>         <filter-name>NtlmHttpFilter</filter-name>
>         <url-pattern>/xxx/*</url-pattern>
>     </filter-mapping>
>     <filter-mapping>
>         <filter-name>HRADGroupFilter</filter-name>
>         <url-pattern>/xxx/xxx.do</url-pattern>
>     </filter-mapping>
> 
> 
> So, are you saying to just remove the following from the above?:
>        <filter-name>NtlmHttpFilter</filter-name>
>        <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
> 
> Is there anything else in there that needs to be removed?  Sorry for my lack of understanding, but this was all developed by previous developers, who are no longer working here and have left no documentation.
> 

Neither I nor the other contributors on this list knows what your application(s) really 
do, nor how your whole system really fits together.
In addition, this list is for the support of Tomcat, and your issue is not really with 
Tomcat, but seems to be really at the application level and how this application
a) performs user authentication
b) later uses the results of the user authentication
The fact that there is no documentation and that the relevant delevelopers have left is a 
pity, but not really something we can do anything about.

What I really suggest, if this application is important for you (and apart from what Chuck 
already mentioned) is this : get in touch with the Jespa authors, at www.ioplex.com (email 
: support@ioplex.com) , present the issue to them, and ask them how they could help.

Maybe first though : download the Jespa Operator's Guide from their website, and read it.
That will already tell you a lot of what you need to know.

Replacing the jCIFS HTTP filter by Jespa is not very hard, and mostly consists of 
installing Jespa and modifying the web.xml to use the Jespa filter instead of the jCIFS 
filter.  That would be the following sections of your current web.xml :

 > <filter>
 >         <filter-name>NtlmHttpFilter</filter-name>
 >         <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
 >
 >         <!--
 >             always needed for preauthentication / SMB signatures
 >         -->
 >         <init-param>
 >             <param-name>jcifs.smb.client.domain</param-name>
 >             <param-value>xxx</param-value>
 >         </init-param>
 >         <!-- SMB message signing requires a valid existing login -->
 >         <init-param>
 >             <param-name>jcifs.smb.client.username</param-name>
 >             <param-value>xxx</param-value>
 >         </init-param>
 >         <init-param>
 >             <param-name>jcifs.smb.client.password</param-name>
 >             <param-value>xxx</param-value>
 >         </init-param>
 >         <!-- Set the logging level -->
 >         <init-param>
 >             <param-name>jcifs.util.loglevel</param-name>
 >             <param-value>3</param-value>
 >         </init-param>
 >         <!--  allow non-IE browsers to use basic auth -->
 >         <init-param>
 >             <param-name>jcifs.http.insecureBasic</param-name>
 >             <param-value>true</param-value>
 >         </init-param>
 >     </filter>

and

 >     <filter-mapping>
 >         <filter-name>NtlmHttpFilter</filter-name>
 >         <url-pattern>/suggestions/*</url-pattern>
 >     </filter-mapping>

and

 >     <filter-mapping>
 >         <filter-name>NtlmHttpFilter</filter-name>
 >         <url-pattern>/xxx/*</url-pattern>
 >     </filter-mapping>

The sections above have a direct equivalent with Jespa, and there should in principle not 
be any code changes to make in your applications.
Just the parameters in web.xml differ somewhat.

Both the jCIFS filter and the Jespa filter are servlet filters, and they basically do the 
same thing :
- authenticate the current user of the application with the Windows Domain Controllers 
(and whatever is used as their back-end authentication mechanism)
- "set" the internal "Tomcat user" to this user-id

Then, after that, runs the other filters that are configured above, and your application.
What they do with whatever information the authentication filter (jCIFS or Jespa) has 
passed to Tomcat, we do not know, and there could be a problem there (but more likely not).
If there was a problem, then the people most likely to be able to help you are the Jespa guys.


In theory, there could be another way : replace this "application-level" filter-based 
authentication by a container-level authentication (and get rid of the filters), but in 
your current situation, I believe that the Jespa solution is really the simplest one.

And, really, consider upgrading your Tomcat version.  Nothing which you are currently 
using is supported anymore.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

Posted by Martin Gainty <mg...@hotmail.com>.
nslookup DomainName

if you still call no joy there is nothing we can do (without contacting your Domain Admin and asking if DomainName is live)

Martin 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.

 
> From: seema165@hotmail.com
> To: users@tomcat.apache.org
> Subject: RE: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx
> Date: Thu, 1 Aug 2013 12:02:34 +0100
> 
> 
> 
> > Date: Thu, 1 Aug 2013 12:06:39 +0200
> > From: aw@ice-sa.com
> > To: users@tomcat.apache.org
> > Subject: Re: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx
> > 
> > Seema Patel wrote:
> > > Hi,
> > >  
> > > I am not sure if this is the right List to post this on, please advise if it isn't and let me know where is best to post.
> > >  
> > > I am getting the following error on one of our applications running on our intranet:
> > >  
> > > 2013-07-31 17:15:11,180 [http-xxx.xxx.x.xxx-xx-x] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/forms].[action] - Servlet.service() for servlet action threw exception
> > > java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx.LOCAL
> > > at jcifs.smb.SmbSession.getChallengeForDomain(SmbSession.java:187)
> > > at jcifs.http.NtlmHttpFilter.negotiate(NtlmHttpFilter.java:150)
> > > at jcifs.http.NtlmHttpFilter.doFilter(NtlmHttpFilter.java:114)
> > > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
> > > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> > > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> > > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
> > > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:465)
> > > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> > > at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
> > > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> > > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
> > > at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:837)
> > > at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:640)
> > > at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1287)
> > > at java.lang.Thread.run(Unknown Source)
> > >  
> > 
> > I believe that you should read this page carefully, in particular the blue text at the 
> > beginning : http://jcifs.samba.org/src/docs/ntlmhttpauth.html
> > 
> > Can you have a look at the WEB-INF/web.xml file *of your application*, and check if there 
> > is a servlet filter configured there, which matches the name above ?
> > 
> > If so, make a backup copy of that web.xml file, and then edit it to remove that filter 
> > from it, and try again.
> > I am not quite sure, but it looks possible to me that you have a duplicate authentication 
> > mechanism in use : one at the container (Tomcat) level, and one at the application level.
> > And the one used at the application level is obsolete, unsupported, unmaintained etc..
> > 
> 
> I have found out that JCIFS is no longer supported, but it will take a lot of time, development and resources to update it to the recommended Jespa.  In my web.xml file I have the following:
> 
> <filter>
>         <filter-name>NtlmHttpFilter</filter-name>
>         <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
>            
>         <!--
>             always needed for preauthentication / SMB signatures
>         -->
>         <init-param>
>             <param-name>jcifs.smb.client.domain</param-name>
>             <param-value>xxx</param-value>
>         </init-param>
>         <!-- SMB message signing requires a valid existing login -->
>         <init-param>
>             <param-name>jcifs.smb.client.username</param-name>
>             <param-value>xxx</param-value>
>         </init-param>
>         <init-param>
>             <param-name>jcifs.smb.client.password</param-name>
>             <param-value>xxx</param-value>
>         </init-param>
>         <!-- Set the logging level -->
>         <init-param>
>             <param-name>jcifs.util.loglevel</param-name>
>             <param-value>3</param-value>
>         </init-param>
>         <!--  allow non-IE browsers to use basic auth -->
>         <init-param>
>             <param-name>jcifs.http.insecureBasic</param-name>
>             <param-value>true</param-value>
>         </init-param>
>     </filter>
>     <filter>
>         <filter-name>HRADGroupFilter</filter-name>
>         <filter-class>xxx.ADGroupFilter</filter-class>
>         <init-param>
>             <param-name>AllowedGroups</param-name>
>             <param-value>G-HR,G-MIS</param-value>
>         </init-param>
>     </filter>
>         <filter>
>         <filter-name>SuggestionsGroupFilter</filter-name>
>         <filter-class>xxx.ADGroupFilter</filter-class>
>         <init-param>
>             <param-name>AllowedGroups</param-name>
>             <param-value>xxx, xxx</param-value>
>         </init-param>
>     </filter>
>     
>     <filter-mapping>
>         <filter-name>NtlmHttpFilter</filter-name>
>         <url-pattern>/suggestions/*</url-pattern>
>     </filter-mapping>
>     <filter-mapping>
>         <filter-name>SuggestionsGroupFilter</filter-name>
>         <url-pattern>/suggestions/*</url-pattern>
>     </filter-mapping>
>     <filter-mapping>
>         <filter-name>NtlmHttpFilter</filter-name>
>         <url-pattern>/xxx/*</url-pattern>
>     </filter-mapping>
>     <filter-mapping>
>         <filter-name>HRADGroupFilter</filter-name>
>         <url-pattern>/xxx/xxx.do</url-pattern>
>     </filter-mapping>
> 
> 
> So, are you saying to just remove the following from the above?:
>        <filter-name>NtlmHttpFilter</filter-name>
>        <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
> 
> Is there anything else in there that needs to be removed?  Sorry for my lack of understanding, but this was all developed by previous developers, who are no longer working here and have left no documentation.
> 
> Thanks
> 
> > 
> > > In my tomcat/conf/server.xml file I have:
> > >  
> > > <Realm className="com.viatel.tomcatrealms.ADJNDIRealm"
> > > debug="01" resourceName="ActiveDirectory"
> > > connectionURL="ldap://xxx:xxx"
> > > alternativeURL="ldap://xxx:xxx"
> > > connectionName="LDAP@xxx.local" connectionPassword="xxx"
> > > referrals="follow" userBase="dc=vtlwavenet,dc=local"
> > > userSearch="(sAMAccountName={0})" userSubtree="true"
> > > roleBase="dc=xxx,dc=local" roleSearch="(member={0})"
> > > roleName="cn" roleSubtree="true" />
> > >  
> > > I have 2 .war files running from this tomcat - 1) intranet portal A, 2) intranet helpdesk page and also another intranet portal B (both run from slightly different URLs).
> > > When tomcat was restarted the intranet portal A runs, intranet portal B runs but the intranet helpdesk portal doesn't run.  For this we get the error message shown above.
> > >  
> > > I don't know if it is the java code, some setting in the tomcat catalina base or if it is a tomcat network issue.
> > >  
> > > We are running Tomcat 5.5.29.
> > > java version "1.5.0_22"
> > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
> > > Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode, sharing) 
> > > It is on a Windows Server 2003 R2 SP2 VM box.
> > >  
> > > Any help on this is appreciated.
> > > Thanks in advance
> > >  
> > > Seema
> > >  
> > >  
> > >  
> > >  		 	   		  
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> > 
>  		 	   		  
 		 	   		  

RE: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

Posted by Seema Patel <se...@hotmail.com>.

> Date: Thu, 1 Aug 2013 12:06:39 +0200
> From: aw@ice-sa.com
> To: users@tomcat.apache.org
> Subject: Re: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx
> 
> Seema Patel wrote:
> > Hi,
> >  
> > I am not sure if this is the right List to post this on, please advise if it isn't and let me know where is best to post.
> >  
> > I am getting the following error on one of our applications running on our intranet:
> >  
> > 2013-07-31 17:15:11,180 [http-xxx.xxx.x.xxx-xx-x] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/forms].[action] - Servlet.service() for servlet action threw exception
> > java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx.LOCAL
> > at jcifs.smb.SmbSession.getChallengeForDomain(SmbSession.java:187)
> > at jcifs.http.NtlmHttpFilter.negotiate(NtlmHttpFilter.java:150)
> > at jcifs.http.NtlmHttpFilter.doFilter(NtlmHttpFilter.java:114)
> > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
> > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
> > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:465)
> > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> > at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
> > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
> > at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:837)
> > at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:640)
> > at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1287)
> > at java.lang.Thread.run(Unknown Source)
> >  
> 
> I believe that you should read this page carefully, in particular the blue text at the 
> beginning : http://jcifs.samba.org/src/docs/ntlmhttpauth.html
> 
> Can you have a look at the WEB-INF/web.xml file *of your application*, and check if there 
> is a servlet filter configured there, which matches the name above ?
> 
> If so, make a backup copy of that web.xml file, and then edit it to remove that filter 
> from it, and try again.
> I am not quite sure, but it looks possible to me that you have a duplicate authentication 
> mechanism in use : one at the container (Tomcat) level, and one at the application level.
> And the one used at the application level is obsolete, unsupported, unmaintained etc..
> 

I have found out that JCIFS is no longer supported, but it will take a lot of time, development and resources to update it to the recommended Jespa.  In my web.xml file I have the following:

<filter>
        <filter-name>NtlmHttpFilter</filter-name>
        <filter-class>jcifs.http.NtlmHttpFilter</filter-class>
           
        <!--
            always needed for preauthentication / SMB signatures
        -->
        <init-param>
            <param-name>jcifs.smb.client.domain</param-name>
            <param-value>xxx</param-value>
        </init-param>
        <!-- SMB message signing requires a valid existing login -->
        <init-param>
            <param-name>jcifs.smb.client.username</param-name>
            <param-value>xxx</param-value>
        </init-param>
        <init-param>
            <param-name>jcifs.smb.client.password</param-name>
            <param-value>xxx</param-value>
        </init-param>
        <!-- Set the logging level -->
        <init-param>
            <param-name>jcifs.util.loglevel</param-name>
            <param-value>3</param-value>
        </init-param>
        <!--  allow non-IE browsers to use basic auth -->
        <init-param>
            <param-name>jcifs.http.insecureBasic</param-name>
            <param-value>true</param-value>
        </init-param>
    </filter>
    <filter>
        <filter-name>HRADGroupFilter</filter-name>
        <filter-class>xxx.ADGroupFilter</filter-class>
        <init-param>
            <param-name>AllowedGroups</param-name>
            <param-value>G-HR,G-MIS</param-value>
        </init-param>
    </filter>
        <filter>
        <filter-name>SuggestionsGroupFilter</filter-name>
        <filter-class>xxx.ADGroupFilter</filter-class>
        <init-param>
            <param-name>AllowedGroups</param-name>
            <param-value>xxx, xxx</param-value>
        </init-param>
    </filter>
    
    <filter-mapping>
        <filter-name>NtlmHttpFilter</filter-name>
        <url-pattern>/suggestions/*</url-pattern>
    </filter-mapping>
    <filter-mapping>
        <filter-name>SuggestionsGroupFilter</filter-name>
        <url-pattern>/suggestions/*</url-pattern>
    </filter-mapping>
    <filter-mapping>
        <filter-name>NtlmHttpFilter</filter-name>
        <url-pattern>/xxx/*</url-pattern>
    </filter-mapping>
    <filter-mapping>
        <filter-name>HRADGroupFilter</filter-name>
        <url-pattern>/xxx/xxx.do</url-pattern>
    </filter-mapping>


So, are you saying to just remove the following from the above?:
       <filter-name>NtlmHttpFilter</filter-name>
       <filter-class>jcifs.http.NtlmHttpFilter</filter-class>

Is there anything else in there that needs to be removed?  Sorry for my lack of understanding, but this was all developed by previous developers, who are no longer working here and have left no documentation.

Thanks

> 
> > In my tomcat/conf/server.xml file I have:
> >  
> > <Realm className="com.viatel.tomcatrealms.ADJNDIRealm"
> > debug="01" resourceName="ActiveDirectory"
> > connectionURL="ldap://xxx:xxx"
> > alternativeURL="ldap://xxx:xxx"
> > connectionName="LDAP@xxx.local" connectionPassword="xxx"
> > referrals="follow" userBase="dc=vtlwavenet,dc=local"
> > userSearch="(sAMAccountName={0})" userSubtree="true"
> > roleBase="dc=xxx,dc=local" roleSearch="(member={0})"
> > roleName="cn" roleSubtree="true" />
> >  
> > I have 2 .war files running from this tomcat - 1) intranet portal A, 2) intranet helpdesk page and also another intranet portal B (both run from slightly different URLs).
> > When tomcat was restarted the intranet portal A runs, intranet portal B runs but the intranet helpdesk portal doesn't run.  For this we get the error message shown above.
> >  
> > I don't know if it is the java code, some setting in the tomcat catalina base or if it is a tomcat network issue.
> >  
> > We are running Tomcat 5.5.29.
> > java version "1.5.0_22"
> > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
> > Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode, sharing) 
> > It is on a Windows Server 2003 R2 SP2 VM box.
> >  
> > Any help on this is appreciated.
> > Thanks in advance
> >  
> > Seema
> >  
> >  
> >  
> >  		 	   		  
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
 		 	   		  

Re: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

Posted by André Warnier <aw...@ice-sa.com>.
Seema Patel wrote:
> Hi,
>  
> I am not sure if this is the right List to post this on, please advise if it isn't and let me know where is best to post.
>  
> I am getting the following error on one of our applications running on our intranet:
>  
> 2013-07-31 17:15:11,180 [http-xxx.xxx.x.xxx-xx-x] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/forms].[action] - Servlet.service() for servlet action threw exception
> java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx.LOCAL
> at jcifs.smb.SmbSession.getChallengeForDomain(SmbSession.java:187)
> at jcifs.http.NtlmHttpFilter.negotiate(NtlmHttpFilter.java:150)
> at jcifs.http.NtlmHttpFilter.doFilter(NtlmHttpFilter.java:114)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:465)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
> at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
> at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:837)
> at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:640)
> at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1287)
> at java.lang.Thread.run(Unknown Source)
>  

I believe that you should read this page carefully, in particular the blue text at the 
beginning : http://jcifs.samba.org/src/docs/ntlmhttpauth.html

Can you have a look at the WEB-INF/web.xml file *of your application*, and check if there 
is a servlet filter configured there, which matches the name above ?

If so, make a backup copy of that web.xml file, and then edit it to remove that filter 
from it, and try again.
I am not quite sure, but it looks possible to me that you have a duplicate authentication 
mechanism in use : one at the container (Tomcat) level, and one at the application level.
And the one used at the application level is obsolete, unsupported, unmaintained etc..


> In my tomcat/conf/server.xml file I have:
>  
> <Realm className="com.viatel.tomcatrealms.ADJNDIRealm"
> debug="01" resourceName="ActiveDirectory"
> connectionURL="ldap://xxx:xxx"
> alternativeURL="ldap://xxx:xxx"
> connectionName="LDAP@xxx.local" connectionPassword="xxx"
> referrals="follow" userBase="dc=vtlwavenet,dc=local"
> userSearch="(sAMAccountName={0})" userSubtree="true"
> roleBase="dc=xxx,dc=local" roleSearch="(member={0})"
> roleName="cn" roleSubtree="true" />
>  
> I have 2 .war files running from this tomcat - 1) intranet portal A, 2) intranet helpdesk page and also another intranet portal B (both run from slightly different URLs).
> When tomcat was restarted the intranet portal A runs, intranet portal B runs but the intranet helpdesk portal doesn't run.  For this we get the error message shown above.
>  
> I don't know if it is the java code, some setting in the tomcat catalina base or if it is a tomcat network issue.
>  
> We are running Tomcat 5.5.29.
> java version "1.5.0_22"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode, sharing) 
> It is on a Windows Server 2003 R2 SP2 VM box.
>  
> Any help on this is appreciated.
> Thanks in advance
>  
> Seema
>  
>  
>  
>  		 	   		  


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Chuck,

On 8/1/13 7:50 AM, Caldarale, Charles R wrote:
>> From: Seema Patel [mailto:seema165@hotmail.com] Subject:
>> java.net.UnknownHostException: Failed to negotiate with a
>> suitable domain controller for xxx
> 
>> I am not sure if this is the right List to post this on
> 
> This is the correct list, but...
> 
>> jcifs.http.NtlmHttpFilter
> 
> Not supported: http://jcifs.samba.org/src/docs/ntlmhttpauth.html
> 
>> We are running Tomcat 5.5.29.
> 
> Not supported.
> 
>> java version "1.5.0_22"
> 
> Not supported.
> 
> You really, really need to upgrade your environment.  Using
> unsupported versions of the JVM and Tomcat leaves you open to
> numerous attacks and other bugs that will never be addressed in
> those versions.

+1

For what it's worth, upgrading the JVM is usually painless (with a few
exceptions, but it's easy to try!).

Since you were already on Tomcat 5.5, the transition from 5.5 -> 7.0
(latest) is pretty much a drop-in replacement (you'll need to re-write
your server.xml from scratch, but it shouldn't be a big deal to
re-configure your <Connector>s).

http://tomcat.apache.org/migration-6.html
http://tomcat.apache.org/migration-7.html

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJR+mFbAAoJEBzwKT+lPKRYyZ4QAMpa71PhxVktGiTwX0W49H2D
Irbt9EQ88BYjwawl0vgpcrt48ofMBOwErhsyFyYhk/zaaKRQOkP9Yf+lhq2sHkOQ
FNMzF52ZyYPcaPhlN7DsGMbEZtYqq07SkTPXYQ9bY7+CAbWUF/4CZ4vG3q0q7MiY
h48SIUs4EKF0UBmDFBcLdJj0xo+Lbnd6mx4WmasjJTDuniZsK6qZtxnn66UQBw2P
7n8hLCOBXvsjol9m5z/bJt1SifjQVNSfyoxlL7A7Pf1QP9zh1bAYen9efPKoa2Za
TM0KGYa9Vb8hNRGPGZH7/Rs0ZfIdpFrPqJtWTVeZBbt7EtABZbvDW3bsh5WYgzv1
G0pyJQl8tnVpem9QvniX4POHEuboSfco53k3SBe8dp6M+798zLAr4DcamRsvxR0d
2nJxLkl3XZiF3IaxyfeIjIz00gqU3AXj4T+yOtMb2g6ok3eRJlaTqraHyeMSPFQ0
IEzcHEUwuYlRfm4+IBqwlQUjRpKTkkM7rjqGQIQz1BqCrZ4amcjM7QlW9/3wj+p+
I803eFy+XfNJ5EwE2t/s1H+zzMM7uzsvR4dMkak4IMcV8r1TRYF+8ddR6AKYNuzX
pKwuFEXRaDycPkxaWoh9OO2UZ5OXk6VPU9QCuEcaLgDLjH3UHpAAFvM27dkmi/5P
tlQKaspmVeRFL8u+i8a3
=udXh
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Seema Patel [mailto:seema165@hotmail.com] 
> Subject: java.net.UnknownHostException: Failed to negotiate with a suitable domain controller for xxx

> I am not sure if this is the right List to post this on

This is the correct list, but...

> jcifs.http.NtlmHttpFilter

Not supported: http://jcifs.samba.org/src/docs/ntlmhttpauth.html

> We are running Tomcat 5.5.29.

Not supported.

> java version "1.5.0_22"

Not supported.

You really, really need to upgrade your environment.  Using unsupported versions of the JVM and Tomcat leaves you open to numerous attacks and other bugs that will never be addressed in those versions.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org