| Author |
Topic |
|
efelito
Constraint Violating Yak Guru
478 Posts |
 Posted - 2002-02-28 : 11:25:10
|
| Hey guys, I have a workstation that is having a problem connecting to a newly configured SQL Server. The server is running Win2K SP1 and SQL Server 7.0 SP3. The workstation is running WinNT 4.0 SP6 and the SQL Server Client Tools SP2. While trying to connect in Query Analyzer with the client alias set to TCP/IP, he receives the following error. "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection." Per KB article Q247641 I tried disabling multiprotocol support using the Server Network Utility, and switching the client to named pipes. While trying to connect in Query Analyzer with the client alias set to named pipes, he receives the following error. "[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exists or access denied." The workstation is able to connect to the server via SQL Authentication with no problems. This workstation is able to connect to many other SQL Server 7.0 SP3 servers via NT Authentication. Many other workstations are able to connect to the new server via NT Authentication. Any ideas on getting this workstation connected to this server?Jeff BanschbachConsultant, MCDBA |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-02-28 : 14:01:42
|
| Are you logged in as a local account, or a domain account?-Chad |
 |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-02-28 : 14:44:21
|
| The server is logged in as a domain account and so is the user. He is able to connect to other SQL Servers on the network via NT Auth, but not this particular one. After a little more testing, we found that this happens to him no matter what machine he logs into, and that I can connect to the server when logged into his machine. So it's not a workstation issue. It's almost like SQL Server doesn't see his login, but it's in there just like every other server.Jeff BanschbachConsultant, MCDBA |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-02-28 : 15:01:05
|
| try dropping and recreating the login.Make sure his account has the 'Access this computer from the network' right.What is the full error message (What precedes the part you posted)? -Chad |
|
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-02-28 : 15:38:15
|
| I have tried droping and recreating the login several times. I have also tried adding an NT group that he is a member of. Both to no avail. Where would I find the 'Access this computer from the network' right? Is it on his NT domain account?This is the error when he tries to connect via Named Pipes....Unable to Connect to server \\SERVERNAME:Server: Msg 17, Level 16, State 1[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.This is the error when he tries to connect via TCP/IP....Unable to Connect to server \\SERVERNAME:Server: Msg 18452, Level 16, State 1[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.Jeff BanschbachConsultant, MCDBA |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-02-28 : 16:15:19
|
| You would assign that right on the server under Admin Tools->Local Security Policy->Local Polocies->User Rights assignmentThis seems pretty strange. Try creating an alias and connecting to that. Also try creating a DSN, and see if it allows you to connect when you set up the DSN. You might also want to turn on auditing of failed logins, and see what gets logged.-Chad |
|
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-03-01 : 09:19:43
|
| I have audit logging turned on, and the messages that appear in the gui get logged on the server. (Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.) I've tried creating a couple of different aliases with the same results. I'll nab someone from the security team and have them assign him that right on the server. I'll also give the DSN a try and let you know how it all goes. Thanks for all of your help on this BTW.Jeff BanschbachConsultant, MCDBA |
|
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-03-01 : 09:41:12
|
| You da man chadmat. The 'Access this computer from the network' right in Admin Tools->Local Security Policy->Local Polocies->User Rights only included the Administrators group. I added Everyone and BANG the developer was able to connect. I've been banging my head on the wall for 2 days trying to figure this one out. Excuse me while I go chew on the group that set this box up for me. Thanks again for your efforts. If you were in the area I'd buy you a beer.Jeff BanschbachConsultant, MCDBA |
|
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2002-03-01 : 11:15:20
|
You are welcome. Go drink a  for me.  -Chad |
|
|
|
|
NT Authentication Problem