Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DCOM CoCreateInstanceEx and timeout? Gurus only!

Status
Not open for further replies.

pcarver

Technical User
Aug 23, 2001
36
US
It's very strange. I am using CoCreateInstanceEx between two Windows Server 2003 system to connect to a Windows Media Server. If I connect to the local server running WM, it works great. If I try to connect to a remote server it fails. OK, I know you are thinking security issues, etc; I've been through all that. Here is the STRANGE PART.

If I get on the remote server, and run the dcomcnfg command...literally, just bring up the config utility for DCOM, then I can connect from to the remote server, but only within the next few minutes. If no activity of more connects, then seems like something times out and I can't connect any more.

It's almost like the DCOM stuff on the remote server isn't actually started/created until something on the remote server does it...but then maybe a timeout occurs and after a minute or two, I can't connect any more.

Given that I can connect sometimes, I think security is set up correctly.
 
Turns out that WM Services needs port 135 open for DCOM port mapping. Once I opened this port, things worked fine.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top