Link to home
Start Free TrialLog in
Avatar of Gatsby
GatsbyFlag for United States of America

asked on

Named Pipes

Hi All

We have a web server (using IIS 5.0 and SQL Server 2000) that uses only TCP-IP as its network protocol and we are filtering out all but 4 ports. We are using Named Pipes as our NetLib. When we try to connect to the server from another machine using Named Pipes, we run into a "SQL Server Not Found" type of error. Is this because of the filtering or is there something else going on behind the scenes?

Thanks in advance.

Clayton
Avatar of ibro
ibro

You can connect using TCP protocol and to be sure what's going on use IP address of the server, but not the name of server. Try to ping the server from the client machine and check if you firewall allows access to SQL Server port (default is 1433).
  hope this will help.
Avatar of Gatsby

ASKER

Hi Ibro


1433 is closed but there is no reason why we couldn't use the TCP-IP netlib. This is more an academic
question. I'm not quite sure of the differences between TCP-IP (Network protocol) TCP-IP (Net-Lib) and
Named Pipes. I am just looking for clarification on exactly why I can't get to the server using Named
Pipes. I suspect it is the TCP-IP filters but I'm not sure. I guess the real queestion is....do the
TCP-IP filters in place block Named Pipes?

Thanks!
ASKER CERTIFIED SOLUTION
Avatar of SYASSIN
SYASSIN

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial