Login failed for user <null> 
Author Message
 Login failed for user <null>

I am having a mysterious problem. Occasionally SQL Server 7.0 gives the
following error when a System DSN is tested:

Connection Failed
SQL State: 42000
SQL Error No: 18452
[Microsoft][ODBC SQL Server Driver][SQl Server] Login Failed for user <null>
Reason: Not associated with a trusted SQL Server Connection

The problem goes away after some time (approx. 15-20 min). My database
server is A. I make a system DSN on computer B for a datasource on A. Then I
test this DSN and the above error message pops up.

Does anyone has an idea of what goes wrong and heals automatically?

Thanks
Nitin



Tue, 27 Apr 2004 01:11:44 GMT
 Login failed for user <null>

Nitin,

This error usually comes up when you are trying to connect to the data
source using WINDOWS NT Authentication within the DSN and the servers are
not in the same domain. In NT authentication your network login will be used
to connect to the source by passing DomainName\LoginName for verification.
You need to give access to this NT login to connect to the SQL Server box.
Refer to the BOL on how to grant access to NT logins. Are both servers in
the same domain? This error may come up if the servers are in different
domains when trying to connect using NT authentication.

HTH.
Prasad

Quote:
> I am having a mysterious problem. Occasionally SQL Server 7.0 gives the
> following error when a System DSN is tested:

> Connection Failed
> SQL State: 42000
> SQL Error No: 18452
> [Microsoft][ODBC SQL Server Driver][SQl Server] Login Failed for user
<null>
> Reason: Not associated with a trusted SQL Server Connection

> The problem goes away after some time (approx. 15-20 min). My database
> server is A. I make a system DSN on computer B for a datasource on A. Then
I
> test this DSN and the above error message pops up.

> Does anyone has an idea of what goes wrong and heals automatically?

> Thanks
> Nitin



Tue, 27 Apr 2004 01:31:27 GMT
 Login failed for user <null>
Hello Prasad

Both the database server and the computer on which I am creating a DSN are
on the same domain.

One important point is that it works fine most of the time and the error
pops up occasionally and disappears without my intervention.

Thanks


Quote:
> Nitin,

> This error usually comes up when you are trying to connect to the data
> source using WINDOWS NT Authentication within the DSN and the servers are
> not in the same domain. In NT authentication your network login will be
used
> to connect to the source by passing DomainName\LoginName for verification.
> You need to give access to this NT login to connect to the SQL Server box.
> Refer to the BOL on how to grant access to NT logins. Are both servers in
> the same domain? This error may come up if the servers are in different
> domains when trying to connect using NT authentication.

> HTH.
> Prasad


> > I am having a mysterious problem. Occasionally SQL Server 7.0 gives the
> > following error when a System DSN is tested:

> > Connection Failed
> > SQL State: 42000
> > SQL Error No: 18452
> > [Microsoft][ODBC SQL Server Driver][SQl Server] Login Failed for user
> <null>
> > Reason: Not associated with a trusted SQL Server Connection

> > The problem goes away after some time (approx. 15-20 min). My database
> > server is A. I make a system DSN on computer B for a datasource on A.
Then
> I
> > test this DSN and the above error message pops up.

> > Does anyone has an idea of what goes wrong and heals automatically?

> > Thanks
> > Nitin



Tue, 27 Apr 2004 01:53:04 GMT
 Login failed for user <null>
Hello Geoff

How do I check the reliability of the communications between the SQL Server
and the domain controller

Thanks

-nitin



Quote:
> Make sure communications are reliable between your SQL server and whatever
> domain controller it is authenticating and that there are no
communications
> issues amongst your domain controllers.

> --
> Geoff N. Hiten
> Senior Database Administrator
> Headhunter.net



> > Hello Prasad

> > Both the database server and the computer on which I am creating a DSN
are
> > on the same domain.

> > One important point is that it works fine most of the time and the error
> > pops up occasionally and disappears without my intervention.

> > Thanks



> > > Nitin,

> > > This error usually comes up when you are trying to connect to the data
> > > source using WINDOWS NT Authentication within the DSN and the servers
> are
> > > not in the same domain. In NT authentication your network login will
be
> > used
> > > to connect to the source by passing DomainName\LoginName for
> verification.
> > > You need to give access to this NT login to connect to the SQL Server
> box.
> > > Refer to the BOL on how to grant access to NT logins. Are both servers
> in
> > > the same domain? This error may come up if the servers are in
different
> > > domains when trying to connect using NT authentication.

> > > HTH.
> > > Prasad


> > > > I am having a mysterious problem. Occasionally SQL Server 7.0 gives
> the
> > > > following error when a System DSN is tested:

> > > > Connection Failed
> > > > SQL State: 42000
> > > > SQL Error No: 18452
> > > > [Microsoft][ODBC SQL Server Driver][SQl Server] Login Failed for
user
> > > <null>
> > > > Reason: Not associated with a trusted SQL Server Connection

> > > > The problem goes away after some time (approx. 15-20 min). My
database
> > > > server is A. I make a system DSN on computer B for a datasource on
A.
> > Then
> > > I
> > > > test this DSN and the above error message pops up.

> > > > Does anyone has an idea of what goes wrong and heals automatically?

> > > > Thanks
> > > > Nitin



Tue, 27 Apr 2004 03:17:14 GMT
 Login failed for user <null>
Thanks Geoff

-Nitin



Quote:
> Ping, then try and map a drive.  That will test both basic communication
and
> authentication.

> --
> Geoff N. Hiten
> Senior Database Administrator
> Headhunter.net



> > Hello Geoff

> > How do I check the reliability of the communications between the SQL
> Server
> > and the domain controller

> > Thanks

> > -nitin



> > > Make sure communications are reliable between your SQL server and
> whatever
> > > domain controller it is authenticating and that there are no
> > communications
> > > issues amongst your domain controllers.

> > > --
> > > Geoff N. Hiten
> > > Senior Database Administrator
> > > Headhunter.net



> > > > Hello Prasad

> > > > Both the database server and the computer on which I am creating a
DSN
> > are
> > > > on the same domain.

> > > > One important point is that it works fine most of the time and the
> error
> > > > pops up occasionally and disappears without my intervention.

> > > > Thanks



> > > > > Nitin,

> > > > > This error usually comes up when you are trying to connect to the
> data
> > > > > source using WINDOWS NT Authentication within the DSN and the
> servers
> > > are
> > > > > not in the same domain. In NT authentication your network login
will
> > be
> > > > used
> > > > > to connect to the source by passing DomainName\LoginName for
> > > verification.
> > > > > You need to give access to this NT login to connect to the SQL
> Server
> > > box.
> > > > > Refer to the BOL on how to grant access to NT logins. Are both
> servers
> > > in
> > > > > the same domain? This error may come up if the servers are in
> > different
> > > > > domains when trying to connect using NT authentication.

> > > > > HTH.
> > > > > Prasad


> > > > > > I am having a mysterious problem. Occasionally SQL Server 7.0
> gives
> > > the
> > > > > > following error when a System DSN is tested:

> > > > > > Connection Failed
> > > > > > SQL State: 42000
> > > > > > SQL Error No: 18452
> > > > > > [Microsoft][ODBC SQL Server Driver][SQl Server] Login Failed for
> > user
> > > > > <null>
> > > > > > Reason: Not associated with a trusted SQL Server Connection

> > > > > > The problem goes away after some time (approx. 15-20 min). My
> > database
> > > > > > server is A. I make a system DSN on computer B for a datasource
on
> > A.
> > > > Then
> > > > > I
> > > > > > test this DSN and the above error message pops up.

> > > > > > Does anyone has an idea of what goes wrong and heals
> automatically?

> > > > > > Thanks
> > > > > > Nitin



Tue, 27 Apr 2004 13:52:47 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. Login failed for user <null> : SQL Server 7.0

2. A connection could not be established to <Srv>- Login failed for user <dom/user>

3. <<<RDBMS/UNIX/SYBASE ENGINEERS WANTED>>>>Oakland, CA

4. <<<RDBMS/UNIX/SYBASE ENGINEERS WANTED>>>>Oakland, CA

5. <<<RDBMS/UNIX/SYBASE ENGINEERS WANTED>>>>Oakland, CA

6. >>>>>---- BETA TESTERS WANTED -------<<<<<<<

7. >>>>>> Attention CTO Candidates <<<<<<

8. <><><> www.FotoCD.net <><><>

9. <><><> www.FotoCD.net <><><>

10. <<<<<<ON SALE FOR OCP ORACLE DBA test(1ZO-013) material >>>>>>

11. <><><> www.FotoCD.net <><><>

12. >>>>>---- BETA TESTERS WANTED -------<<<<<<<


 
Powered by phpBB® Forum Software