If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Microsoft SQL Server > Intermittent - Login failed for user '(null)'

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 02-14-02, 15:13
jlemonds jlemonds is offline
Registered User
 
Join Date: Feb 2002
Posts: 1
Question Intermittent - Login failed for user '(null)'

When trying to connect to a SQL 2K box running on Win2K adv server sometimes/some users report difficulty connecting. If they change from Windows authentication upon connecting to the server and instead use SQL authentication they can successfully connect.
We have other SQL servers on the same subnet that does not have this problem at all.

Env: Win2K Adv server SP2
SQL 2K Ent SP2


The message is as follows:
Unable to connect to server XYZ:
Server: Msg 18452, Level 16, State 1
[Micorsoft][ODBC SQL Server Driver][SQL Server]Login filed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.


Again: Windows Authentication - intermittently fails
SQL Authentication always works.

Note: Users exist in different domain than the machines, but this does not seem to effect the test or dev servers (naturally, only production have we seen this problem).

Any help is greatly appreciated.

thanks,
John
Reply With Quote
  #2 (permalink)  
Old 05-18-04, 09:52
jacksoea jacksoea is offline
Registered User
 
Join Date: Jan 2004
Posts: 3
Login filed for user '(null)'. Reason: Not associated with a trusted SQL Server

Correct me if I am wrong,

Your Env 2K, using SQL2K, SQL SP3; you are getting a SQL Connection error trying to authenicate WindowsNT Accounts in SQL Server.

Error: Server connection.
18452: Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.

In a DB forum I read because I had the same issue, Vikrant Dalwale laid out some things to check:

Potential causes,

1. Is the SQL Server listening on the correct protocol with which the
Central Server is trying to connect?

verify actual protocol with
"HKLM\Software\Microsoft\MSSQLServer\Client\Connec tTo" rather
than relying on clicnfg.exe (Client Network Utility)

2. Is the Central server and SQL Server 7.0 /2K on different domain ? If yes,
are they trusted ?

3. Is SQL 7.0 / 2K configured for Mixed mode security ?

4. Can you register SQL 7.0 / 2K using the IP Address ?

5. Whats is the startup account used for SQL Server 7.0/ 2K Service ? Make sure
that
this account has following rights,

- act as part of OS
- logon as a service
- increase quotas
- replace a process level token

6. Make sure that the account which which you are trying to register the
SQL 7.0/ 2K , has "access this computer from the network" user right on the
SQL Server 7.0/ 2K Machine.

I would like to add (EAJ)

7. make sure your DNS Suffix for a connection is defined. You can find that in the Advance TCP/IP Settings. Also, make sure a check mark is placed in "register this connection" and "Use this connection" and that is located under the DNS Suffix in Advance TCP/IP Settings

8. Under the System Properties, computer name; make sure the Primary DNS Suffix for that computer is defined and also, do not forget to put a check in "change primary DNS suffix when domain membership changes"

I hope this additional info help, it did for me.

Reply back to let me know your status, I am interested

EAJ
__________________
EA Jackson
DBM / Sys Eng.

Last edited by jacksoea; 05-18-04 at 10:00. Reason: to add
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On