Login failed for user '(null)'. Active Directory issue?

From: bglass (bglass.y4umb_at_mail.mcse.ms)
Date: 12/08/03 

Date: Mon, 8 Dec 2003 11:12:42 -0600

Here is the situation...

I have numerous SQL Servers. All SQL2K w/SP2 and security patches.
All report the same version number. All are set to use mixed mode
security, although all our applications/users connect using NT
authentication. All our servers reside in the same domain as do the
users.

Our client machines are a mix of WIN2K and NT4. Our apps connect using
either ADO, OLEDB, or ODBC. The servers are setup to listen on TCP,
Shared Memory, and Named Pipes. Workstations are setup to communicate
on TCP and NP.

Our primary production database server is NT4. We are looking to
upgrade it to WIN2K. In order to do this, I must "failover" to the
backup system during the upgrade (our business is 24/7). The backup
system, being a mirror, is also NT4. When trying to failover this
weekend, we got the:

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

..error message from the apps while trying to connect to the backup
system. The exact same apps work fine against production or any of our
other systems. Meanwhile, I am able to connect to the backup server
from Query Analyzer and EM with no problems.

Other things to note...

* The error seems to only occur when connecting from Win2K
workstations. And some Win2K workstations also get the error under EM
and QA.

* We are in the middle of a transition from NT4 to Win2K domain
controllers. Could this be impacting our authentication?

* The backup server was recently a Win2K machine that was later
downgraded to NT4. Could that be causing an issue somewhere?

I believe this problem to actually be outside of SQL Server itself, but
it doesn't make it any less my problem nonetheless.

Thoughts?

bglass
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message157492.html

 

Relevant Pages

  • Re: W2K Authenticating to NT 4.0 Domain Not working....
    ... NT4 uses Netbios, while Win2K used DNS. ... is not able to resolve the NT4 names. ... I believe that you will have to implement a WINS server on ...
    (microsoft.public.win2000.security)
  • RE: cant log into the domain
    ... to successfully ping the backup win2k server, and I also could ping another ... > with a win2k server as backup should our main site burn down or be destroyed. ... > Today I took a machine off our production network and plugged it ...
    (microsoft.public.win2000.networking)
  • Re: NT Server - 98 WkStn Highschool Lab - Help!
    ... NT Server - 98 WkStn Highschool Lab - Help! ... Now they are at Win2k. ... you will have no luck using Windows 98. ...
    (Focus-Microsoft)
  • Re: SBS2003 + tombstoned WIN2K DC
    ... Last replication recieved from WIN2K at 2006-10-22 ... First you'll need to demote the 2nd DC (NOT the SBS server), ... computer shows up in the SBS server. ... I'm worried that if I remove the AD from WIN2K then everything will ...
    (microsoft.public.windows.server.sbs)
  • Re: e-mail
    ... Select the ones you want to allow, in your list imap server and pop3 ... For example lets say that your user name on your Suse is 'fred'. ... I will tell you all about procmail and fetchmail after lunch. ... on server rather than my win2k box which dual boots into opensuse10.2. ...
    (alt.os.linux.suse)