Strange problem connecting to SQL Server with windows authentifica

fermat

unread,

Mar 2, 2010, 4:11:01 PM3/2/10

to

Hi there,

I'm struggling for hours with a very strange problem trying to connect from
Microsoft Dynamics Nav to SQL Server using Windows authentification.
The scenario: I have a Windows XP client at which a domain user is logged
in. (Login: TESTDOMAIN\TESTUSER)

This domain user tries to connect with the Dynamics Nav Client to its SQL
Server database using windows authentification. The SQL server resides at a
W3K server (not the domain controller) named TESTSERVER. At the server there
is also a local account named TESTUSER.

The connect fails saying "invalid user name or password". Using the profiler
reveals the reason for this. Despite the fact that the user that ist logged
in at the client is TESTDOMAIN\TESTUSER the SQL server Login is
TESTSERVER\TESTUSER, to which no access has been granted. For some reason the
authetification seems to has changed.

BTW. Logging in at the TESTSERVER as domain user TESTDOMAIN\TESTUSER works
correctly and connection from Dynamics NAv client to the database ist
established.

Does anyone has an explanation for this?

Thanks....

Michael

Erland Sommarskog

unread,

Mar 3, 2010, 2:54:03 AM3/3/10

to

If you are wanting to use Windows Authentication, but the client in fact
is using SQL Server authentication, it is really pulling your legs. I can't
give any explanation for this, but then again I know nothing about
Dynamics NAV, and I suspect knowledge about this product is needed to
solve this puzzle.

--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Lutz Uhlmann

unread,

Mar 3, 2010, 3:42:00 AM3/3/10

to

Am 02.03.2010 22:11, schrieb fermat:
> Hi there,
>
> I'm struggling for hours with a very strange problem trying to connect from
> Microsoft Dynamics Nav to SQL Server using Windows authentification.
> The scenario: I have a Windows XP client at which a domain user is logged
> in. (Login: TESTDOMAIN\TESTUSER)
>
> This domain user tries to connect with the Dynamics Nav Client to its SQL
> Server database using windows authentification. The SQL server resides at a
> W3K server (not the domain controller) named TESTSERVER. At the server there
> is also a local account named TESTUSER.
>
> The connect fails saying "invalid user name or password". Using the profiler
> reveals the reason for this. Despite the fact that the user that ist logged
> in at the client is TESTDOMAIN\TESTUSER the SQL server Login is
> TESTSERVER\TESTUSER, to which no access has been granted. For some reason the
> authetification seems to has changed.

Are you sure that TESTSERVER a member of the TESTDOMAIN?

fermat

unread,

Mar 3, 2010, 2:36:01 PM3/3/10

to

Lutz,

yes... TESTSERVER is definetly a member of TESTDOMAIN. In fact, if I login
as TESTDOMAIN\TESTUSER at the server TESTSERVER everything works fine, but
the same at the client results in the described problem. At the client the
Windows login is TESTDOMAIN\TESTUSER the SQL Profiler at the server
TESTSERVER, where the SQL Server is located, says that the login - when
trying to connect - is for some reason NOT TESTDOMAIN\TESTUSER but
TESTSERVER\TESTUSER.

I have no idea, why this can happen. A kind of impersonation? But I have not
configured anything in this matter...

Michael

"Lutz Uhlmann" wrote:

> .
>