Re: I can only connect via Windows Auth - WHY?
From: SA Dev (nospam38925_at_forme.com)
Date: 09/29/04
- Next message: Gert E.R. Drapers: "Re: SQL Server 2000 on Win 2003 and DTC"
- Previous message: Kevin McDonnell [MSFT]: "RE: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
- In reply to: Kevin McDonnell [MSFT]: "Re: I can only connect via Windows Auth - WHY?"
- Next in thread: Kevin McDonnell [MSFT]: "Re: I can only connect via Windows Auth - WHY?"
- Reply: Kevin McDonnell [MSFT]: "Re: I can only connect via Windows Auth - WHY?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 29 Sep 2004 12:56:26 -0500
Hi Kevin,
> Change your connection to use TCP .
> Try this test with OSQL.
In the SQL Server properties BOTH Named Pipes and TCPIP are listed until the
network settings. I have the security set to MIXED.
Here is what I get:
D:\Temp\5>OSQL -Stcp:192.168.101.11 -Usa
Password:
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
Is there any other settings I should check?
Thanks for the help,
SA Dev
- Next message: Gert E.R. Drapers: "Re: SQL Server 2000 on Win 2003 and DTC"
- Previous message: Kevin McDonnell [MSFT]: "RE: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection."
- In reply to: Kevin McDonnell [MSFT]: "Re: I can only connect via Windows Auth - WHY?"
- Next in thread: Kevin McDonnell [MSFT]: "Re: I can only connect via Windows Auth - WHY?"
- Reply: Kevin McDonnell [MSFT]: "Re: I can only connect via Windows Auth - WHY?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]