Connection failure

I developed an MS Access front end to an MS SQL 2000 database. The server is now in production on a remote site.
I am attempting to continue developing the system linking to a development version on my PC.
The VB coding has connection to the devl database hard coded, and the drop down combos use the linked tables to the DEVL database.
But when I call a query that in turn passes parameters to stored procedure the system hangs for 30 secs then returns error:
Connection failed
SQL State: '01000'
SQL server Error: 11001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] Connection Open (Connect())
Connection failed
SQL State: '01000'
SQL server Error: 11001
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] Specified SQL Server not found

It then allows me to choose between IMEX-SERVER ( the PROD server which is not connected) and PHACT-PC (the devl database server). PHACT-PC brings back the correct selection from the devl database.

I have done a reinstall of the WIN XP operating system, lest there was data in the registry, and reinstalled the developers SQL SERVER 2000 with SP4. The problem still persists.

I cannot see any alias when I use CLICONFG.

How can I continue to develop the system whilst pointing to the DEVL database, yet be certain that it will work when I put it on the users client machines which point to IMEX-SERVER?

Telnet IMEX-SERVER 1433 returns connecting to IMEX-SERVER could not open connection to the host on port 1433. Which is as expected as it is not on the same network. However when I try telnet PHACT-PC which is the SQL sever sitting on the same PC it hangs for more than three minutes.

The CLICONFG is set for two protocols firstly TCPIP with port 1433, secondly named pipes \\.\sql\query

Thanks for the suggestion about firewalls, but this is connecting to a SQL server on the same box. I am using ESET/NOD antivirus and MS windows firewall.

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

I skipped the upgrade SP3a and went directly to SQL2000.AS-KB884525-SP4-x86-ENU.
Should I apply SP3a then SP4?
Should I uninstal SQL server and start again?
It will be 24 hours before I can do it, but will keep you informed.

I note that the SuperSocket Info: Bind failed on TCP port 1433. I checked on netdiag /test:winsock, it passed but warned that "RAS Async adapter" may not be working because it had not received any packets, but that is just a remote area connection.

I checked the network connections for TCP/Ip. It is set to automatically to obtain IP address and automatically obtain DNS server address and is DHCP enabled.

There was some reference to winsock corruption seizing port 1433.
There is a Microsoft registry workaround in Q307197 to change the DWORD to TcpAbortiveClose on HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer\SuperSocketNetlib\Tcp which I have not tried.

The other alternative is to use LSP-FIX a utility that repairs damage done to WINSOCK2 registry. But Netdiag seems to think this is OK.

The queries are pass-through queries. These are attached to the data-source when they are saved originally. This seems to be the only occassion when the data source is set, as it cannot be edited or enven displayed again. I have eight pass-through queries. I will rename them and re-create eight pass-through queries with the same name pointing to the TEST database. I understand that I could create a generic pass through query.

Thanks for the tip about the upgrade version. I still do not know why I have a supersocket bind error SuperSocket Info: Bind failed on TCP port 1433.

Microsoft Access has a limit of 255 columns in a single table; SQL Server allows tables with over 255 columns, but reading that data is not necessarily simple. The final solution for this task involved creating a custom text parser and then reading…

Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.