Thursday, March 22, 2012

Authentication Issue - Cannot connect from one wkstation

Hi,
I am having trouble using windows authentication to connect to a SQL Server
2000 instance on a Windows 2003 Server. I can connect with my domain accoun
t
from Computer A but not from Computer B. Other authentication requirements
to the server seem to be fine from Computer B eg I use my domain account to
logon to Computer B and I can remote to the server from Computer B.
I was having some issues with my profile on Computer B so I wonder if this
has affected some cached credentials for SQL Server or something else. Any
help with this would be most appreciated.
Thanks, TadHi,
which error do you get ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--|||Hi,
In SQL Query Analyzer:
Unable to connect to server XXXX:
Server: Msg 17, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or
access denied.
In MS SQL Server Mgmt Studio:
Cannot connect to XXXXX.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 2)
In SQL Enterprise Manager (while trying to register server):
XXXX - SQL Server does not exist or access denied.
ConnectionOpen (Connect())
"Jens" wrote:

> Hi,
> which error do you get ?
> HTH, Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>|||Are the computers in the same domain ? Which authentication method are
you using ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
--|||yes, same domain and Windows authentication
"Jens" wrote:

> Are the computers in the same domain ? Which authentication method are
> you using ?
> Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>|||Tadwick wrote:
> Hi,
> I am having trouble using windows authentication to connect to a SQL Serve
r
> 2000 instance on a Windows 2003 Server. I can connect with my domain acco
unt
> from Computer A but not from Computer B. Other authentication requirement
s
> to the server seem to be fine from Computer B eg I use my domain account t
o
> logon to Computer B and I can remote to the server from Computer B.
> I was having some issues with my profile on Computer B so I wonder if this
> has affected some cached credentials for SQL Server or something else. An
y
> help with this would be most appreciated.
> Thanks, Tad
Are you sure it's an authentication error and not something network
related? Can you even SEE the server from this workstation? Can you
ping it by hostname AND by IP address? Can you connect to SQL via the
IP address?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy,
Your note just prompted me to the solution. It was not authentication - it
was because I used a custom instance name and was so used to it being there
by default when I open a client side tool that I forgot to specify when my
profile changed on Computer B. Embarassing, but true.
Thanks to you and Jens for getting me there.
Tad
"Tracy McKibben" wrote:

> Tadwick wrote:
> Are you sure it's an authentication error and not something network
> related? Can you even SEE the server from this workstation? Can you
> ping it by hostname AND by IP address? Can you connect to SQL via the
> IP address?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>sql

No comments:

Post a Comment