workstation sees 2 instances of the SQL Server?

[emily]

This might not be a SQL Server question, might be something else. I
have a workstation on a LAN that can't connect to the SQL Server. When
I try to configure a User DSN to connect to it, the server name I want
appears TWICE in the list of possible servers. No matter which one I
select, it can't get the connection.

The workstation also can't connect through EM or QA.

We've checked the user's permissions, we've re-installed some server
packs, re-installed the Client Tools, we've even hunted through the
registry, everything looks OK, but we still can't connect. This is the
only machine on the LAN that can't connect. Everybody else connects
fine.

I'm stumped. Any ideas? Anybody ever seen the server name appear
twice like that?

-Emily

[Erland Sommarskog]

emily (eh******@hotmail.com) writes:

This might not be a SQL Server question, might be something else. I
have a workstation on a LAN that can't connect to the SQL Server. When
I try to configure a User DSN to connect to it, the server name I want
appears TWICE in the list of possible servers. No matter which one I
select, it can't get the connection.

The workstation also can't connect through EM or QA.

We've checked the user's permissions, we've re-installed some server
packs, re-installed the Client Tools, we've even hunted through the
registry, everything looks OK, but we still can't connect. This is the
only machine on the LAN that can't connect. Everybody else connects
fine.

I'm stumped. Any ideas? Anybody ever seen the server name appear
twice like that?

And the error message is?

Have you tried added an alias in the Client Network Utility?

Have you tried connecting using the IP-address?

Have you checked in the Client Network Utility that the protcols that
server use are enabled?
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

[emily]

We got it. It was the Client Network Utility. The workstation had a
bad alias set up in there, for some reason. We deleted that alias, and
now we can connect! Thanks for your help. Learn more about this stuff
every day....