FreeTDS Development Group

["Varley, David (CBorn at Alcoa)" <David.Varley AT alcoa.com.au>]

That's interesting. When some of our client databases were updated from
MSSQL7 to MSSQL2K recently, our access via Enterprise Manager failed with
the message about "user null". Our complaints took a while to filter up to
an expert in Microsoft Support, and the answer came back to use only Named
Pipes instead of tcp/ip.

We are connecting cross-domain, and the solution seems to be to map a
network drive to the NETLOGON share on the SQL server box using a valid NT
username/pw, and then connect using Named Pipes, which is much slower, but
authenticates.

>From what's been said in this thread, sounds like this may be a configurable
policy setting on their servers.

[I haven't tested against those servers with FreeTDS. Since the start of the
iconv changes a long time back I haven't been able to get a working build on
Tru64 :( ]

Cheers,

David

> -----Original Message-----
> From: B. Bell [mailto:bradleyb AT u.washington.edu] 
> Sent: Wednesday, 6 August 2003 5:20 AM
> To: FreeTDS Development Group
> Subject: RE: [freetds] Domain Login Support, connecting to MSSQL issue
> 
> 
> On Tue, 5 Aug 2003, B. Bell wrote:
> 
> > I use tcp/ip from the win2k workstations as well, so that 
> shouldn't be 
> > the problem.  I'm starting to suspect NTLM though.
> 
> I have CONFIRMED that it does NOT work if you have the 
> following machine
> policy:
>  Computer Configuration\Windows Settings\Security 
> Settings\Local  Policies\Security Options\LAN Manager 
> Authentication Level set to "Send NTLMv2 response only\refuse 
> LM & NTLM" I set it to "Send LM & NTLM responses" (the 
> default) and it works! I will try and narrow it down some 
> more to see if I can set it any higher. Would it be possible 
> for freetds to support NTLMv2 in the future?
> 
> -Brad
> 
> 
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org 
> http://lists.ibiblio.org/mailman/listinfo/free> tds
>