Named Pipes Application Run on Windows 7 Virtual PC.

Hi Experts,

I have an MFC application that uses Named Pipes.  It is working fine on a stand alone PC.  I try to use this same application on a Windows 7 Virtual workstation, but the message from the pipe client is not always sent to the same the virtual workstation.  What should I do to get this to work correctly?

Thanks in advance.
ChiliPequinAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
ChiliPequinConnect With a Mentor Author Commented:
Hi Experts,

Thank you very much for your input.  I have found a solution for my question.  After reading further on Microsoft document, I realize that from the server side, I can only use the dot for local server when I create a namedpipe.  I now append the virtual IP address to the name when I create a namedpipe.  This approach seems to work for me.

Thanks again for your advice.
0
 
strivoliConnect With a Mentor Commented:
The client is a physical PC that connects to a server which is a virtual W7?
Is the connection between client and server, reliable?
0
 
David Johnson, CD, MVPConnect With a Mentor OwnerCommented:
Which virtualization software is being used?
0
[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

 
ChiliPequinAuthor Commented:
Hi experts,

Both the client and the server reside in the same session of the Virtual Workstation.  Currently, the server uses the CreateNamedPipe with the name:  LPTSTR lpszPipeName = TEXT("\\\\.\\pipe\\myPipeApp");  Since we move this application to a virtual workstation, there are many other sessions; therefore, when the client sends the request, sometimes the request is routed to one session, other times, the request is routed to another session.  

I am thinking of replacing the . in the pipename to the IP address of the session on the V-workstation, but the create fails with error 123 when the . is replaced with the ip address like LPTSTR lpszPipeName = TEXT("\\\\12.34.567.89\\pipe\\myPipeApp");

Thanks.
0
 
David Johnson, CD, MVPConnect With a Mentor OwnerCommented:
to connect you would use \\192.168.0.100\pipe\pipename but the pipe must already be connected.

http://stackoverflow.com/questions/719353/win32-named-pipes-and-remote-clients
0
 
ChiliPequinAuthor Commented:
This approach seems to solve the problem.
0
All Courses

From novice to tech pro — start learning today.