[jcifs] Fail-over capability with WINS

WYND Consulting wyndconsulting at shaw.ca
Fri Dec 1 06:32:51 GMT 2006


Mike,

I appreciate you getting back to me. The problem is that as Windows is evolving WINS is rarely installed  and is heavily reliant on DNS now. Mainly putting feelers out to see if anyone has addressed this through the code. If not, may have a crack at it.

Stephen

----- Original Message -----
From: Michael B Allen <mba2000 at ioplex.com>
Date: Thursday, November 30, 2006 7:33 pm
Subject: Re: [jcifs] Fail-over capability with WINS

> Failover requires WINS. The code could be modified to do better but
> currently it just doesn't. The only way to use the Filter without WINS
> is to use jcifs.http.domainController. Note that by default an AD 
> serveris usually also a WINS server.
> 
> Mike
> 
> On Thu, 30 Nov 2006 14:26:32 -0800
> WYND Consulting <wyndconsulting at shaw.ca> wrote:
> 
> > I have reviewed a large number of posts and noticed several about 
> the desire to use NTLM Filter without WINS but no suggestions were 
> given. I'm trying to get more information whether anyone has had 
> any luck or suggestions on how to get this to work. 
> > 
> > I had a thought of allowing an alternate Domain Controller entry 
> in the web.xml file and when the library is run it validates that a 
> primary server on port 445 is available and if not then uses the 
> alternate server by swapping over the values in the code.
> > 
> > Example:
> > 
> > 1) Gets the properties for both domainController and 
> altDomainController.> 2) Prior to attempting any of the NTLM 
> handshake it checks port status.
> > 3) If primary is available then use the primary if not then 
> substitute the alternate server in as the domainController value.
> > 
> > Any thoughts would be much appreciated.
> > 
> > Thanks
> > 
> > Stephen 
> > 
> 
> 
> -- 
> Michael B Allen
> PHP Active Directory SSO
> http://www.ioplex.com/
> 


More information about the jcifs mailing list