mssql 2K connection

eomer

Hi all,

I have a connection problem between php & mssql 2K.
The server & DB uses windows authentification security... and I have no idea on how to connect to the database.

Is there a solution, or does a fixed user have to be created?

Thank's in advance,

Nicolas

hessian

The server must be configured for TCP/IP which will open 1433, is that open? I think by default it is named pipes only, but I really don't play with MsSQL all that often. If 1433 isn't open, go and open it, start -> Programs -> MSsql -> SQL Server Network Utility.

As far as authentication, you may just want to try the sa account with no passwd. Most SQL Servers i have seen havent had a password because that is how it is by default.
<?
if(mssql_connect("SQL_SERVER_IP","sa",""))
echo "connected";
else
echo "Counldnt connect";
?>

If not can you not create accounts? You can have sql server and windows authenication at the same time.

Just a side note, if you are connecting for a website, to be Legal, you have to buy a internect connector lic from microsoft, i think it is $3800 dollars per processor in the SQL Server.

eomer

Hi,

Thank's for your response...

I think I could ask for a fixed user to be created in order to connect, but I was just wondering if it was possible to use the windows authentification with php... but it is quite difficult to find informations about this type of connection.

For the license fees, we are quite fully equiped 😉

Regard's,

Nicolas

Doug_G

Windows authentication to sql server means the login to the database server is based on the windows user, so if your web server isn't a windows IIS server you probably won't be able to use windows authentication to the db.

If your web server is IIS it's possible. IIS usually operates in the IUSR_computername user account, which is usually a local account for the web server. If the DB is on another computer, you need to clone this user account.

If your website forces user authentication to windows, after a browser user logs in IIS will then impersonate the logged in user and this user must also exist on the DB server.

Using SQL server user/passwords is usually easier from a web server.

eomer

Well, I suppose I could run the site on a IIS server, but it is actually an apache server... I think I'm gonna ask for a "fixed" user on that database.... ;o)

Thank's for the infos,

Nicolas