Windows 2000 Client cannot connect Windows Server 2003 DCOM Server

Windows 2000 Client cannot connect Windows Server 2003 DCOM Server

Post by S2V2aW4gTF » Mon, 07 Aug 2006 17:51:02


I have a DCOM C/S system, with server app running in Windows 2000 Server, and
clients running in Win2K Pro and WinXP Pro. The server is running as a
Windows service. Both server & client apps are programmed by VC6/MFC. It
works well.
However, when we move the DCOM server to Windows Server 2003 (SP1), the
clients cannot connect to server no longer. Each time when client calls
CoCreateInstanceEx(), it returns 0x800706ba, and there is a new event log,
with ID as 10009 and description as "DCOM couldn't use any configed protocol
to communicate with computer ###". Even if we switch off the Windows
Firewall, the problem remain the same. When the windows firewall is on, we
notice there are 3 lines added into the firewall log:
OPEN-INBOUND TCP "client IP" "Server IP" 3440 135
OPEN-INBOUND TCP "client IP" "Server IP" 3441 135
CLOSE TCP "Server IP" "client IP" 135 3440

Any one could help me with this? Thanks !

Kevin
 
 
 

Windows 2000 Client cannot connect Windows Server 2003 DCOM Server

Post by RGVvbiBNY0 » Fri, 29 Sep 2006 01:09:03

I have a similar problem. I have a server running on XP Pro that I am trying
to connect to with a 2000 Pro client. I also get a 10009 event whenever I
try to connect.

The program I am using is distributed. An identical copy of the server and
client are running on the 2000 and XP machines also. The XP machine has no
problem connecting with 2000 server. The XP machine client can also connect
with other XP machines running the server. The 2000 machines' clients can
connect with other 2000 machine servers without problems.

In both configurations, I am only using the default system protocols for the
component.

Any ideas would be appreciated.

Thanks,
Deon