Connection problems

Question

Post reply

Connection problems

stubob

SSCommitted

Points: 1839
More actions
February 12, 2004 at 5:01 pm

#66255

Let me start by letting you all know that I am pretty ignorant of windows networking. Usually, I set up one computer with SQL Server and I can connect from another, it just works.
But not this time. Instead I try to register, or connect via ODBC, and I get the error:
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
What does all this mean? How do I become a user other than '(null)'? I tried connecting with the sa account & that gave a similar error message.
I work at a small office where we have set up a domain-less workgroup network. Computers all run Win 2k, Pro, or Win XP pro. Another question I have is whether SQL Mail is possible in this configuration. I was unable to get SQL Mail to work on a different SQL Server installation with no other obvious problems.
Data: Easy to spill, hard to clean up!

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 1

Try to configure the security settings on the SQL Server to permit Mixed mode (NT and SQL Server) authentication.

If it doesn't work, try to install MDAC 2.7 SP2.

stubob SSCommitted Points: 1839 More actions · Answer 2

Thanks - configuring to mixed mode works so I can connect through the sa (and I assume any other) sql server account.

I still wonder why Windows NT Authentication doesn't work, but the most important thing is being able to connect. Security is not an issue here, so I don't care if we use the SA account for now.

I'll move my sql mail question to another forum.

Data: Easy to spill, hard to clean up!

johnsonj SSCrazy Points: 2159 More actions · Answer 3

I agree with Allen that the first thing to check would be mixed mode security on the server.

Try this on the Win2k PC's first. I've seen some problems in small businesses without a domain or AD where the built-in firewall in XP causes some headaches with not only SQL, but also with sharing and networked printers and scanners.

Joe Johnson
NETDIO,LLC.

stubob SSCommitted Points: 1839 More actions · Answer 4

Yes, I configured for mixed mode and now I can connect from winXP to win2k via sql auth. I can connect from win2k to winXP using sql or windows auth via the guest account. I'm thinking now that the accounts aren't being communicated between machines.

For some reason that I do not understand, from winXP I get null user - not even "guest", which makes it impossible to authenticate.

We're going to move computers around soon. After that, I would like to know how to better set up the computers to communicate & access sql server.

Data: Easy to spill, hard to clean up!

dharper3 SSCrazy Points: 2391 More actions · Answer 5

Try this to allow winxp to win2k. From DOS cmd enter net use \\destinationserver\ipc$ password /user:destinationserver\ntaccount on destination server. Where destinationserver is the server hosting sql server and the ntaccount on destination server is an NT account on the server hosting sql server that is defined as a sql login. Password is the nt password for this account. Subsequent nt auth connections to sql server on the destination server will be permitted as the NT account you have specified in the net use command

stubob SSCommitted Points: 1839 More actions · Answer 6

Sounds good. I'm going to try that, but it will be a few days before I'm back in the office. Let you know how it goes then!

Data: Easy to spill, hard to clean up!

dharper3 SSCrazy Points: 2391 More actions · Answer 7

Oh and another thought because I have been getting this problem occur randomly 'null user' is that I need to create an alias via the SQL network utility. This seems to force connections via EM or osql to use named pipes rather than tcp/ip. Why I have to create these aliases is a question I would love an answer to myself, as my workstation setup etc etc has not changed but one day I can connect the next I cannot unless I define an alias.