Prev   Next

Back to the top of the FAQ

Q. ODBC and Windows 2003

A. You will be pleased to note that Windows 2003's is locked down much more than Window 2000.
You won't be so pleased to learn that this can make it harder to create DSN strings, and harder to successfully connect to the database.

One user found that everything was working on Windows 2000 but when moved to W2K3 the AuthentiX filter was not able to gain access to the database, with the following message in the Event Log:

General Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. - 28000

In the second dialog for setting up System DSN, he was using Network Logon for Trusted Connection. Changing this to using SQL Server Mixed Authentication (SQL2000) with a matching account in SQL Security, solved the issue.

Adding the NT Authority\network service (s-1-5-20) user to the admin group may help.

Also, see here.

Back to the top of the FAQ

Prev   Next