Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 808
  • Last Modified:

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.
0
ChiliPequin
Asked:
ChiliPequin
  • 3
  • 2
4 Solutions
 
strivoliCommented:
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, MVPOwnerCommented:
Which virtualization software is being used?
0
 
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
Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

 
David Johnson, CD, MVPOwnerCommented:
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:
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
 
ChiliPequinAuthor Commented:
This approach seems to solve the problem.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now