| Title: | DCE Product Information |
| Notice: | Kit Info - See 2.*-4.* |
| Moderator: | TUXEDO::MAZZAFERRO |
| Created: | Fri Jun 26 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2269 |
| Total number of notes: | 10003 |
A customer is in the process of testing Client/Server relationships in the DCERPC environment. To date he has sucessfully tested the environments: client Microsoft Windows 95/Server Microsoft NT relationship client Microsoft Windows 95/Digital UNIX relationship (2.08 ok) Now he is in the process of testing the Server Microsoft 95 / OpenVMS Alpha 6.1 client/server relationship and has ran into a snag. On the client side he is using Microsoft Visual C++ 4.0 on Windows 95 using DCE obtained from the Microsoft SDK CD # 9 August 1996. On the server side he is using DCE VERSION 1.3 the context handler example CXHNDL to serve access to a data file. The network transport used is TCP/IP. The functionality he is attempting to get working between the Client and the Server is contained in the CXHNDL example. (Since I cannot locate this example in the dce examples directory on an Alpha system, I suspect it is one that comes with MS). When this runtime environment is executed the client logs a FAILURE IN CONNECTION error condition. Customer suspects that there may be some version compatibility issues. If the versions are compatible additional help understanding why there is a failure in the connection would help. Thanks, Elin
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2213.1 | MS RPC <> DCE RPC | ESME::SPENCE | Bugs? You mean insects? | Wed Apr 09 1997 12:19 | 14 |
I didn't know you could get DCE from Microsoft. I've done a fair amount of interoperability testing between Microsoft's RPC and the official DCE RPC, and I found a major problem in the area of context handles. I never managed to get this to work correctly using the built-in RPC for a Windows 95 or NT 3.51 client. However, if you use an NT 4 client, or a 'proper' DCE client, it works. Maybe this is the problem you're seeing. You don't get this problem if use Digital DCE for Windows on the client (it's the real thing). - Cameron | |||||
| 2213.2 | "DCE obtained from Microsoft? | TUXEDO::MAZZAFERRO | Wed Apr 09 1997 14:56 | 8 | |
I, too, would be very curious to find out if you're really using a true DCE product obtained from Microsoft on Win95, or NT, for that matter. We know of no such DCE product from Microsoft. Microsoft provides an RPC as part of the SDK, but Digital provides the full DCE runtime facilities on top of their RPC. If you're not using the DCE product from Digital and only using the MSRPC, then this is a Microsoft problem. Laura | |||||
| 2213.3 | I'll verify exactly what is what | CSC32::E_VAETH | Suffering from temporary brain cramp, stay tuned | Wed Apr 09 1997 15:57 | 3 |
thanks for the help so far -elin | |||||