named pipes vs TCP/IP (tcp dosent work and names pipes do, why?)
Posted on 2007-11-22
I have a client who connects a client app to a SQL 2000 server. Recently 3 of his client computers were unable to connect to the SQL server. the error was 'the server dosent exist or you dont have permissions'. When checking the clients ODBC settings they were set to connect using TCP/IP (just like the other 30 odd clients that are still successfully connecting). I changed the connection protocol to named pipes and the faulting workstations connected instantly.
Could you shed any light on why these 3 computers will only connect using names pipes and all the others connect fine using TCP/IP? The workstations are a mix of Windows XP Pro and Vista Business Edition and all are connecting through a Windows 2003 domain to a Microsoft 2000 SQL server sat on a Windows 2000 Server box.
thanks in advance.