CreateNamedPipe... someone got any idea?

Lately I have been experimenting with pipes. I made two apps (server and client) respectively. The problem is that the server app doesn't initialize the pipe. I checked for all the parameters and also reffered to the example on a CD (Visual C++ 4.0 Developer Studio) yet no success. The CreateNamedPipe function doesnt create any pipes.

The pipe name string is written correctly \\\\.¡\\pipe\\mypipe for the server side.
I checked server app even on the same computer as client one  (basically it was meant to run on a server - NT 4.0), otherwise the network itself isn't a problem.

I'm asking what else could be wrong?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hi The OnlineDocumentation says the path to the pipe has to be
\\.\pipe\pipename (for using a constant within C/C++
if it is not a typo you have
and that is wrong as the docs says
Hope that helps

NitemareAuthor Commented:
Yes that's what documentation said. But one should be aware that specifying special character in a string you must use \ and then the character you want in your string. Therefore \\ in a string means \. This was also my first mistake. I debugged the app and saw the string I want is in memory just as it should be. there has to be seomething else.
NitemareAuthor Commented:
Character after dot is a mistake. Ignore it.
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

Have you tried using GetLastError() to see what the error is?  You should always try that first.
To use VC's memory debugging features you use the procedure _CrtSetDbgFlg().  with the _CRTDBG_LEAK_CHECK_DF flag.  (Or this flag in with the existing flags.  This will report memory block overruns and blocks that weren't deleted when the program terminates.  To make it really effective, though you need to overload the new operator so that it stores with each block the source code file name and line number from which thr block was allocated.  Then when you gets these errors reported, you can doubleclick the error message and it will show you the line of code that allocated the block.  This is all documented in the VC help.
Woops.  Got posted to the wrong question!  sorry.
Feel free to reject this because it is a shot in the dark, but named pipes can only be created on NT. Is your test machine an NT?
NitemareAuthor Commented:
Yes. I use NT 4.0 Server. That's the whole  point. Since it didn't work I ran both apps on Windows 95 machine because I suspected something could be wrong with network implementation.
NT machine is just as is, no SP3 or alike have been installed.
I read all docs I could find on that topic and haven't found a statement that would imply named or annonymous pipes won't work on Windows 95.

Perhaps someone could pass an alternative?

Promising solution will get double points!!!
On Win95, only the client side of named pipes is implemented. So your client app should work on win95 and on NT, not your server.

What exactly is your problem? Does "CreateNamedPipe" return an invalid handle? If not, does connectnamedpipe return you an instance or is your client just failing?

Is your server app a service?

I have a working program with named pipes for a server and programs from NT and 95 can connect to it...
Your problem could be coming from the fact that the client is connecting as a NULL session.  (It's hard to tell from your question if this is the case or not.)

To allow a NULL session to connect to a pipe, check out MS-Knowledge base article Q126645.  Along with a lot of other things, it says:

>You can allow access to a named pipe using the Null Session by adding the pipe name to the following registry entry on the machine that creates the named pipe:

The pipe name added to this entry is the name after the last backslash in the string used to open the pipe. For example, if you use the following string to open the pipe:


you would add mypipe to the NullSessionPipes entry on the computer named hardknox.

Hope this helps!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
NitemareAuthor Commented:

Yes I appologize that I didn't supply as much data as needed but you gave me an extra edge with that article. It solved a few other things too. Thx abesoft.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.