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

x
?
Solved

RPC: NT Server/UNIX client

Posted on 1997-08-14
1
Medium Priority
?
473 Views
Last Modified: 2013-12-23
I am implementing RPC with an NT server and a UNIX (DEC Alpha) client.

Easy enough to generate both a client and a server on a single platform.  'rpcgen' on UNIX and 'MIDL' on NT.  

The problem is getting a client generated by 'rpcgen' and a server generated by 'MIDL' to communicate.  The 'rpcgen' call seems to be the gating factor.  On the NT side I specify the pipe, the server and information like that.  On the UNIX side I specify nothing of this sort.  It is information such as procedure number and program number.  What are the significance of these things?  How do they fit in with what I did on the NT side?

Can anyone help?

-Joe
0
Comment
Question by:joechick
1 Comment
 

Accepted Solution

by:
bkc earned 100 total points
ID: 1582251
It seems to me that Microsoft's vision of RPC is not compatible with ONC RPC.

I believe NT's RPC mechanism runs over MS-networking (which may be on UDP, IPX or Netbeui) and uses Named Pipes to establish end-points.

I suspect you'll either have to purchase a 3rd party RPC package,
or port Sun's RPC implementation to Win32. We chose the later for an internal project. It wasn't difficult.

Windows uses named pipes for interprocess communication, which it
appears from your comments is what NT's MIDL expects.

You might look at Samba, an SMB implementation for Unix. It might
support named pipes and you might be able get a connection that way.

Also, I don't think Microsoft's RPC implementation is ONC RPC compatible, and I don't think Microsoft uses XDR. So even though both mechanisms are "remote procedure calls", I think they're implemented in different ways, regardless of the transport mechanism they use.

In fact, if you can NOT specify a program number, version and procedure number with NT, there's no way it can call an ONC RPC implementation, even if they both used UDP!

So, I'll change this from a comment to an answer: You can not use
Microsoft's RPC to talk to an ONC RPC server. You must use a 3rd party library or port ONC RPC yourself.

0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Originally, this post was published on Monitis Blog, you can check it here . It goes without saying that technology has transformed society and the very nature of how we live, work, and communicate in ways that would’ve been incomprehensible 5 ye…
This article will show how Aten was able to supply easy management and control for Artear's video walls and wide range display configurations of their newsroom.
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

963 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question