SQL ODBC Connection Weirdness

[endwarde]

I have a SQL 2000 server which is running Great Plains software on a 2003 Server. I have a number of XP Pro machines in the network that access this server regularly. When the Great Plains (GP) client was installed, all of the computers had an System DN created for the server (Pluto) and all was well... except for a couple of problematic PCs. Here's where the problem comes from:

When I go into the creation of the ODBC entry, when I go to enter the name of the SQL server, the list shows all of the servers on the network with SQL Server, but the server I am looking to connect to shows up twice in the list (same name, one after the other).

I select one of the servers, and on the next page I enter in the sa account and password to log in and I get the error message:

Connection failed:
SQLState:'01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error:17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access is denied


I can do this exact same procedure on other PCs, the server only shows up once in the list, and I log in easily.

Any idea what the heck could be causing this?

 

[ArtieChoke]

Does this happen if you choose either entry for the server?

"I think we're all Bozos on this bus!" - Firesign Theatre

 

[endwarde]

Yes, this happens regardless of which of the double-entries I select.