I think I figured this out. Needed to opon port 135 on the server running
Windows Media Services.
Amil
"Amil Hanish" <amilhanish[ at ]hotmail.com> wrote in message
news:uNrgxMylHHA.3280[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] >I am using two Windows 2003 Servers. I use a utility on server A to look
>up publish points on server B's Windows Media Service. Server A uses
>standard connection code (see below). When I try to connect to server B, I
>get error "RPC server is unavailable" result code. I've used dcomcnfg on
>server B to allow correct rights. What is strange is I can get it to work
>by simply opening up dcomcnfg and drilling down to the Windows Media
>Services DCOM element. If I want a period of time, it will quit working,
>but I can get it to work again by just opening dcomcnfg. It's almost like
>a timeout and some strange DCOM thing goes away.
>
> Any ideas why it works, but after a period of time, some type of timeout
> occurs?
>
> hr = CoCreateInstanceEx(
> CLSID_WMSServer,
> NULL,
> CLSCTX_REMOTE_SERVER,
> &cs, // COSERVERINFO
> 1,
> &mqi); // MULTI_QI
>
> Amil
>
>
|