INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!

Talk With Other Members
Be Notified Of Responses
To Your Posts
Keyword Search
One-Click Access To Your
Favorite Forums
Automated Signatures
On Your Posts
Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Tek-Tips LinkedIn^® Group

Join our
LinkedIn^® Group!

Hook up with past and present colleagues and classmates quickly.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site

(Download This Button Today!)

Feedback

"...On your site I feel quite confident that the contacts and feedback will make my life a little less hectic..."

More...

Geography

Where in the world do Tek-Tips members come from?

Click Here To Find Out!

Tek-Tips Shirts!

Get your
Tek-Tips Forums
SWAG here!

Home > Forums > Programmers > EAI Distributed/Component Programming > DCOM / COM Forum

DCOM CoCreateInstanceEx and timeout? Gurus only!

Read More Threads Like This One

pcarver (TechnicalUser)

15 May 07 20:28

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.

pcarver (TechnicalUser)

16 May 07 0:51

Turns out that WM Services needs port 135 open for DCOM port mapping. Once I opened this port, things worked fine.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Back To DCOM / COM