NT Authentication/Integrated security

[Nordlund]

Hi there.
I'm trying to connect to an MSSQL server usinng NT Authentication. I've manage to log on after reading this tip:

Leave user name and password blank in your application's
TDatabase and make sure that the USER NAME in the BDE
ALIAS and MSSQL driver settings is blank (used as a default
when an ALIAS parameter is blank).

http://bdn.borland.com/article/0,1410,19731,00.html

The only problem i'm dealing with right now, is that I have to use Named pipes to get it to work. I don't want to use Named pipes. I want to use TCP/IP...

Any ideas? Please share them...

Thanks.


//Nordlund

 

[VintageWine]

Hi Nordlund,

This is my understanding of the situation:

If you are going to use NT authentication, it is implicit that the user is logged into the NT Domain. In which case what not use Named Pipes and be done with it.

Conversely if you are using tcp/ip because the user is not logged into the domain, you can't take advantage of the NT Authentication anyway.

If it's not too late for your project, how about changing from the BDE to ADO.

Good luck
Simon

 

[Nordlund]

Thanks Simon.
Unfortunately, I have to use TCP/IP... And BDE.....

It's not possible to change from named pipes at all, and it's much too complex to change from BDE to ADO......





//Nordlund