Re: RPC_S_INVALID_BINDING in client
From: Shawn Fessenden (shawn#no#_at_testech-ldt.#spam#com)
Date: 02/26/05
- Next message: Nollie: "Re: Getting all the HUMAN users on an XP/2K/NT machine"
- Previous message: Nollie: "Re: Getting all the HUMAN users on an XP/2K/NT machine"
- In reply to: Shawn Fessenden: "RPC_S_INVALID_BINDING in client"
- Next in thread: Shawn Fessenden: "Re: RPC_S_INVALID_BINDING in client"
- Reply: Shawn Fessenden: "Re: RPC_S_INVALID_BINDING in client"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 26 Feb 2005 19:47:21 GMT
Further info:
The latest documentation states that RpcServerRegisterIfEx (on the server
side) *REQUIRES* a server version of Windows, yet the call succeeds! What's
this all about? Does that mean I can't use an auto-listen interface? That
kinda blows. That means I'll have to put the call to RpcServerListen in a
separate thread - so's my dialog can draw & function.
And speaking of RpcServerListen, the dox also say that if I'm using an
auto-listen interface then I don't have to call listen! Jebus. Is there just
a simple tutorial somewhere on using MS RPC? So far the one I'm using (the
SDK RPC tutorial) has been wrong on all points - and *it* doesn't work
either.
And there's all this stuff about registering endpoint vectors & crap. All I
want to do is remote a few simple functions. I don't really care what RPC
does, as long as it does it right. Could somebody just give me a basic
overview for the following requirements:
The server will run on any version of Windows (using Win32). The server is a
dialog that displays status information - remote function name, last hit
time and number of hits. I could care less what transport is used. TCP/IP is
common to all servers. If I have to specify a port, ok but I would rather
let it float.
The client initially is a simple dialog that allows calling all functions on
any server for testing purposes. The client's final form is a php extension.
It will run on Windows 2000 Pro but should be compatible with XP / Server
2003 and whatever future versions of NT that MS cooks up, with the exception
that I don't plan on doing that Longhorn stuff.
-SHAWN-
- Next message: Nollie: "Re: Getting all the HUMAN users on an XP/2K/NT machine"
- Previous message: Nollie: "Re: Getting all the HUMAN users on an XP/2K/NT machine"
- In reply to: Shawn Fessenden: "RPC_S_INVALID_BINDING in client"
- Next in thread: Shawn Fessenden: "Re: RPC_S_INVALID_BINDING in client"
- Reply: Shawn Fessenden: "Re: RPC_S_INVALID_BINDING in client"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
