Named Pipes and Windows Firewall Question

  • Thread starter Thread starter dvestal
  • Start date Start date
D

dvestal

I have a program running on a WinXP SP2 computer that creates a named
pipe.

A program running on a different WinXP box attempts to open this named
pipe for reading, and receives system error code 53: bad network path.

If I turn off the Windows Firewall on the first computer, the
connection succeeds.

The question is, how exactly is Windows Firewall preventing the
connection from succeeding, and how can I get around it without
disabling the Firewall?
 
Back
Top