Solved

RPC: NT Server/UNIX client

Posted on 1997-08-14
1
465 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
bkc earned 50 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

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Short answer to this question: there is no effective WiFi manager in iOS devices as seen in Windows WiFi or Macbook OSx WiFi management, but this article will try and provide some amicable solutions to better suite your needs.
PRTG Network Monitor lets you monitor your bandwidth usage, so you know who is using up your bandwidth, and what they're using it for.
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Suggested Courses
Course of the Month9 days, 14 hours left to enroll

624 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