I'm having an unusual problem with named pipe, on an NT 4.0 system. I
force an error by closing an restarting the server end. The client
detects this and will attempt to connect to the named pipe (the original
name). This product needs to be automatically reconnect.
The outcome is that I can perform a Writefile to the pipe from the
Client side, but can no longer Readfile on the same pipe on the Client
side. (Although I know that there should be data there)
Has anyone else seen this problem? I tried searching Deja.News, and
Microsoft Knowledge Base.
I may implement two pipes ... one RX one TX, but would prefer to have it
work on the single pipe.
Thanks for any Help.