Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Duplicate server in list

Status
Not open for further replies.

Zen216

MIS
Jul 13, 2006
616
US
Hello All,
I have a server that needs to connect to a sql2000 db. Is was working fine for along time, but suddenly stopped working. When I go into the ODBC connectors, and try to create a new connection, on the drop down for "Which SQL server do you want to connect to" it lists this server twice, and fails to connect to either one. I have three other DB server on the network, and they are listed once, and I can connect to them fine. I have tried to create test connections on 4 other workstations, 2 servers, (1 virtual workstation and 1 virtual server, the rest are physical) and they all have no problems connecting. It is just this one server. Does anyone have any ideas on where I should look to try and repair this connection?

Thanks
 
for the time being,, I was able to get it working by using the IP of the db server instead of the name, but would still like to try and find out why it happened.
 
Is this default instance or named instance?
Try to ping to the instance name outside the system where SQL server is running and verify the name resolves with an IP.
If "No" engage your SA/Network team to verify the DNS entries for your instance

If "Yes" then proceed to

SQL Server Manager (2000)
Under SQL Server Properties
Connections: Allow RPC is enabled
General:? Bothe Named Pipes and TCP/IP are enabled protocols

SQL Server Client Network Utility
Alias: Add an Alias for your instance
All suggestions are for SQL Server 2000 and post back your results.

Good Luck




Dr.Sql
Good Luck.
 
DrSQL,
Thank you, I looked into the suggestions, and all were already as you advised.

One thing I did not mention, and I do not know if this is the issue as well...

this DB server was recently virtualized (VM Ware Vsphere 4, on a ESX host), however, after the virtualization, this is the only server that is having issues connecting to the DB. This is the only server that has the DB name listed twice in the odbc connector dropdown that I mentioned earlier... all other servers, and workstations see the virtual db with no issues, and no duplicates.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top