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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Changed network cards, not cannot connect to named instance

Status
Not open for further replies.

Luvsql

Technical User
Apr 3, 2003
1,179
CA
We have a default and a named instance of sql server 2000 (sp#3) running on our Win2k server. We just switched to gigabit cards and now we cannot connect to the named instance via TCP/IP on the server using Enterprise Manager, Query Analyzer or ODBC connection or from any client (the application works fine because it connects via ADO).

I checked the port that the instance is listening on, but is there anyway to see if that port is valid or if any other app is using it?

The error we are getting is [TCP/IP Sockets] SQL Server does not exist or access denied.
 
What does the errorlog file show for that instance? If there is a problem listening on the correct port it should show up in there. It will also show up in the application event log.

Any error messages at all from the SQL Server in those logs?

Denny
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top