Pretty sure. The only reason I say that is that when I test it I have to change to the port every test because if I don't it says the port is in use (I guess the program isn't closing the port or something). Honestly I still don't fully understand how rpc finds the port number, which may be the problem. When using RpcServerUseProtseq on Windows, according to msdn, "the port number is dynamically determined by the RPC run time, depending on availability and registry settings." If that's the case how does the client know what port to connect to? Since I'm using RpcServerUseProtSeqEp instead on Linux would that change things? I'll try specifying the port in the client and seeing if that works.
My code works and I use different functions, have a look. I do specify a port. It's roughly taken from the MSDN.
Matt Edlefsen
Damjan
rpctest.tar.bz2
Description: BZip2 compressed data
