Login issue

[kodaksmile]

I have a sql server account that I can use to connect through odbc from my desk to the server. If I go out to a different machinein another building that is still on the same domain and try to connect via odbc I get an error that either the sql server does not exist or access is denied though I can ping the server by name and by ipaddress and as I mentioned previously can connect via odbc from another workstation using the same sql id. Any ideas on where to look?

Thanks

 

[SQLBill]

How is the ODBC connection set up? Is it FILE or SYSTEM DSN?

One is machine specific, the other isn't.

Is the SQL Server using Windows Authentication Only or MIXED Authentication?

If Windows Only, the other computer might not be 'trusted'.

Look in SQL Server's Error Logs for any messages. Also, look in the server's Windows Event Viewer Logs (application, security, system) for any error messages.

-SQLBill

 

[kodaksmile]

I was using system dsn so it would be for all users. The sql server is using mixed mode and I am using a sql login. There were no entries in either the sql log or the event viewer (first 2 places I looked).

 

[SQLBill]

I don't know how to check the version, but your MDAC may be 2.6 or earlier. Try upgrading the MDAC to the latest version. My understanding is that MDAC has something to do with ODBC and an old version is one of the biggest reasons for connection failures.

-SQLBill

 

[kodaksmile]

That was the first thing I did was upgrade to mdac 2.7 refresh 1..... I am really out of ideas short of reimaging the workstation....

 

[TonyKhela]

Have you checked the client network Library?
Look for it in the ODBC configure properties.
Is it TCP/IP? What is the port?
Is the same setting as your other client?
Is the same Network Library configured on the server?
TK

 

[kodaksmile]

I tried using both TCP/IP and Named pipes -- the server is set to accept both and I checked the port on TCP/IP and it is correct - also tried letting it dynamically configure port. It is the same setting as on the other workstation.

 

[TonyKhela]

Pls check the ODBC SQL Driver version and compare with first workstation. Its in the ODBC Drivers tab.
Also you might want to try connecting using Query Analyser from the troubled workstation.
Or to check the SQL TCP/IP use SQLPING utility.
Or to check the SQL Named Pipes connection use Makepipe and ReadPipe.exe utility.

Hope this helps
TK

 

[Corran007]

Is it just that single machine that will not work? Try a different machine in that same building. Im wondering if the building doesnt have a firewall preventing it or something like that.

 

[kodaksmile]

Yes it is just a single machine in that building - another machine one desk away works fine...

 

[JBaileys]

Kodaksmile,

We had a similar issue. Once we set-up a trusted user on the server and added a login in sql server using server\username as a valid login - things worked fine.