named pipes vs TCP/IP (tcp dosent work and names pipes do, why?)

Hi,
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.
Mark.
markkindredAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
nmcdermaidConnect With a Mentor Commented:
on the clients, go to a command prompt and try:

TELNET <Servername> 1433

(this tests TCP/IP)

Then try

TELNET <Servername> 445

(This tests named pipes)
0
 
imitchieConnect With a Mentor Commented:
check that tcp/ip is still enabled in   start->run->cliconfg
has anything changed on the firewalls? dns? windows update? software installs?
0
 
abhijit_kCommented:
Please Add Entry to HostFile on the Client Machine
Go to -- Run->Drivers->etc->open host file and add the entry in the last with Server Ip and Name.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.