Solved

RPC: NT Server/UNIX client

Posted on 1997-08-14
1
463 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

Don't Miss ATEN at InfoComm 2017!

Visit booth #2167 to see the  new ATEN VM3200 32 x 32 Modular Matrix Switch. Other highlights include the VE8950 4K HDMI Over IP Extender, VS1912 12-Port DP Video Wall Media Player  and VK2100 ATEN Control System. Register now with Free Pass Code ATEN288!

Question has a verified solution.

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

Suggested Solutions

#Citrix #Citrix Netscaler #HTTP Compression #Load Balance
Most of the applications these days are on Cloud. Cloud is ubiquitous with many service providers in the market. Since it has many benefits such as cost reduction, software updates, remote access, disaster recovery and much more.
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…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

759 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